<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security-Tooling on it-learn.io | IT, Networking &amp; Cybersecurity Blog</title><link>https://blog.it-learn.io/tags/security-tooling/</link><description>Recent content in Security-Tooling on it-learn.io | IT, Networking &amp; Cybersecurity Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 27 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.it-learn.io/tags/security-tooling/index.xml" rel="self" type="application/rss+xml"/><item><title>Auditing a Cisco ISE Deployment Without Touching It</title><link>https://blog.it-learn.io/posts/2026-05-30-cisco-ise-read-only-audit-report-generator/</link><pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate><guid>https://blog.it-learn.io/posts/2026-05-30-cisco-ise-read-only-audit-report-generator/</guid><description>&lt;p&gt;A weekend project that turned into the consulting deliverable I wish I&amp;rsquo;d had three customer engagements ago: a read-only ISE audit that pulls 52 endpoints over ERS and OpenAPI, derives findings, maps them to a prioritized remediation catalog, and renders an HTML / PDF report you can hand a customer the same afternoon.&lt;/p&gt;
&lt;p&gt;Repo: &lt;strong&gt;&lt;a href="https://github.com/asarmiento85/cisco-ise-automation"&gt;github.com/asarmiento85/cisco-ise-automation&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In the &lt;a href="https://blog.it-learn.io/posts/2026-05-12-cisco-ise-automation-ansible-claude-deployment/"&gt;previous ISE automation post&lt;/a&gt; I walked through deploying ISE 3.4 from scratch in one evening. This one is the opposite direction: how do you assess an ISE deployment &lt;strong&gt;that already exists&lt;/strong&gt;, without changing a thing, and produce something a customer can actually act on?&lt;/p&gt;</description></item></channel></rss>