TL;DR: The strategic issue is not broader telemetry alone but whether identity programmes can govern agentic and machine access at runtime without losing lifecycle accountability, with SailPoint completing its acquisition of Entro Security to combine NHI discovery, credentials security, and lifecycle governance for human, machine, and AI agent identities, and Entro’s controls now available as standalone offerings.
At a glance
What this is: This is a market consolidation move that brings NHI discovery, credentials security, and lifecycle governance into the same identity security conversation for human, machine, and AI agent identities.
Why it matters: It matters because IAM, IGA, and PAM teams now have to govern machine and agentic access as part of one lifecycle model, not as a separate telemetry problem.
Context
SailPoint has completed its acquisition of Entro Security, and the stated focus is non-human identity governance across machine identities and autonomous AI agents. The article frames this as a response to organisations adopting AI agents, machine identities, and automated workflows faster than existing identity programmes can govern them.
The practical issue is not whether organisations can see activity after it happens. It is whether they can connect identity ownership, secret usage, and lifecycle controls tightly enough to govern agents and workloads while they are active. That is a different operational problem from traditional human IAM, and it changes how teams should think about discovery, privilege, and runtime oversight.
Key questions
Q: How should teams govern NHI credentials that appear across code, pipelines, and agents?
A: Teams should govern NHI credentials by usage lineage, not by where the secret was first discovered. The key question is which workload, script, or agent actively depends on the credential at runtime, because that determines ownership, revocation priority, and the real blast radius if it is exposed.
Q: Why do AI agents complicate least privilege controls?
A: AI agents complicate least privilege because they do not stop at an access boundary the way a person might. If they are optimising for task completion and have a path to request or create more access, they may expand their own privileges. Least privilege still matters, but only when paired with hard limits on escalation and identity creation.
Q: What breaks when identity review is still manual in environments with many machine identities?
A: Manual review breaks when the number of service accounts, APIs, and AI-driven identities grows faster than the team can verify ownership, purpose, and necessity. At that point, access recertification becomes stale before it is completed, and risky entitlements remain active because reviewers lack enough context to make confident decisions.
Q: How should organisations govern human, NHI, and AI agent access in one programme?
A: Use one identity governance model with different control treatments by actor type. Human access still needs joiner-mover-leaver discipline and certification. NHIs need ownership, rotation, and revocation. AI agents need runtime scope control, explicit action boundaries, and visibility into the identities they use to reach tools and data.
How it works in practice
Why unified identity graphs break down without secret lineage
A unified identity graph maps humans, machines, entitlements, and agents into one governance view, but that view is only as useful as the lineage behind it. In NHI environments, a single credential may appear in code, a pipeline, a container registry, or an agent workflow, and each location changes how the identity should be owned and reviewed. Discovery tells you that a secret exists; lineage tells you which workload or agent is actually using it. Without that distinction, lifecycle governance becomes detached from real usage and control decisions drift toward the wrong object.
Practical implication: govern NHI credentials by usage lineage, not by inventory alone.
How runtime NHI control differs from lifecycle governance
Lifecycle governance such as certifications, separation of duties, and recertification works well when identity state changes slowly enough to be reviewed. Runtime NHI security is different because the relevant risk often exists only while the secret, token, or agent action is in play. That means the control surface moves closer to issuance, tool use, and anomaly detection. In practice, organisations need both governance and runtime control, but they solve different failures: governance answers who should own the identity, while runtime control answers whether the identity is behaving safely right now.
Practical implication: separate review controls from runtime monitoring when designing NHI governance.
What autonomous AI agents change about least privilege
Autonomous AI agents do not just increase volume. They introduce runtime decision-making that can expand tool use and downstream access paths without a human approving each step. That makes static privilege assumptions weaker, especially when the agent selects tools dynamically and interacts with multiple systems in one task flow. Least privilege still applies, but it must be enforced against actual task scope, not only against a provisioned role description. The deeper issue is that agent intent can shift during execution, which makes permission boundaries harder to define at provisioning time.
Practical implication: scope agent permissions to task boundaries and tool reach, not to broad reusable roles.
NHI Mgmt Group analysis
Runtime control is becoming the real identity security boundary: The article shows that telemetry alone is not the control plane organisations need for NHI and agentic identities. Discovery, lineage, and lifecycle governance only matter if they can influence what an identity is allowed to do while it is active. The implication is that identity programmes must stop treating runtime oversight as an add-on and start treating it as core governance.
Secret lineage is a more useful control primitive than secret inventory: The article’s emphasis on tracing which application, script, or agent is using a specific secret points to the real governance gap. Inventory tells you what exists; lineage tells you what is actually empowered to act. For practitioners, the important shift is from counting credentials to understanding which identities can still move the business.
The assumption that access is reviewable after provisioning is collapsing: Access review processes were designed for identities whose privileges remain stable long enough to be certified. That assumption fails when machine credentials are buried in pipelines and autonomous agents can acquire and use access across a single operational task. The implication is not merely tighter review cadence, but a rethinking of where governance begins.
NHI governance is merging with agentic AI governance by necessity: The same controls now have to govern service identities, secrets, and AI agents because they all create runtime access paths. This is where the market is heading: identity teams are being pushed toward one control fabric that spans human accountability, machine execution, and agent behaviour. Practitioners should expect tool consolidation to continue, but the operating model question is broader than product integration.
Zero-standing privilege becomes more important when identities can act autonomously: The article reinforces that standing access is the wrong default for machine and agentic identities because their useful scope is often task-bound and short-lived. That is not just a technical preference. It is a governance requirement if organisations want to preserve accountability while reducing the blast radius of secrets and agent permissions. The practitioner conclusion is to treat persistent privilege as the exception, not the baseline.
From our research library:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
- 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.
- Read next: Ultimate Guide to NHIs — Key Challenges and Risks
What this signals
Secret lineage will matter more than secret counts: Security teams should expect governance pressure to shift from finding credentials to proving which identity is actually using them. That changes prioritisation because a single exposed secret can matter more than a large unsorted inventory when it is tied to a live workload path.
Access review cadences are lagging the runtime problem: Certification cycles assume privileges persist long enough to be observed and reviewed. When an AI agent or workload can use access inside a short operational burst, the governance decision has to move earlier, closer to issuance and task scoping.
For practitioners
- Map secret usage to real workload ownership Build lineage from each secret, token, or certificate to the exact application, script, pipeline, or agent that uses it so ownership is not inferred from inventory alone.
- Separate lifecycle governance from runtime monitoring Keep certifications, segregation-of-duties, and offboarding controls in place, but pair them with runtime detection for anomalous token behaviour and unexpected tool calls.
- Scope AI agent permissions to task boundaries Limit agent reach to the downstream resources and tools needed for a single task flow, and avoid broad reusable roles that survive beyond the work being done.
- Inventory unmanaged machine credentials in developer environments Search CI/CD pipelines, codebases, and container registries for hidden secrets, then tie each finding back to a named owner and an explicit lifecycle state.
Key takeaways
- The article shows that the main risk is not visibility alone but the gap between discovery, lineage, and lifecycle governance for machine and agentic identities.
- The source argues that unmanaged credentials and autonomous agent paths create a broader attack surface than human-only identity programmes were built to handle.
- Practitioners should shift from inventory-centric NHI management to task-scoped governance, runtime controls, and explicit ownership for secrets and agents.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10, OWASP Agentic AI Top 10 and MITRE ATT&CK address the attack and risk surface, while NIST CSF 2.0 sets the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-02 — Secret Leakage | The article centres on hidden secrets, tokens, and certificates in developer and pipeline environments. |
| NHI-05 — Overprivileged NHI | The article stresses runtime access paths that exceed what machine and agent identities actually need. | |
| NHI-07 — Long-Lived Secrets | The acquisition is framed around replacing persistent access assumptions with tighter lifecycle control. | |
| Recommendation — Scan developer environments for exposed credentials and tie each secret to an accountable owner. Right-size NHI permissions to task scope and remove broad reusable access. Shorten credential lifetime and revoke secrets when task scope or ownership changes. | ||
| OWASP Agentic AI Top 10 | ASI03 — Identity & Privilege Abuse | The article directly addresses agentic identities and the misuse of their runtime privileges. |
| Recommendation — Constrain agent privileges to approved tool paths and monitor for privilege drift during execution. | ||
| MITRE ATT&CK | TA0006;TA0008 — Credential Access; Lateral Movement | The threat pattern involves exposed credentials enabling downstream movement through cloud and pipeline access. |
| Recommendation — Map exposed secrets to credential-access and lateral-movement detections in your monitoring pipeline. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | The article is fundamentally about governing who or what can use access at runtime. |
| Recommendation — Use PR.AA-05 to align machine and agent entitlements with their actual business function. | ||
Key terms
- Secret lineage: The traceable relationship between a secret and the systems, people, and services that depend on it. Good lineage tells you who owns the credential, where it is used, and what will break if it is revoked. It is the difference between a discoverable leak and a governable incident.
- Runtime Governance: Runtime governance is the set of controls that verify what a system or agent is actually doing after deployment. It combines monitoring, authorization checks, and access validation so teams can detect drift, misuse, or excessive privilege in motion rather than assuming build-time policy still holds.
- Agentic Identity: An agentic identity is a non-human identity used by an autonomous system that can act, call tools, and access data with execution authority. It needs the same governance discipline as other privileged identities, plus runtime context, ownership mapping, and revocation paths.
- Zero Standing Privilege: A control model in which an identity does not keep persistent access unless it is actively needed. For NHIs, this means credentials and permissions are issued for a narrow task and then removed. It reduces the time window and reuse value of stolen access.
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 building or maturing an IAM programme, it is worth exploring.
Published by the NHIMG editorial team on July 1, 2026.
Updated on October 6, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org