Zero Trust still fails when teams ignore containment and blast radius

At a glance

What this is: Illumio says zero trust breaks down when teams treat it as a policy label rather than an operating model built around containment and blast-radius control.

Why it matters: For IAM, PAM, NHI, and broader security teams, the lesson is that access decisions matter less if compromised access can still spread unchecked across systems and workloads.

Context

Zero trust is often described as a strategy for limiting implicit trust, but in practice it only works when containment is built into the operating model. The security problem here is not the label itself, but the gap between authentication and what happens after access is granted across users, services, and workloads.

The article sits squarely in the identity and access governance space because blast-radius reduction depends on how access is structured, monitored, and constrained once a compromise occurs. That makes the topic relevant to IAM, PAM, and NHI programmes, especially where machine identities and lateral movement are part of the exposure path.

Key questions

Q: What fails in a zero trust programme when containment is missing?

A: Zero trust fails when teams stop at verification and never define what a compromised identity is allowed to reach. Authentication may still work, but the environment remains vulnerable to lateral movement, excessive privilege spread, and operational disruption because post-access boundaries are weak or absent.

Q: Why does blast radius matter more than authentication alone?

A: Because authentication answers only whether access was granted, while blast radius shows how much damage that access can cause once abused. In practice, a valid credential with broad reach is often more dangerous than a poorly defended perimeter, especially in hybrid estates with many machine identities.

Q: What are the signs that containment controls are failing in a modern environment?

A: The warning signs are broad lateral movement paths, shared admin accounts, persistent service credentials, and critical systems that sit close to routine user or developer environments. If a compromise in one area can quickly reach many others, containment is too weak. The environment is behaving like one flat trust zone rather than separated control domains.

Q: How should security teams prepare for autonomous AI attacks that move at machine speed?

A: Security teams should map the full AI attack surface, including data pipelines, agent orchestration, APIs, identities, and third-party dependencies. They should test complete attack paths, not isolated controls, and validate that detection and response can run continuously outside business hours. Clear authorization boundaries are also essential so autonomous actions that exceed policy can be stopped or reviewed.

Technical breakdown

Why containment is the operational core of zero trust

Zero trust is not just about denying access at the edge. It is about assuming that some access will eventually be granted or stolen, then designing controls so a compromise cannot move freely across the environment. Containment turns trust into a bounded condition, using segmentation, least privilege, and policy enforcement to limit what any user, service, or workload can reach. Without that layer, zero trust becomes a set of authentication checks with no meaningful protection after compromise. The architecture succeeds or fails on post-access containment, not on slogans about verification.

Practical implication: teams should measure zero trust by how well they confine compromised access, not by how many login controls they have.

How blast radius changes the identity security question

Blast radius describes the amount of damage a compromised identity can cause before it is contained. In IAM and NHI environments, that question matters because a valid credential does not equal safe access. Service accounts, tokens, and delegated access often have paths wider than their owners expect, especially in hybrid estates where permissions accumulate across systems. If those paths are not constrained, an attacker or rogue process can pivot from a single identity into broader access. The governance problem is therefore not only who can authenticate, but how far authenticated access can travel.

Practical implication: inventory identity paths that can pivot laterally and constrain the highest-risk access routes first.

Why AI raises the pressure on resilience, not the need for new fundamentals

AI changes the speed and scale of attack activity, but it does not remove the need for basic security physics. Faster reconnaissance, more convincing phishing, and more automated misuse all increase the odds that an adversary gets a foothold, which makes containment more valuable, not less. That is especially true where non-human identities are used by automation, integrations, and AI-driven workflows. Those identities can create broad execution paths if they are not tightly scoped and monitored. The core governance challenge is to make sure resilience does not depend on perfect prevention.

Practical implication: treat AI-driven attack pressure as a reason to harden containment controls around both human and non-human identities.

Threat narrative

Attacker objective: The attacker objective is to move from initial foothold to wider environment impact by exploiting weak containment and excessive reachable access.

1. Entry occurs when an attacker gains a foothold through a valid identity or compromised access path rather than by defeating every control up front.
2. Privilege use expands when that foothold is able to reach more systems than intended because access was not sufficiently contained.
3. Impact follows when the compromise spreads across the environment, turning one incident into a broader operational disruption or ransomware event.

