SailPoint’s Entro acquisition signals a shift in NHI governance

At a glance

What this is: This is an analysis of SailPoint’s planned acquisition of Entro and its implications for NHI and AI agent governance.

Why it matters: It matters because identity teams need to understand how discovery, ownership attribution, and runtime protection change when machine and agent identities become first-class governance targets.

By the numbers:

• This unified capability brings out-of-the-box coverage for over 1,000 NHI and agent types, plus the discovery of over 1,200 non-human identity types.
• Covering more than 70 critical enterprise sources across cloud environments, CI/CD pipelines, and developer tools, the platform extends governance into the systems where machine identities operate.

👉 Read SailPoint’s blog on its planned Entro acquisition and AI agent governance

Context

Non-human identity governance has moved beyond simple secret inventory. As AI agents, API connections, and cloud workflows take on more access, the problem shifts to proving what each actor can do, what it touched, and who owns it across the identity lifecycle.

SailPoint’s planned acquisition of Entro is framed around that governance gap, especially for environments where discovery, context, and runtime monitoring must line up. For identity programmes, the question is no longer whether machine identities exist. It is whether they are visible, attributable, and bounded in ways that survive real operational complexity.

Key questions

Q: How should security teams govern non-human identities that span cloud, CI/CD, and developer tools?

A: Security teams should govern non-human identities by mapping each credential to an owner, an approved purpose, and a defined operational boundary. Then they should connect discovery to entitlement review and runtime monitoring so access is not just visible but also enforceable across cloud, CI/CD, and developer tooling.

Q: Why does ownership attribution matter for machine identity risk?

A: Ownership attribution matters because a discovered token or key is not governable until someone is accountable for it. Without a named owner, certification, remediation, and offboarding become process artifacts with no enforcement path, which leaves blast radius and escalation risk unresolved.

Q: What do security teams get wrong about NHI discovery?

A: Teams often treat discovery as the end state when it is only the first step. A complete inventory without relationships, permissions, and usage context cannot show risk, because the same identity may be harmless in one workflow and highly exposed in another.

Q: Who should be accountable when a machine identity is over-privileged?

A: Accountability should sit with the human owner of the identity and the team that approved its operational scope. Governance fails when machine access is treated as ownerless infrastructure, because every privileged credential still exists inside a business process that can be reviewed and corrected.

How it works in practice

Why discovery alone is not enough for NHI governance

Discovery tells you that a machine identity exists, but it does not tell you what that identity can reach, which secrets it uses, or how far its access can spread. In practice, NHI governance needs relationship mapping across tools, APIs, certificates, tokens, and cloud services, because the same credential can behave very differently depending on where it is used. Without context, inventory becomes a static list rather than an enforceable control surface.

Practical implication: treat discovery as an input to governance, not the control itself.

How blast radius and ownership attribution change machine identity risk

Blast radius is the practical measure of how much damage follows from a compromised or over-privileged identity. Ownership attribution links that identity back to a human accountable for approval, review, and remediation. For NHI programmes, the two have to travel together, because a discovered token with no owner and no mapped dependencies is already outside meaningful governance. That is where access certification, lineage, and entitlement context become operational rather than administrative.

Practical implication: require every NHI to resolve to an owner and a defined scope before it is accepted into production.

What real-time detection adds to least privilege

Least privilege is often described at provisioning time, but machine identities drift after deployment through new integrations, expanded scopes, and reused credentials. Real-time detection looks for behavioural anomalies that suggest over-privilege, misuse, or unexpected access patterns before the issue becomes a breach. This matters because non-human identities can move much faster than periodic review cycles. If the control only runs during certification, it will always lag the operational reality.

Practical implication: pair periodic certification with runtime monitoring for NHI behaviour that changes outside the approved model.

NHI Mgmt Group analysis

Discovery is no longer the hard part of NHI governance, context is. The article’s core point is that organisations already have enough tooling to find machine identities, but not enough discipline to explain what those identities are actually entitled to do. That changes the governance problem from enumeration to interpretation, which is where most identity programmes are still weak. Practitioners should treat contextual lineage as the control boundary, not the asset list.

Identity blast radius is the right concept for the AI era. A token, key, or agent credential does not become risky only when it is exposed. It becomes risky when no one can quickly map its reach across cloud, CI/CD, and developer tooling. That makes blast radius a governance measure, not just an incident metric, and it should sit beside access review evidence in any NHI programme.

