Topic starter
12/07/2026 12:19 pm
TL;DR: Clarity Security argues that AI agents have exposed long-standing NHI governance weaknesses, with ownership, observability and runtime enforcement emerging as the real controls while prompts and static permissions fail to constrain agent behaviour. The governing assumption that instructions alone can control runtime action has collapsed.
Editorial analysis by NHI Mgmt Group, based on content published by Clarity Security: “Beyond Human: What Lalit Choda and Alexis Moyse Are Telling Security Teams About Non-Human Identity and AI Agent Security”.
Key questions
Q: What breaks when AI agents are allowed to act on untrusted prompts without runtime guardrails?
A: Without runtime guardrails, agents can be socially engineered into disclosing data, crossing policy boundaries, or executing unintended actions that look like normal work.
Q: Why do ownership models for AI agents need to follow the workload or product?
A: Because individual ownership fails when people change roles or leave.
Q: How do security teams know if NHI governance is actually working?
A: A working NHI programme shows clear ownership, short-lived credentials, frequent revocation, and low numbers of dormant or shared machine accounts.
Practitioner guidance
- Build a unified identity inventory Catalogue every AI agent and NHI, then map what each one can access, which credentials it uses, and which downstream systems it can reach.
- Assign ownership to the operating team Define the business team or service owner responsible for each agent, and separate that accountability from the person who originally created it.
- Move enforcement to runtime Block or allow each tool call, API request or database action based on current purpose and scope rather than on prompt text or static policy notes.
Bottom line: AI agents expose the limits of prompt-based control because runtime behaviour can diverge from written instructions.
What's in the full article
Clarity Security's full webinar covers the operational detail this post intentionally leaves for the source:
- The ownership model discussion for agents, including why accountability should sit with the team rather than the builder.
- The runtime enforcement example tied to destructive agent behaviour and how live decisioning changes access control.
- The discovery workflow for inventorying NHIs, agents, APIs and downstream systems before governance can begin.
- The board communication framing for explaining agent risk in terms executives already understand.
👉 Read Clarity Security's webinar on AI agent and NHI governance →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
12/07/2026 12:33 pm
Prompt-based governance is a broken control model for autonomous runtime decisions. Written instructions can shape intent, but they cannot reliably constrain action once an agent is selecting tools and execution timing on its own. The article shows why this matters for identity governance: the control point has moved from what the system is told to what the system is allowed to do at runtime. Practitioners should treat prompts as guidance, not policy.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should teams do when AI-agent access exceeds a human user's scope?
A: They should revoke or narrow the agent's access until the scope matches a clearly defined business task and an accountable owner can explain why the agent needs it. AI-agent identities should be governed like service accounts, but with even tighter scrutiny on persistence between sessions and reuse across workflows. If a human would not get the same scope, the agent should not keep it.
👉 Read our full editorial: AI agent and NHI governance need runtime enforcement, not prompts