OWASP Agentic Top 10 Mapping

July 30, 2026 ยท View on GitHub

Agent OS combines native ACS policy evaluation with host lifecycle controls. The mapping below identifies the primary control surface for each risk.

RiskPrimary controls
ASI01 Agent Goal HijackInput and output policies, prompt-injection detection, audit
ASI02 Tool MisuseManifest tool catalog, pre_tool_call, sandbox controls
ASI03 Identity and Privilege AbuseAgentMesh identity, capability checks, approval
ASI04 Agentic Supply ChainTool identity, signatures, provenance, package controls
ASI05 Unexpected Code ExecutionSandbox providers, code scanning, tool policy
ASI06 Memory and Context PoisoningContext validation, memory integrity, input policy
ASI07 Insecure Inter-Agent CommunicationAgentMesh trust and encrypted transport
ASI08 Cascading FailuresCircuit breakers, SLOs, rate limits, session budgets
ASI09 Human-Agent Trust ExploitationApproval binding, evidence, restricted audit
ASI10 Rogue AgentsIdentity, runtime mediation, sandbox isolation, kill controls

Native policy example

from agent_control_specification import AgentControl, HostSession

runtime = AgentControl.from_path("policies/owasp-manifest.yaml")
session = HostSession(
    runtime,
    agent_id="owasp-agent",
    session_id="owasp-session",
)

evaluation = session.pre_tool_call(
    tool_name="execute_code",
    args={"code": "untrusted input"},
)

The manifest can bind policies to input, model, tool, and output intervention points. Tool catalogs, budgets, transforms, evidence, and approval are native ACS contracts.

Host controls

Policy evaluation does not replace host security:

  • SandboxConfig owns network, filesystem, resource, and provider controls.
  • AgentMesh owns identity, trust, and transport.
  • Agent SRE owns circuit breakers, SLOs, chaos testing, and incident response.
  • Agent OS adapters own framework lifecycle ordering and sanitized errors.

Fail-closed behavior

Unexpected policy, dispatcher, or approval errors deny the operation. Public exceptions expose stable text while trusted audit code retains the structured PolicyEvaluation.

Verification

Use agt test for policy replay, adapter mediation tests for side-effect ordering, sandbox provider tests for isolation, and red-team suites for cross-layer attack scenarios.

This mapping is architectural guidance, not a certification claim. Validate the controls required by the deployment's own threat model.