Skip to content
Zero Day Playbook

Cisco ISE network access control playbook: the first 72 hours after a critical flaw

  • 0 to 4 hours: 3 steps
  • 4 to 24 hours: 4 steps
  • 24 to 72 hours: 2 steps
  • Hours elapsed: the bar under the cells

Checklist to print

  1. 0 to 4 hours3 steps, due by hour 4
    1. 1

      Security lead, hand-off

      List every node of the system, the release and the patch level. On Cisco ISE and ISE-PIC run show version at the CLI of each node, because a node can lag its peers. Mark which nodes are primary admin, secondary admin, policy service and PIC.

      Done at

    2. 2

      Platform engineering, hand-off

      List which networks can open connections to each node's management and API interfaces, from firewall rules and from a test on a normal user VLAN and any guest network. Then apply infrastructure ACLs so only required management and control plane traffic reaches the nodes. List the admin stations and integrations that call ISE before you apply, since anything not listed loses access. Cisco's advisory does not name the API endpoint or port, only that the bypass reaches "the web-based management interface", so treat every management-plane port the node listens on as the target. Test from outside your network, for example from a cloud host or a phone hotspot: nmap -Pn -p 443,8443,9060 <node address>, and curl -k -sI --connect-timeout 5 https://<node address>/admin/. Every port must show filtered or time out.

      Done at

    3. 3

      Security lead, hand-off

      Take a copy of the configuration and a backup before touching a node: Administration > System > Backup & Restore. Start a support bundle on each node with debug logs and shared key encryption, so the apigateway access log is kept.

      Done at

  2. 4 to 24 hours4 steps, due by hour 24
    1. 4

      Security lead, hand-off

      Review the access log on every node of the deployment for suspicious usernames: show logging application ise-kong/access.log | include dummyuser, where dummyuser is the example string in Cisco's advisory. Replace it with each username you want to look for: any name that is not an account you created, and any name an attacker could pick, since Cisco calls its example non-exhaustive. Read ./ise/logs/apigateway/access.log.gz from the support bundle for older entries. Any hit on a username nobody owns is a possible compromise.

      Done at

    2. 5

      Security lead, hand-off

      Cross-check network and firewall logs outside the device for uploads from the ISE node to external addresses and downloads from malicious addresses. Cisco publishes no indicator addresses, so look for any outbound flow from the node that has no purpose.

      Done at

    3. 6

      Platform engineering, hand-off

      Install the fixed patch one node at a time, secondary admin and policy service nodes first, the primary admin last. Confirm replication and show application status ise after each node, and test a wired, wireless and VPN login before the next node.

      Done at

    4. 7

      Platform engineering, hand-off

      Rebuild any node with a suspicious hit instead of patching it: re-image, then restore the configuration backup. Cisco strongly recommends re-imaging if you suspect compromise.

      Done at

  3. 24 to 72 hours2 steps, due by hour 72
    1. 8

      Security lead, hand-off

      If a node may have been compromised, rotate everything it holds: admin passwords, the AD or LDAP join and bind accounts, RADIUS shared secrets, pxGrid and ERS API clients, certificates (Administration > System > Certificates), and any integration credentials. End active admin and portal sessions.

      Done at

    2. 9

      Application owner, hand-off

      Test sign-in for each application and network service that depends on the system, including guest and posture flows, and record failures. Review accounts that were created in the exposure window and any policy change you cannot explain.

      Done at

This playbook is for Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC), the network access control (NAC) server that sets who joins the network. It is not a playbook for a cloud identity provider such as a single sign-on service. An ISE node holds the access policy, the connections to the directory, RADIUS shared secrets, certificates and API client credentials. Flaws in it are usually authentication bypasses on an API or admin endpoint, reached from the network with no credentials. CVE-2026-76460 is one: Cisco says a successful attack may give command execution as root, and control of the server is control of network access.

Patching is hard because the server must keep answering. A NAC outage locks out staff, VPN users and wireless devices, so nodes are patched one at a time in a set order. Evidence is also weak: after a root compromise the attacker can hide or remove traces on the node, so logs held elsewhere carry the investigation.

