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

Playbook, sources read 19 Nov 2026

**The short answer.** Cisco Identity Services Engine (ISE) decides which users and devices join wired, wireless and VPN networks, so an authentication bypass there reaches everything behind it. Cisco rated CVE-2026-76460 at CVSS 10.0 on 16 Sep 2026, and CISA listed it the same day with forensic triage required.

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.

## The steps, hour by hour

| Window | Owner | Step, and why it comes here | Record to keep |
| --- | --- | --- | --- |
| 0 to 1 hour | Security lead | 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.<br>The fixed patch differs per release (3.1 Patch 12, 3.2 Patch 11, 3.3 Patch 12, 3.4 Patch 7, 3.5 Patch 4). Release 3.0 has reached end of software maintenance and has no fix: Cisco says to migrate to a supported release that includes the fix, so plan 3.0 nodes as an upgrade to one of those trains and then its fixed patch, following the Upgrade Guides on Cisco's ISE support page. | Node, role, release, patch level, and whether it is below the fixed patch. |
| 0 to 4 hours | Platform engineering | 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.<br>Cisco has no workaround, and ACLs are its only mitigation; they reduce who can reach the API but do not fix the flaw. | The ACL before and after, the callers you kept, and the test from an untrusted VLAN. |
| 0 to 4 hours | Security lead | 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.<br>Patching restarts services, and the log on a node may be the only record of what ran against the API. | Backup name, support bundle name, hash, time, and who holds the shared key. |
| 4 to 24 hours | Security lead | 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.<br>Cisco names this log and this command as its indicator, and CISA marks the entry forensic triage Yes, so the search must be run per node, not on the primary only. | Per node: period covered, usernames searched, and each hit with the source address. |
| 4 to 24 hours | Security lead | 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.<br>After root access the evidence on the box can be removed, so the network record is the independent check. | The query, the period, and each unexplained flow. |
| 4 to 24 hours | Platform engineering | 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.<br>Authentication keeps working only if a node is healthy while its peer restarts. | Per node: patch level, time, replication state, the three login tests. |
| 4 to 24 hours | Platform engineering | 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.<br>A patch closes the hole but does not remove persistence left by someone who already had root. | Which nodes were rebuilt, from which backup, and the date. |
| 24 to 72 hours | Security lead | 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.<br>Whoever had root can read every secret the system uses to talk to other systems. | Each secret, its owner, the rotation date, and the dependent system tested. |
| 24 to 72 hours | Application owner | 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.<br>Rotations and ACLs break integrations quietly, and a new policy or account is how a bypass turns into lasting access. | Test list with result, and the list of new accounts and policy changes with owner confirmation. |

Print this table as the checklist: write the time each step was done in the record column.

## 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.

| When | What happened | Source |
| --- | --- | --- |
| 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](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5) |
| 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](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5) |
| 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](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-76460) |
| 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](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-76460) |
| 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](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5) |
| 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](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5) |
| 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](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-76460) |

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.

## Related pages

- [Container base image playbook: the first 72 hours when a flaw is in the image your services build on](/playbooks/container-base-image/)
- [The network edge appliance playbook for the first 72 hours](/playbooks/network-edge-appliance/)
- [SaaS vendor playbook: the first 72 hours when the flaw is in a service you cannot patch](/playbooks/saas-vendor/)

## Sources

- Cisco Security Advisory cisco-sa-ISE-ABP-VNSW7Tn5: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ISE-ABP-VNSW7Tn5 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-76460: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-76460 (read 19 Nov 2026)
- NVD record for CVE-2026-76460: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-76460 (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://zerodayplaybook.com/playbooks/network-access-control/
