Topic starter
24/06/2026 7:38 pm
TL;DR: Identity mapping alone leaves AI agents with over-permissioned, long-lived credentials and weak approval controls, according to 1Kosmos. Runtime checks are what let teams interrupt sensitive actions before an agent acts beyond scope.
Editorial analysis by NHI Mgmt Group, based on content published by 1Kosmos: “AI Agents Need More Than Identity Mapping: They Need Trust, Authentication, and Human Assurance”.
Key questions
Q: Why do AI agents create different risk patterns from normal service accounts?
A: AI agents can change their behaviour and decision path during execution, so their effective authority may expand even when the credential itself does not change.
Q: How can security teams tell whether AI agent approval controls are actually working?
A: Look for evidence that sensitive actions trigger a fresh approval event, that approvals are tied to a specific human principal, and that the agent cannot proceed when the checkpoint fails.
Q: What breaks when organisations map every AI agent to a human owner?
A: Ownership mapping still helps governance, but it breaks as a complete control because it does not explain current behaviour.
Practitioner guidance
- Inventory agents as governed identities Register each AI agent as a first-class identity with a unique identifier, explicit owner, and lifecycle record so access can be traced and revoked.
- Separate agent authentication from human authentication Require the agent to prove its own identity with cryptographic methods instead of inheriting trust from the person who initiated the workflow.
- Bind delegated authority to explicit conditions Issue delegated credentials with scope, purpose, and risk thresholds so the agent cannot reuse broad standing access across unrelated tasks.
Bottom line: AI agent governance fails when teams confuse ownership mapping with actual authorisation and approval control.
Glossary terms: AI Agent Identity, Delegated Authorization, Human-in-the-Loop Approval, Runtime assurance
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 22 hours ago by NHI Mgmt Group
25/06/2026 5:00 am
Identity mapping is a recordkeeping control, not a trust control. Binding an AI agent to a human owner or service account creates attribution, but it does not prove current authorisation or safe behaviour. That distinction matters because agent activity is continuous and contextual, while mapping is static. Practitioners should stop treating ownership labels as evidence of enforceable governance.
A few things that frame the scale:
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: When should organisations require human approval for an AI agent action?
A: Require human approval when the action could change infrastructure, expose sensitive data, move laterally across systems, or trigger a business-critical workflow that is hard to reverse. Approval is also warranted when the agent’s decision depends on ambiguous input or external data that cannot be trusted at face value. High-consequence actions need a human stop point.
👉 Read our full editorial: AI agent identity assurance is replacing simple agent mapping
This post was modified 22 hours ago by NHI Mgmt Group