Notifications
Clear all
Topic starter
18/08/2026 2:33 pm
TL;DR: IAM reviews can confirm assigned permissions without revealing what sensitive data those permissions can actually reach, especially when AI agents inherit broad access across multi-hop data pipelines, according to Sentra. The real governance gap is lineage, because dormant service identities and ghost agents can quietly preserve exposure long after the original use case disappears.
NHIMG editorial — based on content published by Sentra: Lineage-aware IAM is exposing ghost agents and hidden data reach
By the numbers:
- 97% of non-human identities carry excessive privileges, according to Entro Security's 2025 research.
Questions worth separating out
Q: What breaks when IAM only reviews permissions and not data reachability?
A: Teams can approve a role or service account while still missing the sensitive data it can reach through pipelines, inheritance, or downstream systems.
Q: Why do ghost agents increase NHI risk more than ordinary dormant accounts?
A: Ghost agents are risky because they remain authenticated, can still hold live access, and often sit outside normal human lifecycle cues like leave events or recertification prompts.
Q: How can security teams tell whether an identity is actually overexposed?
A: Look for identities whose permitted path reaches regulated or customer data through multiple systems, even when the direct role assignment seems modest.
Practitioner guidance
- Inventory dormant service identities and ghost agents Search for non-human identities that still authenticate but no longer have a current business owner, active project, or documented purpose.
- Map reachable data, not just assigned permissions Trace each identity from its role or service principal through pipelines, storage, and retrieval layers to the sensitive data it can actually surface.
- Add decommission triggers for AI agents and service accounts Require explicit offboarding when a project ends, a data source changes, or an identity has not executed a validated business task within its intended lifecycle.
What's in the full article
Sentra's full article covers the operational detail this post intentionally leaves for the source:
- Lineage-aware access mapping examples that trace identity reach across Snowflake, Databricks, S3, and agent-facing retrieval layers
- The article's practical framework for distinguishing assigned access from actually reachable sensitive data
- Specific examples of ghost-agent style exposure and how the vendor proposes to surface them in live environments
- The way Sentra maps human and machine identities to sensitive data reach in practice
👉 Read Sentra's analysis of lineage-aware IAM and ghost agents →
Ghost agents and hidden data reach: what IAM teams are missing?
Explore further
18/08/2026 3:20 pm
Lineage is now the decisive control gap in IAM. Permission review still matters, but it is no longer enough to prove security when identities can reach sensitive data through chained systems and inherited access. The discipline has shifted from asking who can read a resource to asking what that identity can actually expose in context. Practitioners should treat reachable data as the real unit of governance.
A few things that frame the scale:
- 97% of non-human identities carry excessive privileges, according to the 2026 Infrastructure Identity Survey.
- 59.8% of organisations see value in a solution that simplifies non-human access management and introduces dynamic ephemeral credentials, according to The 2024 Non-Human Identity Security Report.
A question worth separating out:
Q: Should organisations treat agent access reviews the same as human access reviews?
A: No. Human reviews focus on role, business need, and employment status, while agent reviews must also cover tool scope, credential inheritance, and downstream action paths. The review object is not just the agent itself but the full execution chain it can initiate. That distinction matters because agent behaviour can change faster than a standard recertification cadence can capture.
👉 Read our full editorial: Lineage-aware IAM is exposing ghost agents and hidden data reach
