Active Directory risk meets AI speed in the Mythos era

At a glance

What this is: This is an analysis of how AI-speed vulnerability discovery is widening the gap between Active Directory exposure and human-paced governance.

Why it matters: It matters because IAM, PAM, and security teams need controls that reduce trust paths and lateral movement before attackers reach identity systems, not after patch queues clear.

By the numbers:

• Cloudflare found 2,000 vulnerabilities, including 400 rated high or critical severity.

Context

Active Directory risk is a governance problem as much as a technical one. It persists because trusted relationships, elevated permissions, and legacy dependencies accumulate faster than teams can untangle them, especially when cloud, mergers and acquisitions, vendors, and remote access all expand the trust surface.

AI changes the timing, not the underlying attack path. Illumio frames Mythos as a speed multiplier for familiar intrusion chains, which makes identity containment, privilege mapping, and lateral-movement control more urgent than assuming patch cadence can keep pace.

Key questions

Q: How should teams reduce Active Directory risk when AI speeds up exploitation?

A: Teams should assume patching will lag and focus on reducing the routes attackers can use to reach identity systems. That means mapping trusted relationships, removing unnecessary privilege, and containing lateral movement so an initial foothold cannot quickly become directory control.

Q: Why do trusted relationships make Active Directory so hard to defend?

A: Trusted relationships turn ordinary connectivity into an access path, so attackers can move from one system to another without obvious alarms. In large environments, those paths accumulate across cloud, vendors, remote access, and mergers, creating more reach than administrators usually expect.

Q: What are the signs that Active Directory containment is failing?

A: The warning signs are expanding privilege paths, overconnected systems, and remote access routes that can still reach identity infrastructure after a compromise. If a low-level foothold can move laterally toward domain control, containment is not working well enough.

Q: Should organisations prioritise segmentation or patching first for Active Directory risk?

A: Patching remains necessary, but segmentation should rise when exploit windows are shrinking and the environment cannot be remediated fast enough. If you cannot patch every exposure quickly, limiting where an attacker can travel becomes the more dependable way to reduce impact.

Technical breakdown

Why AI speed changes Active Directory exposure

AI-assisted vulnerability discovery shortens the time between exposure and exploitation, which matters because Active Directory environments are rarely simple or static. They contain inherited trust, privileged groups, service dependencies, and cross-domain access that take time to map and change. The issue is not that AI invents a new path into AD. It compresses the defender's decision window until old assumptions about review, testing, and staged remediation become harder to rely on. When attackers can move from discovery to abuse in hours, control effectiveness depends on what can be contained before patching completes.

Practical implication: prioritise containment and path reduction for the AD relationships most likely to be reached first.

How trusted relationships become the route to identity systems

Attackers usually do not attack Active Directory in a single jump. They move through trusted relationships between users, systems, applications, and domains until they reach identity infrastructure with broad authority. That makes trust mapping a core security function, not just an architecture exercise. In practice, many environments have more implicit trust than documentation suggests, especially where remote access, vendor connectivity, and cloud integrations overlap. Once those paths exist, privilege escalation becomes less about exotic exploitation and more about finding the shortest route to the accounts that unlock everything else.

Practical implication: maintain current trust-path maps and use them to prune unnecessary routes into privileged identity systems.

Why lateral movement controls matter more than perfect patching

The article's central operational point is that teams cannot patch everything fast enough when exploit development is moving at machine speed. That shifts the centre of gravity toward limiting lateral movement, understanding which privileged accounts still matter, and reducing the blast radius if an attacker gets in. Microsegmentation and segmentation are not replacements for remediation, but they buy time by constraining how far an intruder can travel while governance teams work through change control and validation. In AD-centric environments, that containment window is now a primary control objective.

Practical implication: treat lateral movement reduction as a standing control objective alongside patching and access review.

Threat narrative

Attacker objective: The objective is to reach Active Directory-level control so the attacker can unlock and manipulate enterprise-wide access.

1. Attackers gain a foothold through an initial vulnerability or exposed path, then use the resulting access to probe trusted connections toward identity infrastructure.
2. They move laterally through users, systems, applications, and domains until they reach Active Directory or other privileged identity services.
3. Once inside identity infrastructure, they escalate privileges and can hijack broader enterprise access, turning a local compromise into environment-wide control.