When no fix exists yet

If the vendor has no fix yet, the mitigation for a NAC server is to shrink who can reach it. Allow only the admin hosts and the devices that must talk to it, and put the API behind the management network. The cost is that every integration outside the list stops working, so build the caller list first. Cisco's guidance for ISE treats ACLs as a reduction of exposure, not a fix.

Take the system offline only if exposure is wide and exploitation is reported, and only after you know what fails without it. An offline NAC server means wired and wireless authentication fails open or fails closed depending on your design, so decide that in advance. When compromise is suspected, a rebuild from a clean image and a configuration backup is the safe route, and the cost is node downtime.

CVE-2026-76460 worked through, hour by hour

Cisco published advisory cisco-sa-ISE-ABP-VNSW7Tn5 on 16 Sep 2026 at 16:00 GMT for an authentication bypass in an API endpoint of Cisco ISE and ISE-PIC. The CVSS 3.1 base score is 10.0 and no configuration is required to be affected. Each row pairs a published event with what a team running this playbook does at that hour. The advisory, the NVD record and the KEV entry all appeared on day 0, and no source dates the first attack.

WhenWhat happenedSource
16 Sep 2026, 16:00 GMT (hour 0)Published: Cisco releases version 1.0 with fixed patches for 3.1 to 3.5, says release 3.0 is end of software maintenance, says there is no workaround, names the ise-kong access.log search for suspicious usernames on every node as the indicator, gives no attack date, attacker detail or indicator addresses, and says its PSIRT is aware of active exploitation. The bug (CSCww39530) was found while resolving a TAC support case. Response: the security lead reads the advisory and starts the version check with show version on every node.source
16 Sep 2026, 17:00 to 20:00 GMT (hours 1 to 4)Response, no new publication: the inventory is complete, with each node marked by release, patch level and whether it sits below the fixed patch. Platform engineering lists the callers of each node, applies the ACLs, which are the one mitigation the advisory gives, and runs the outside port test, while the security lead takes the configuration backup and starts the support bundle with debug logs so the apigateway access log is kept.source
16 Sep 2026, 21:17 UTC (hour 5)Published: NVD publishes the record with a CVSS 3.1 base score of 10.0 (Critical), supplied by Cisco. Response: the per-node log search for usernames nobody owns is under way, with network and firewall logs checked for outbound flows from each node.source
16 Sep 2026 (CISA publishes no time; hours 0 to 8)Published: CISA adds the CVE to KEV with a due date of 19 Sep 2026, forensic triage Yes and ransomware use Unknown. Its SSVC entry in NVD records exploitation as active, automatable as yes and technical impact as total. Response: the forensic triage flag moves the log search ahead of the patch, so no node is patched before its logs and support bundle are copied.source
17 Sep 2026 (hours 8 to 32)Response, no new publication: nodes with a hit are re-imaged and restored from the backup. The remaining nodes are patched one at a time, secondary admin and policy service nodes first, the primary admin last, with a wired, wireless and VPN login test after each.source
18 Sep 2026 (hours 32 to 56)Response, no new publication: if any node had a hit, the AD or LDAP accounts, RADIUS shared secrets, pxGrid and ERS clients and certificates are rotated, and admin and portal sessions are ended.source
19 Sep 2026 (hour 72)Published: KEV due date, three days after listing. Response: every node is on its fixed patch or documented as an exception, the integration tests are recorded, and the new accounts and policy changes in the exposure window are confirmed by their owners.source

The advisory and the listing came on the same day, so the 72-hour window of the playbook ends at the KEV due date. Because KEV marks forensic triage Yes, a patched node still needs its log search and network cross-check before it is called clean. The advisory gives no attack date, so the log search must cover the whole period the nodes were reachable, not only the days after 16 Sep.

Sources

  1. Cisco Security Advisory cisco-sa-ISE-ABP-VNSW7Tn5, read 19 Nov 2026
  2. CISA KEV entry for CVE-2026-76460, read 19 Nov 2026
  3. NVD record for CVE-2026-76460, read 19 Nov 2026

Last reviewed 19 Nov 2026.