Notifications
Clear all
Topic starter
14/09/2026 10:09 am
TL;DR: Secure agentic migration depends on an identity-aware substrate that authenticates, scopes, logs, vaults, rotates, and revokes every tool call in real time, rather than relying on detached approvals or service-account sprawl, according to C1.ai. The governing assumption breaks when agency is treated like human identity, because autonomous tool use needs lifecycle and revocation at call time, not after the fact.
NHIMG editorial — based on content published by C1.ai: Security Isn't the Brake on Your Agentic Migration. It's the Engine
By the numbers:
- 79% of organisations have experienced secrets leaks, with 77% of these incidents resulting in tangible damage.
- Only 5.7% of organisations have full visibility into their service accounts.
- 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation.
Questions worth separating out
Q: How should security teams govern agent tool calls in production?
A: Treat each tool invocation as a separate identity decision, not as a one-time permission granted to the agent.
Q: Why do autonomous agents require different access governance than human users?
A: Human IAM assumes a stable user session and a predictable review cycle.
Q: What breaks when agent credentials are stored only in the runtime environment?
A: Long-lived secrets become available to any tool path, prompt leak, or misconfigured connector that can reach the runtime.
Practitioner guidance
- Implement runtime policy enforcement at the tool boundary Require every agent action to pass through an identity-aware proxy so authentication, authorisation, and logging happen on each call, not only at login or provisioning.
- Remove long-lived credentials from agent execution paths Keep service credentials in a vault, ban .env storage for agent workflows, and ensure rotation and instant revoke are available before any production rollout.
- Bind every agent chain to a named human owner Record a responsible human for each agent workflow, including chained sub-agent actions, so accountability remains traceable across delegation hops.
What's in the full article
C1.ai's full blog post covers the operational detail this post intentionally leaves for the source:
- The full runtime substrate model for identity-aware proxying across agent tool calls.
- The operational logic behind credential vaulting, auto-rotation, and instant revoke.
- The chain-of-accountability example showing one human owner across multiple agent hops.
- The 90-day blueprint referenced at the end of the series for teams planning rollout sequencing.
👉 Read C1.ai's analysis of agentic security as an identity substrate →
Agentic identity substrate: what makes fast and safe the same path?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
14/09/2026 10:10 am
Agency has become the security object, not identity alone. The article is right to separate who something is from what it may do on whose behalf, because agentic systems turn access into a runtime problem. Traditional IAM answers the login question; agentic governance has to answer delegation, scope, lifecycle, and revocation at the moment of action. Practitioners should treat agency as the unit of control.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
- 71% of NHIs are not rotated within recommended time frames, showing how quickly runtime governance can decay when lifecycle controls are weak.
A question worth separating out:
Q: How do organisations know if agent governance is actually working?
A: Agent governance is working when every agent is discoverable, owned, least privileged, and auditable at the action level. Look for reduced shadow AI, fewer embedded secrets, clean revocation on retirement, and logs that show which tools and data paths were used. If those signals are missing, governance is still partial.
👉 Read our full editorial: Agentic migration needs identity substrate controls, not more friction