Breaches seen in the wild

• New York Times GitHub breach 2024: An exposed GitHub token gave an attacker The New York Times' repositories; the 270GB leak held 4,875 unique secrets.
• HPE Aruba Instant On hard-coded credentials: Hard-coded admin credentials in HPE Aruba Instant On access point firmware let anyone bypass login (CVE-2025-37103); no exploitation reported.

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

Containment is the missing control plane in many zero trust programmes. Organisations often adopt authentication and policy language without building the operational boundary that limits what a compromised identity can actually do. That leaves the environment vulnerable to spread even when the front door is technically guarded. The practical conclusion is that zero trust must be judged by containment outcomes, not implementation labels.

Blast-radius control is the real test of identity governance. IAM and PAM can prove who received access, but they do not automatically prove how far that access can travel once misused. In NHI-heavy environments, that distinction becomes critical because tokens, service accounts, and delegated credentials can be abused at machine speed. Practitioners should treat reachable scope as a first-class governance metric.

Non-human identities make zero trust more brittle if lifecycle control is weak. The more automation and AI workflows depend on machine identities, the more damage a single overly broad credential can cause. That is not an argument against automation; it is an argument for stronger issuance, scoping, and offboarding discipline. The programme implication is simple: unmanaged NHI reach turns resilience into an afterthought.

AI does not rewrite the zero trust model, but it does punish shallow implementations. Faster attack cycles make delayed containment more costly and more visible. If teams still rely on perimeter assumptions or broad privilege grants, AI accelerates the failure rather than causing it. The market signal is that containment, segmentation, and identity scope are converging as the same governance problem.

From our research library:

• 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation, according to the Ultimate Guide to NHIs.
• By 2029, 40% of enterprises that successfully implement zero trust within cloud service provider environments will rely on the advanced visibility and control capabilities offered by CNAPP solutions.
• Read next: Zero Trust Identity Guide

What this signals

Blast-radius control should be treated as a governance metric, not an architecture slogan. If a compromised identity can still cross critical boundaries, the programme has not translated zero trust into operational containment.

Zero Trust Identity Guide remains the right lens for teams that need to connect access policy with enforcement boundaries. The point is not more authentication, but less reachable impact when trust is misplaced or stolen.

NHI programmes in particular should assume that machine identities will be targeted for their reach, not just their existence. The practical response is to reduce what those identities can touch before an incident proves the point.

For practitioners

• Define blast radius as a control objective Measure how far a compromised identity, token, or workload can move across production systems, then set reduction targets for the highest-risk paths.
• Map lateral movement paths for NHIs Identify service accounts, APIs, and automation credentials that can reach multiple environments, and prioritise the ones with the widest reachable scope.
• Constrain post-authentication reach Use segmentation and privilege scoping so that successful authentication does not translate into broad east-west movement or uncontrolled workload access.
• Review resilience assumptions for AI-enabled workflows Check whether agentic or automated processes can be paused, isolated, or revoked quickly enough if their credentials or behavior are compromised.

Key takeaways

• Zero trust programmes fail when they stop at access verification and do not limit how far a compromised identity can travel.
• The most useful governance metric is blast radius, because it captures the damage a valid credential, token, or workload can cause after misuse.
• Containment, segmentation, and narrow identity scope are the controls that turn zero trust from a policy statement into resilience.

Key terms

• Blast Radius: The potential scope of damage if a specific credential or identity is compromised. Identities with broad permissions have a larger blast radius and represent a higher priority for least-privilege enforcement and security controls.
• Containment: The phase of incident response that stops an incident from spreading while preserving the evidence needed to investigate it. In cloud environments, containment often starts with identity revocation, isolation of workloads, and protection of logs before any system is terminated or cleaned up.
• Zero Trust: A security model that assumes no identity, human or non-human, should be trusted by default, even inside a network perimeter. Every access request must be verified, authorised, and continuously validated.
• Non-Human Identity (NHI): A digital identity assigned to a non-human entity such as a software application, service account, API key, bot, machine, or AI agent that enables it to authenticate and interact with systems without direct human involvement. NHIs now outnumber human identities in most enterprises by 25 to 50 times.

Deepen your knowledge

NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security, and secrets management. It helps practitioners connect identity controls to the containment decisions that reduce blast radius.