Breaches seen in the wild

• Cisco Active Directory credentials leak 2025: Kraken leaked Cisco Active Directory hashes, including service and krbtgt accounts; Cisco says they came from its 2022 breach, not a new one.
• SonicWall SSL VPN account compromises 2025: Attackers used valid credentials to log in to more than 100 SonicWall SSL VPN accounts across 16 environments in October 2025.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Machine-speed discovery exposes a human-speed governance gap: Active Directory risk does not become more severe because the architecture changed, but because the defender's operating tempo no longer matches attacker tempo. Patch testing, approval, and rollout still take human time, while AI-assisted discovery compresses the abuse window. The implication is that governance based on remediation cadence alone is no longer sufficient for identity infrastructure.

Trust-path visibility is now the real control surface: The article shows that attackers usually reach Active Directory by following trusted relationships, not by attacking identity systems in isolation. That makes trust mapping the decisive security lens because the shortest path to privilege is often hidden inside routine connectivity. Practitioners should treat invisible trust as a control failure, not a documentation issue.

Identity blast radius is the concept this article sharpens: In an AD-heavy environment, the main question is not whether compromise is possible, but how far it can spread before containment stops it. That shifts the discipline from patch-only thinking to limiting the reachable privilege surface. The practitioner conclusion is simple: contain the path, or the path becomes the compromise.

Active Directory is a concentration point for enterprise trust: Once attackers reach AD, they can often inherit the access relationships that hold the environment together. That is why identity governance, segmentation, and privilege control cannot be managed as separate programmes. The implication for security architects is to align identity containment with the trust topology of the business, not with directory administration alone.

Speed changes the value of prevention versus containment: When exploitation timelines shrink from months to hours, the highest-value control is often the one that still works after a foothold exists. This does not diminish patching, but it does re-rank controls that slow movement and shrink impact. Teams should assume that some weaknesses will be exposed before they are fixed and govern accordingly.

What this signals

Identity blast radius is the right planning unit: Active Directory programmes should be judged by how much trust remains reachable after compromise, not by whether every known flaw is already patched. When AI accelerates exploitation, the practical question becomes how much of the directory still needs to be reachable for business to function.

In that environment, segmentation, privilege scoping, and trust-path reduction are not separate initiatives. They are the controls that determine whether a discovered weakness becomes an enterprise-wide event or a contained incident.

For practitioners

• Map the shortest paths into Active Directory Identify which users, systems, applications, and vendor connections can reach privileged identity assets, then remove any route that is not required for operations.
• Inventory and tighten privileged access List every account with elevated permissions, confirm where it can authenticate, and verify that each privilege is still needed for current business use.
• Reduce lateral movement opportunities Use segmentation to separate routine workloads and remote access paths from the identity systems that control the rest of the estate.
• Prioritise containment for exposed identity services Assume some vulnerabilities will remain unpatched during rapid exploit windows, and build response plans that isolate identity systems before an attacker can expand reach.

Key takeaways

• AI-speed vulnerability discovery compresses the time defenders have to protect identity systems, which makes Active Directory governance a timing problem as well as a technology problem.
• The article's evidence points to a world where attackers move through trusted relationships toward directory control faster than human-paced remediation can keep up.
• Reducing reachable privilege and limiting lateral movement are the controls most likely to change outcomes when patch windows are no longer the defender's main advantage.

Key terms

• Identity Blast Radius: The amount of damage a compromised identity can cause across systems, data, and infrastructure. In NHI environments, it is shaped by permissions, network reach, and administrative capability rather than by the credential alone. Reducing blast radius is a containment strategy that limits lateral movement and data exposure.
• Trust Path: A trust path is the sequence of systems a request passes through before identity controls or service access complete. It includes resolution, routing, verification, and policy enforcement, so weak controls anywhere in the path can undermine the assurance of the final access decision.
• Lateral Movement: A post-compromise technique where an attacker uses a compromised NHI to move through a network, accessing additional systems and escalating impact without triggering detection.
• Attack Path Reduction: Attack path reduction is the practice of removing the specific combinations of identity, privilege, and infrastructure that let an attacker move from initial access to business impact. It focuses on reachable compromise routes rather than isolated vulnerabilities or theoretical risk.

Deepen your knowledge

NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.