Security Framework Coverage
Frameworks such as the OWASP Top 10 for LLMs, the OWASP Top 10 for agentic applications, and MITRE ATLAS describe categories of risk. Most categories are addressed by more than one capability, across the posture and runtime layers, and some depend on controls in your own architecture. The tables below show, for each framework item, which layer of AI Agent Security addresses it and what remains the responsibility of your architecture.
How to read the mapping: for each item, the first column shows the runtime contribution (the Guard API guardrails), the second the posture contribution (discovery and risk assessment), and the third the controls that sit with your own architecture. An empty cell means that item is not the primary place that layer contributes.
OWASP Top 10 for LLMs (2025)
OWASP Top 10 for Agentic Applications (2026)
Notes on coverage
- Inter-agent communication (ASI07) is addressed indirectly: by inspecting the content agents pass between each other when those interactions are screened through the Guard API. Cryptographic and identity controls for inter-agent channels sit with your architecture.
- Runtime protection today integrates through the Guard API. Native runtime integration with agent platforms is on the roadmap.
- Posture-level enforcement of agent component allow/deny lists is on the roadmap. Runtime tool access control is available today through the Tool Allow/Deny List in Agent Behavior Defense.
- MITRE ATLAS techniques are mapped on individual risks in the risk assessment, alongside the OWASP references shown in the risk-types view.