Network segmentation as a compensating control
Cisco's advisory of 16 Sep 2026 for ISE CVE-2026-76460 (CVSS 10.0) lists no workaround and one mitigation: infrastructure ACLs that allow only required management and control plane traffic to the ISE nodes. That is network segmentation. It narrows which networks reach the API and leaves the flaw in place until a fixed patch is installed.
On this page
What segmentation is in the standards' words
CISA names it for assets that cannot be updated in time: "Depending on your environment, appropriate isolation techniques may include decommissioning, removal of the vulnerable software product, network segmentation, isolation, software-defined perimeters, and proxies." (BOD 26-04 implementation guidance, read 19 Nov 2026.) NIST SP 800-40 Rev. 4 lists it under the Mitigate response: "using firewalls and network segmentation to isolate vulnerable assets, thus reducing the attack surface" (section 2.1), and for unpatchable assets points to micro-segmentation and software-defined perimeters in SP 800-207 (section 3.5.4) (SP 800-40 Rev. 4, read 19 Nov 2026).
SP 800-53 Rev. 5.2.0 gives the control text. SC-7 b: implement subnetworks for publicly accessible system components that are separated from internal organizational networks. SC-7(5): "Deny network communications traffic by default and allow network communications traffic by exception". SC-7(21): "Employ boundary protection mechanisms to isolate" the components the organization names; its discussion says isolation "provides the capability for increased protection of individual system components and to more effectively control information flows between those components." (NIST OSCAL catalog of SP 800-53 Rev. 5.2.0, last modified 22 Oct 2026, read 19 Nov 2026.)
When segmentation counts as a mitigation
| It counts when | It does not count when |
|---|---|
| The vendor or CISA names an access or ACL control, as Cisco does for ISE, and your rule is the one described. | The rule exists only on a diagram, or exists but a second path (another VLAN, a VPN pool, a management network) still reaches the component. |
| The attacker's starting point is a network position the rule removes, such as the user or guest VLAN. | The attacker is already inside the allowed set: an admin workstation, another node, a compromised integration server. |
| Rules are deny by default, with each allowed source listed and owned. | The rule is allow any with a few exceptions, so the allowed set is larger than anyone has counted. |
| The flaw is reached over the network. Cisco's CVSS vector for CVE-2026-76460 is network, no privileges, no user interaction. | The flaw is triggered on the host, through a file or document, or through a service the segment must keep open. |
Worked case: Cisco ISE CVE-2026-76460
Cisco Identity Services Engine and ISE-PIC have an API endpoint with insufficient authentication control. An unauthenticated attacker can bypass authentication, and Cisco says a successful attacker may obtain root privileges. Cisco published the advisory (cisco-sa-ISE-ABP-VNSW7Tn5) on 16 Sep 2026, states its PSIRT is aware of active exploitation, and gives first fixed releases of 3.1 Patch 12, 3.2 Patch 11, 3.3 Patch 12, 3.4 Patch 7 and 3.5 Patch 4. Release 3.0 has reached end of software maintenance, and Cisco advises migrating to a supported release. CISA added the CVE to KEV the same day with a due date of 19 Sep 2026 and a forensic triage requirement (Cisco advisory, CISA KEV feed 2026.11.18, read 19 Nov 2026).
On workarounds Cisco writes: "There are no workarounds that address this vulnerability. However, there is a mitigation. To prevent remote exploitation of this vulnerability, use infrastructure access control lists (iACLs) to allow only required management and control plane traffic that is destined to the affected device." It adds that it "considers any workarounds and mitigations (if applicable) to be temporary solutions until an upgrade to a fixed software release is available." The setting is therefore an allow list on the network path to each ISE node, with everything else denied. The advisory gives no port list; the allowed set is yours to inventory. Cisco's advisory does not use the word segmentation. An ACL on the path decides which networks may reach the nodes, so the case sits here. Access restriction covers the other question, which identities and addresses may call a component, and works that through on the PAN-OS flaw CVE-2026-0322.
CISA's SSVC data in NVD rates the flaw automatable and total impact, which is row 1 of BOD 26-04 Table 1 for an exposed asset: 3 days with forensic triage. Segmentation does not change that row unless it also removes public reachability, and even then row 9 is also 3 days with forensic triage, so the due date stays 19 Sep 2026. Removing internet exposure shows which rows move.
What Cisco says to look for in access.log
The ACL does nothing about a node that was already reached. Cisco's advisory gives this under Indicators of Compromise (read 19 Nov 2026):
- Review access.log for suspicious usernames, on every node if the deployment is distributed.
- Cisco's non-exhaustive example, run at the ISE CLI:
admin#show logging application ise-kong/access.log | include dummyuser, where dummyuser stands in for a suspicious username. - For more access.log files, collect a support bundle with include debug logs selected and shared key encryption, then decrypt it and find the log at
./ise/logs/apigateway/access.log.gz. - Cisco: "The presence of any entry in the output may indicate malicious activity." If activity is suspected, Cisco strongly recommends re-imaging the affected nodes and restoring from a configuration backup if needed.
- On success the attacker may hold root, so evidence on the node may be removed or hidden. Cisco recommends cross-checking network and firewall logs outside the device for unexpected uploads from the node to external IP addresses and downloads from malicious IP addresses. The advisory lists no indicator addresses.
What the ACL costs
- Anything that talks to ISE from a network you did not list loses access. Inventory the callers first: administrator workstations or a jump host, the other ISE nodes in the deployment, the network devices that send authentication requests, and any integration server. An omission is an outage on the network access control system itself.
- A change window and a rollback copy of the ACL on every device in the path, since a wrong deny cuts the system that decides who may join the network.
- Ongoing ownership. The allowed list drifts when a new site, device group or integration appears; each addition is a change ticket against this entry.
- Cisco states the limit plainly in its own terms: the ACL is temporary until the upgrade, and a compromised allowed source can still reach the API.
A dated plan for a three-node deployment
Illustration: ISE 3.4 at a patch level below Patch 7, three nodes, one admin jump host. Rows marked plan are choices for the example. The 17 Sep ACL leaves the nodes on the network and reachable from the jump host, the network devices and each other, so it is not removal from the network. CISA's guidance says that if the required action cannot be done in the timeframe, "remove the asset from the agency network", and names network segmentation among isolation techniques only for that purpose. This plan therefore does not treat the ACL as meeting the 19 Sep date, and the patch row below is marked late.
| Date | Event or plan | Record produced |
|---|---|---|
| 16 Sep 2026 | Event: Cisco advisory published, KEV entry added, due 19 Sep 2026. Plan: caller inventory started from firewall and ACL logs | Inventory sheet with owner per source |
| 16 Sep 2026, later | Plan: allow list agreed with the network team; change ticket opened | Draft ACL, ticket, approver |
| 17 Sep 2026 | Plan: ACL applied on the device in front of the nodes; reachability checked from the user VLAN, the guest network and the jump host | ACL export, dated; check results per vantage point |
| 19 Sep 2026 | Event: KEV due date. Plan: forensic triage done with the access.log review above; Patch 7 window booked | Triage ticket, patch ticket |
| 26 Sep 2026 | Plan: 3.4 Patch 7 installed on all three nodes and confirmed with show version. This is 7 days after the 19 Sep due date, so for an agency under BOD 26-04 it is late and the ACL does not excuse it; a non-federal operator records it as the end of the temporary control | Version output per node |
| 3 Oct 2026 | Plan: ACL narrowed back to its standing form or removed, as the ticket says | Closing entry |
How to verify the boundary
- Export the rule set from the device that enforces it and date the export. Confirm the final rule is a deny and that no earlier rule widens the allowed set.
- Check reachability of each ISE node's management and API interfaces from a user VLAN, a guest network and any internet-facing network you own, and from one allowed source. Record who could connect and who could not. This is a connection test of your own addresses, not a test of the flaw.
- Compare the result with the inventory. Every allowed source should connect; every other source should not.
- Review firewall logs for denied connection attempts to the nodes; they show callers you missed and traffic you meant to stop. Keep the outside-the-node log check from the access.log section with this record.
- Repeat after every change to the path.
What to record
Network segmentation entry
- Finding: CVE-2026-76460, ISE version and patch level per node
- Source of the control: Cisco advisory cisco-sa-ISE-ABP-VNSW7Tn5 (iACL mitigation), read 19 Nov 2026
- Boundary device and rule set name; export with date
- Allowed sources, each with an owner and a reason
- Reachability check: vantage points, date, tester, result
- Known gaps: sources inside the allowed set; other paths to the nodes
- Change ticket, approver, rollback copy
- Forensic triage ticket (KEV entries marked yes)
- Fix date, review date, and the date the entry is retired
SP 800-40 Rev. 4 says to plan to replace emergency mitigations with permanent fixes and to set schedules for both patch deployment and mitigation removal. Retire the entry when the fixed patch is confirmed on every node. If the ACL is kept, rename it as standing hardening so it is not mistaken for the temporary control. For callers narrowed by identity rather than network, see access restriction, and verification steps are in how to verify a mitigation works.
Sources
- Cisco security advisory cisco-sa-ISE-ABP-VNSW7Tn5 (vendor): workarounds, fixed releases, indicators, read 19 Nov 2026
- CISA KEV JSON feed, catalog 2026.11.18: CVE-2026-76460, read 19 Nov 2026
- NVD record for CVE-2026-76460 (CVSS vector, CISA ADP SSVC data), read 19 Nov 2026
- CISA BOD 26-04 implementation guidance, FAQ on alternative mitigation (remove the asset from the agency network; isolation techniques), read 19 Nov 2026
- CISA BOD 26-04, Appendix A, Table 1, read 19 Nov 2026
- NIST SP 800-40 Rev. 4, sections 2.1, 3.5.3 and 3.5.4, read 19 Nov 2026
- NIST SP 800-53 Rev. 5.2.0 OSCAL catalog (last modified 22 Oct 2026): SC-7, SC-7(5), SC-7(21), read 19 Nov 2026
Last reviewed