Topic starter
10/07/2026 9:28 pm
TL;DR: Lateral movement prevention is an architectural problem, not a tooling problem, according to Elisity, as credential abuse remains the top initial access vector in 22% of breaches and compromised-credential incidents take 246 days to identify and contain. In AI agent environments, identity separation and east-west containment must be designed in, because the old human-plus-service-account model no longer matches runtime reality.
Editorial analysis by NHI Mgmt Group, based on content published by Elisity: “Andy Ellis on How to Prevent Lateral Movement in the Age of AI Agents”.
By the numbers:
- Credential abuse is now the single most common initial access vector, used in 22 percent of breaches.
- Breaches involving compromised credentials took an average of 246 days to identify and contain in 2025.
Key questions
Q: What breaks when an attacker can move laterally with valid credentials?
A: The failure is that internal authentication no longer proves legitimacy.
Q: Why do AI agents make lateral movement harder to contain?
A: AI agents add more runtime identities to the same endpoint and can act faster than human review cycles.
Q: How do security teams know if lateral movement defences are actually working?
A: Teams should test whether one compromised identity can reach adjacent systems, SaaS apps, or production zones that it should not access.
Practitioner guidance
- Map identity blast radius per actor Define the maximum reachable scope for each human, service account, and AI agent identity, then compare it to actual business need.
- Enforce east-west segmentation by identity Apply policy so internal systems are not broadly addressable just because they are on the same network.
- Separate AI agents from human and service identities Treat AI agents as distinct runtime identities when they can initiate actions or reach tools independently.
Bottom line: Lateral movement remains the step where a local compromise becomes a broader incident, so containment has to be architectural rather than reactive.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
10/07/2026 9:51 pm
Lateral movement prevention is an architectural objective, not a tooling outcome: The control failure here is not the absence of a single product feature. It is the assumption that detection and response can compensate for an environment that still allows compromised identities to move freely. When identity, segmentation, and enforcement are designed separately, the attacker inherits the joins between them. Practitioners should treat containment as a property of architecture, not a post-breach hope.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between microsegmentation and a proxy boundary for legacy assets?
A: Microsegmentation limits which identities can reach an asset, while a proxy or policy enforcement boundary controls and mediates the traffic itself. They solve different parts of the same problem. Together, they reduce direct reachability and make it harder for compromised identities to talk laterally to protected devices.
👉 Read our full editorial: AI agent identity and lateral movement: why architecture fails