Human ownership attribution remains the accountability anchor even for machine and agent identities. The article’s emphasis on tying machine identities back to human owners reflects a necessary governance truth: non-human access still needs human accountability. Without that anchor, lifecycle controls such as certification, remediation, and offboarding become procedural theatre. Practitioners should insist that every non-human identity resolves to a responsible owner and a reviewable business purpose.

Real-time protection is becoming the difference between policy and control. Periodic governance can document entitlement, but it cannot keep pace with machine-speed access changes or behavioural drift. That is why detection and response now belong inside NHI governance rather than beside it. The practical conclusion is that runtime monitoring is not optional once autonomous agents and workload identities are allowed to interact with critical data.

AI agent governance and NHI governance are converging, not competing. The same control questions now apply to service identities, API credentials, and autonomous agents that make tool and data decisions at runtime. That convergence means identity teams should stop designing separate governance models for every new actor type. The programme that wins will be the one that can govern context, ownership, and privilege across all non-human access paths.

From our research:

• 98% of companies plan to deploy even more AI agents within the next 12 months, despite documented rogue behaviour in 80% of current deployments, according to AI Agents: The New Attack Surface report.
• Only 44% of organisations have implemented policies to govern AI agents, even though 92% agree that governing them is critical to enterprise security.
• For a broader control model, see OWASP Agentic AI Top 10 for the risk patterns behind agent identity misuse and tool abuse.

What this signals

Identity blast radius is becoming a programme-level metric, not just an incident-response afterthought. As AI agents and machine identities spread across cloud and developer tooling, teams need to know not only what exists but how far each identity can reach before a compromise becomes operationally material. That is why discovery, lineage, and ownership must be tracked together in the same operating model.

The governance gap is widening because review cycles assume access remains stable long enough to be certified. For non-human identities, that assumption is fragile when credentials are reused, embedded, or expanded through adjacent workflows. Teams should expect higher demand for runtime monitoring, entitlement graphs, and evidence that ties every privileged identity back to an accountable owner.

If your programme still separates agent governance from NHI governance, the separation will become expensive. The practical direction is toward one control plane for context, entitlement, and response across machine and autonomous identities, with lifecycle evidence anchored to reviewable ownership.

For practitioners

• Map every non-human identity to a human owner Require an accountable owner, business purpose, and review path for each machine identity before it is promoted to production. If the identity cannot be attributed, it cannot be governed.
• Build entitlement graphs around access context Document which tools, APIs, cloud services, and credentials each identity can reach so you can calculate blast radius and isolate overreach quickly.
• Pair certification with runtime monitoring Use access reviews for governance evidence, then layer behavioural monitoring to catch over-privileged access and scope drift between review cycles. Reference the Ultimate Guide to NHIs for lifecycle patterns and review design.
• Restrict non-human access to explicit operational boundaries Tie credentials to approved sources, environments, and workflows, and revoke anything that expands beyond the defined operating context. Use the OWASP NHI Top 10 to structure control gaps.

Key takeaways

• SailPoint’s Entro deal reflects a broader shift from discovering non-human identities to governing their context, ownership, and blast radius.
• AI agent and machine identity risk is now defined by scope, lineage, and runtime behaviour, not by inventory alone.
• Identity teams should align discovery, certification, and behavioural monitoring so non-human access is both attributable and enforceable.

Key terms

• Non-human identity: A non-human identity is any machine- or software-based identity used to authenticate and access systems, including service accounts, API keys, tokens, certificates, workloads, and AI agents. The governance challenge is not just creating it, but tracking ownership, scope, lifecycle, and revocation.
• Identity blast radius: Identity blast radius is the amount of systems, data, and operational capability exposed if an identity is misused or compromised. In NHI governance, it is the practical measure of entitlement reach, and it becomes useful only when access paths, dependencies, and ownership are mapped clearly.
• Ownership attribution: Ownership attribution is the process of linking a non-human identity back to a responsible human or team. It gives lifecycle controls a real enforcement point, because certification, remediation, and offboarding only work when someone can approve, investigate, and correct the access path.
• Runtime monitoring: Runtime monitoring is continuous observation of identity behaviour while access is being used, not just when it is issued or reviewed. For machine identities and AI agents, it helps detect over-privilege, unusual tool use, and scope drift that periodic access reviews can miss.

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 governance maturity in your organisation, it is worth exploring.

This post draws on content published by SailPoint: How Entro will supercharge our SailPoint Agentic Fabric. Read the original.