Notifications
Clear all
Topic starter
20/08/2026 5:43 pm
TL;DR: AI agents can interpret objectives, invoke applications, access sensitive data, and initiate transactions with limited intervention, which expands the identity, data, and operational attack surface, according to Living Security Human Risk Management Platform. The control problem is not universal approval gates but attributable, bounded, observable, and reversible authority, because AI agent identity governance now has to cover delegated action, runtime context, and human accountability at once.
NHIMG editorial — based on content published by Living Security Human Risk Management Platform: How to Secure AI Agents Without Slowing Adoption
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes.
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: Why do AI agents create a different access-risk profile than traditional applications?
A: AI agents can chain actions, call multiple tools, and change behaviour based on context, so one credential can enable more than one operational path.
Q: What breaks when AI agents are given broad inherited permissions?
A: Broad inherited permissions break the assumption that access is tied to a narrow business need.
Practitioner guidance
- Inventory every production agent as a governed identity Record owner, purpose, model, environment, connected applications, data classes, credentials, and deployment status.
- Issue unique short-lived credentials for each agent Do not let agents inherit a user session or share a generic service account.
- Move enforcement outside the model Apply API allowlists, parameter validation, row-level permissions, network egress filtering, data classification checks, rate limits, spend ceilings, and maximum transaction values at gateways and target systems.
What's in the full article
Living Security Human Risk Management Platform's full guide covers the operational detail this post intentionally leaves for the source:
- A seven-step control architecture for discovering, classifying, and owning every production AI agent.
- Concrete enforcement examples for allowlists, transaction caps, output validation, and step-up approval.
- Testing guidance for red-team scenarios, kill-switch validation, rollback, and progressive release.
- Examples of how Human Risk Management ties human behaviour, identity, and agent activity into one workflow.
AI agent governance without slowing adoption: what teams need?
Explore further
20/08/2026 6:27 pm
AI agent governance fails when identity is treated as a provisioning problem instead of a runtime control problem. The article correctly frames the core risk as delegated authority that can vary with context, not a fixed permission set. That means traditional IAM checkpoints alone are insufficient when the actor can select tools, alter its plan, and act across multiple systems in one workflow. Practitioners should treat the agent’s operating state as part of the access decision, not just the identity record.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, with 38% having no or low visibility, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities.
A question worth separating out:
Q: Who should be accountable when an AI agent causes a security incident?
A: Accountability should sit with the human owner, platform team, or business function that granted and operated the agent. The identity may act independently, but governance cannot detach responsibility from the delegation chain. Programs should define ownership, escalation, and remediation paths before deployment so responsibility is clear when the agent's behaviour changes.
👉 Read our full editorial: How to secure AI agents without slowing adoption
