Topic starter
16/04/2026 6:56 pm
TL;DR: AI agent security tools are largely built to observe behavior after the fact, while the real breach condition is a toxic combination of overbroad permissions and exposure to unauthorized invokers, according to Obsidian Security. The architectural gap is that detection without runtime enforcement cannot stop legitimate but dangerous execution before damage occurs.
Editorial analysis by NHI Mgmt Group, based on content published by Obsidian Security: “The Architecture Gap No AI Agent Security Tool Is Built to Close”.
Key questions
Q: What breaks when AI agent security tools only monitor behavior?
A: Behavior-only tools miss the moment when an agent becomes dangerous through valid credentials and excessive reach.
Q: Why do AI agents create new risk in non-human identity management?
A: AI agents create risk because they operate as software identities with delegated authority, but many organisations do not track them with the same discipline applied to users or service accounts.
Q: How do you know if an AI agent is overexposed?
A: An AI agent is overexposed when it can reach resources that are not strictly necessary for its job, especially secrets, execution tools, and internal data stores.
Practitioner guidance
- Map agent entitlement scope inside connected applications Inventory what each agent's service account can actually reach in Salesforce, ServiceNow, Workday, Slack, and similar systems, not just what the agent is configured to do.
- Tie invocation rights to data sensitivity Identify which users, workflows, or systems can invoke each agent and compare that reach to the sensitivity of the records and actions available to the agent.
- Separate detection from enforcement Require a control that can block execution before an agent action completes, because alerting after the action is logged does not stop the harmful state change.
Bottom line: AI agent risk is not defined by behaviour alone, but by whether excessive entitlements and unauthorised invocation intersect at runtime.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
12/10/2026 3:27 pm
Runtime enforcement is the missing identity control for AI agents: the market has over-invested in post-event observation and under-invested in execution-time decision control. When an agent can act through valid credentials, the critical question is not whether the behaviour looks unusual after the fact. The question is whether the action should have been permitted at the moment of invocation. Practitioners need to treat execution as the control point, not the audit trail.
A few things that frame the scale:
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
- 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.
A question worth separating out:
Q: What should teams do when sensitive data moves through service accounts or automation?
A: Apply the same governance discipline used for human access, but make the audit and enforcement logic identity-aware. Service accounts and automated workflows should have explicit data paths, narrow scope, and reviewable exceptions, because they can move data without the behavioural cues that human users produce.
👉 Read our full editorial: AI agent security tools miss the toxic combination at runtime