Topic starter
06/06/2026 1:51 am
TL;DR: Multi agent AI systems plan, delegate, and act across enterprise infrastructure without human approval, creating security risks that traditional request-response controls were not designed to handle, according to WitnessAI. The governance gap is not just visibility, but the collapse of assumptions about stable privilege, trusted handoffs, and human-paced review.
Editorial analysis by NHI Mgmt Group, based on content published by WitnessAI: “Multi agent security: risks & how to secure AI agent systems”.
Key questions
Q: What breaks when multi-agent AI systems are governed like single-model deployments?
A: Single-model governance assumes one prompt, one response, and a human-visible decision boundary.
Q: Why do autonomous AI systems create more identity risk than normal automation?
A: Normal automation follows a fixed path, but autonomous systems can interpret goals, choose actions, and continue without waiting for a person.
Q: How can security teams know if agent skill controls are actually working?
A: Look for evidence that skills are inventoried, risk rated, scanned before execution, and tied to a policy manifest or approval record.
Practitioner guidance
- Map every agent to a governed non-human identity Assign each agent a scoped identity, minimum standing permissions, and a clear owner so delegated actions are not anonymous or open-ended.
- Enforce runtime controls on tool use Apply policy at execution time for tool calls, outbound communication, and sensitive data access rather than relying on one-time setup approvals.
- Build lineage across agent handoffs Record prompts, tool selections, outputs, and downstream recipients so incident teams can trace how one agent’s action influenced the next step.
Bottom line: Multi-agent AI creates an identity governance problem because delegated machine actions do not fit the assumptions behind human-paced access review.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/06/2026 3:12 am
Stable privilege is the wrong governance assumption for multi-agent systems: The article shows that enterprise identity infrastructure was designed for human principals who can be reviewed, certified, and offboarded on a stable schedule. That assumption fails when agents delegate work, chain tool calls, and move across systems at machine speed. The implication is that identity governance has to account for delegated action paths, not just named accounts.
A few things that frame the scale:
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
- 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.
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: Multi agent AI security exposes a new identity governance gap