Reachable Attack Surface

The subset of assets that a compromised identity can actually touch in practice. Unlike a theoretical asset inventory, this definition focuses on what the attacker can access through existing permissions, network paths, and application links, making it a practical measure for IAM and PAM prioritisation.

Expanded Definition

Reachable attack surface is the portion of an environment that a compromised NHI, service account, or AI agent can actually reach through current permissions, trust relationships, network routes, and application dependencies. It is narrower and more operational than a full asset inventory, because it reflects the paths an attacker can use after an identity is abused rather than every asset that exists.

In NHI governance, this term helps teams separate exposure from accessibility. A token may be present in a vault, but if no workload can retrieve it, it is not part of the reachable attack surface from the attacker’s perspective. That distinction matters for prioritising least privilege, PAM hardening, segmentation, and token scope reduction. Definitions vary across vendors when agentic systems are involved, because some count only direct API permissions while others also include downstream systems reached through orchestration chains. For broader NHI risk context, see NHIMG’s Ultimate Guide to NHIs — Key Challenges and Risks and the Top 10 NHI Issues. External models such as NIST SP 800-53 Rev 5 Security and Privacy Controls remain relevant for access control and boundary protection.

The most common misapplication is treating reachable attack surface as a static inventory problem, which occurs when teams count assets but ignore the live permission paths that a compromised identity can traverse.

Examples and Use Cases

Implementing reachable attack surface analysis rigorously often introduces operational friction, because shrinking real access paths can slow deployment workflows and require tighter change control, but it materially improves prioritisation.

• An AI agent has read access to customer support records and a tool connection to a ticketing system. The reachable attack surface includes both the records and any linked workflow actions the agent can trigger, not just the source database.
• A compromised CI/CD service account can read deployment secrets and write to a container registry. The actionable surface is the registry, the secret retrieval path, and any environments that trust the published image.
• A cloud workload identity can call only three APIs, but one of them can assume a secondary role. The reachable attack surface expands through the role chain, which is why transitive trust must be mapped.
• NHIMG’s AI Agents: The New Attack Surface report shows why this matters: 80% of organisations report agent actions beyond intended scope, including unauthorised system access and credential exposure.
• For attacker behaviour patterns, CISA cyber threat advisories and the MITRE ATT&CK Enterprise Matrix help teams model how compromise moves through reachable paths.

Why It Matters in NHI Security

Reachable attack surface is the practical lens for deciding which NHIs need remediation first. If a service account has broad permissions but no reachable path to sensitive systems, its risk is lower than an apparently smaller identity that can pivot into production, secrets stores, or AI toolchains. This is why the concept is central to privilege review, network segmentation, identity federation, and agent governance.

It also prevents false confidence. Many organisations assume that secret storage or approval gates are enough, yet NHIs are often compromised through chained permissions, exposed tokens, or over-privileged automation. NHIMG research on 52 NHI Breaches Analysis and the Ultimate Guide to NHIs shows that attackers routinely exploit identity paths rather than isolated assets. When AI agents are involved, the exposure becomes harder to see, and only 52% of companies can track and audit the data their AI agents access, leaving 48% with a blind spot for investigation.

Organisations typically encounter the damage only after lateral movement, secret abuse, or unauthorised agent behaviour has already occurred, at which point reachable attack surface becomes operationally unavoidable to address.

Related resources from NHI Mgmt Group

• Attack Surface Management
• Why does Agentic AI make NHI attack surface expand so significantly?
• What is the difference between attack surface management and NHI governance?
• Why do NHIs create a larger attack surface than human users?