Subscribe to the Non-Human & AI Identity Journal

Notifications
Clear all

MITRE ATLAS for AI agents: are your controls keeping up?


(@nhi-mgmt-group)
Member Moderator
Joined: 1 year ago
Posts: 2827
Topic starter  

TL;DR: The first 2026 MITRE ATLAS update expands coverage of AI service APIs, agent tool credential harvesting, data poisoning, data destruction, and clickbait attacks against agentic browsers, according to Zenity. The shift matters because autonomous agents can invoke tools, credentials, and workflows at runtime, which means identity and runtime governance now sit at the center of AI security.

NHIMG editorial — based on content published by Zenity: Advancing MITRE ATLAS AI Security Through Zenity’s Contributions

By the numbers:

Questions worth separating out

Q: How should security teams govern AI agents that use enterprise tools and APIs?

A: They should govern them as privileged non-human identities with runtime visibility, scoped access, and explicit ownership.

Q: Why do agentic browsers create risk beyond normal web automation?

A: Agentic browsers can interpret content, make decisions, and execute actions on behalf of a task, which means malicious page content can steer machine behaviour directly.

Q: What breaks when AI agents can reach secrets through connected tools?

A: The trust boundary breaks because the agent’s usefulness often depends on access to tokens, keys, and service accounts held by adjacent systems.

Practitioner guidance

  • Map agent runtime privilege chains Inventory every AI agent, the tools it can invoke, the credentials it can reach, and the downstream systems those credentials unlock.
  • Separate agent access from human workflows Stop granting broad shared access to agentic browsers and assistants that mirror human work.
  • Treat connected tools as credential exposure points Review every agent-connected tool for tokens, API keys, session material, or embedded secrets.

What's in the full report

Zenity's full analysis covers the operational detail this post intentionally leaves for the source:

  • The specific ATLAS technique mappings and case-study context behind AI service API abuse and agent tool credential harvesting.
  • The article's examples of how agentic browsers can be manipulated through page content, metadata, and workflow prompts.
  • Zenity's discussion of where runtime monitoring, identity governance, and API telemetry fit into AI security operations.
  • The source article's broader framing of agent-aware security as a foundation for enterprise AI defence.

👉 Read Zenity's analysis of MITRE ATLAS and agentic AI security →

MITRE ATLAS for AI agents: are your controls keeping up?

Explore further

View Full Forum →  |  NHI Foundation Course →



   
Quote
(@mr-nhi)
Member Moderator
Joined: 4 weeks ago
Posts: 1125
 

AI agent governance is now an identity problem, not a model problem. The article’s strongest signal is that MITRE ATLAS is expanding to cover the places where agents act, not just the places where they reason. That is the right shift for the field because the security failure now sits in runtime access, tool invocation, and delegated authority. Practitioners should treat agentic AI as part of identity governance, not a separate AI-only domain.

A few things that frame the scale:

  • 92% agree governing AI agents is critical to enterprise security, yet only 44% have implemented any policies to do so, according to AI Agents: The New Attack Surface report.
  • 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.

A question worth separating out:

Q: How can organisations tell whether their agent governance is actually working?

A: Look for complete inventory, runtime telemetry, and named owners for each agent’s access path. If you cannot answer which tools an agent used, what data it touched, and who approved the delegated access, governance is incomplete. Effective programmes can reconstruct agent actions after the fact and limit blast radius during execution.

👉 Read our full editorial: MITRE ATLAS and agentic AI security: what practitioners need to know



   
ReplyQuote
Share: