Topic starter
14/09/2026 10:09 am
TL;DR: Agentic AI risk must be classified by autonomy and human oversight, not just by who owns the stack, because two agents on the same model can carry very different exposure, according to WitnessAI. That assumption collapse is now visible in production deployments where agents plan, call tools, and act on external systems without per-step human approval.
Editorial analysis by NHI Mgmt Group, based on content published by WitnessAI: “How to apply the AWS Agentic AI security scoping matrix”.
Key questions
Q: What breaks when agent scope is defined by stack ownership instead of runtime authority?
A: The classification misses the actual risk boundary.
Q: Why do agentic AI controls need to be tied to autonomy and oversight?
A: Because autonomy changes the ceiling on what an agent can do before a human can intervene.
Q: What are the signs that agent authority is failing in production?
A: Look for long-lived tokens, shared credentials, missing approval logs, and audit trails that cannot attribute an action to the agent itself.
Practitioner guidance
- Inventory agent identities and tool connections Record each deployed agent, its MCP or other tool connections, the systems it can read and write, and the human owner responsible for the deployment.
- Classify agents by agency and autonomy Use separate judgments for what the agent is permitted to change and how much runs without human approval.
- Move enforcement out of the model Apply deterministic policy, scoped credentials, and tool-level allow or block controls outside the agent's reasoning loop.
Bottom line: Agentic AI governance fails when teams classify systems by model ownership instead of the authority the agent can exercise.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/09/2026 10:10 am
Agentic AI scope cannot be governed by stack ownership alone: The article's central point is that two agents on the same model can present very different risk because one recommends and the other executes. That breaks the old assumption that AI risk can be classified by infrastructure provenance instead of runtime authority. The implication is that identity governance for agents must treat authority as the primary variable, not just deployment context.
A few things that frame the scale:
- 62% of organisations are at least experimenting with AI agents, but only 23% have scaled one into a single business function, according to McKinsey's 2025 State of AI survey.
A question worth separating out:
Q: How should organisations govern autonomous agents that act on behalf of users?
A: They should require clear delegation, task-scoped permission, and continuous traceability back to a human creator. The goal is not to impersonate the user more perfectly, but to narrow what the agent can do, preserve auditability, and separate ordinary automation from high-risk action.
👉 Read our full editorial: AWS agentic AI scope matrix exposes the governance gap