Join our Newsletter — 33% off our NHI Course

Why do Protocols leave AI agent governance unfinished?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20217
Topic starter  

TL;DR: AI agent protocols are emerging to standardise how agents exchange information, coordinate actions and handle errors across cybersecurity use cases, according to Black Kite. Agent communication standards should be treated as access-control decisions because delegated authority can move across systems without enough lifecycle control.

Editorial analysis by NHI Mgmt Group, based on content published by Black Kite: “AI Agents and Protocols:”.

Key questions

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: What breaks when multiple agents share tools and data without a common protocol?

A: The failure mode is inconsistent coordination: agents can duplicate work, act on stale context or pass unsafe decisions downstream.

Q: How should security teams govern agentic AI as it moves into production?

A: Security teams should govern agentic AI as a class of non-human identity, not as a generic application feature.

Practitioner guidance

  • Define protocol-level trust boundaries Specify which systems, tools and peer agents each protocol may reach, and require explicit approval for any cross-domain or cross-environment interaction.
  • Bind each action to a governed agent identity Assign a distinct identity to each agent, record its delegated scope and revoke access when the task, workflow or session ends.
  • Test for cascading failure across agent chains Simulate stale context, conflicting instructions and malformed messages to see how far a bad decision can propagate through collaborating agents.

Bottom line: AI agent protocols solve coordination problems, but they also expose where governance for identity, delegation and trust is still immature.

Glossary terms: AI Agent Architecture, Protocol-Mediated Delegation, Inter-Agent Trust, Agentic workflow

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20707
 

Protocol standardisation is becoming a governance problem, not just an engineering convenience. Once AI agents can negotiate with tools, other agents and shared systems, the question becomes who controls the trust boundary between them. A protocol gives structure to communication, but it does not by itself define policy, ownership or accountability. Practitioners should treat agent protocols as part of identity governance, not as a purely technical plumbing layer.

A few things that frame the scale:

A question worth separating out:

Q: What should teams do before allowing autonomous agents to act across systems?

A: They should require explicit delegation rules, scoped permissions and revocation paths before any autonomous workflow goes live. The critical test is whether the organisation can identify the acting agent, the authority it used and the systems it touched after the task completes.

👉 Read our full editorial: AI agent protocols expose governance gaps in collaborative automation


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.