CSAIChaptersEventsBlog

Working Group

Autonomous Action Runtime Management (AARM)

AARM is an open system category specification for securing AI-driven actions at runtime. Build systems that intercept, authorize, and audit autonomous actions before they execute.
Autonomous Action Runtime Management (AARM)

About the AARM Working Group


The Autonomous Action Runtime Management (AARM) Working Group, operating under the Cloud Security Alliance Agentic Control Plane Initiative, is building the open system category specification for securing AI-driven actions at runtime. The security posture of AI systems is increasingly determined not by what models say but by what they do, and existing security paradigms were not built for irreversible, high-velocity, compositional actions executed by agents under static high-privilege identities.

AARM is an open system specification. It defines what a runtime security system must do, not how to build it. The Working Group exists to:

  • Develop and maintain the AARM specification, threat model, and conformance requirements as a vendor-neutral public good
  • Enable buyers to objectively evaluate vendor claims against defined criteria, before fragmentation forecloses interoperability
  • Preserve architectural choice by specifying what conformant systems must do rather than mandating a single implementation approach
  • Accelerate adoption of runtime security for AI agents through practical implementation guidance, reference patterns, and a public conformance review process
  • Coordinate research on open challenges in intent inference, data flow tracking, multi-agent coordination, and protection of the security system itself

AARM is part of the Cloud Security Alliance Agentic Control Plane Initiative, announced in April 2026.

Stay informed about AARM and Participate. Help shape the future of runtime security for AI agents. Sign up to receive information on AARM specification updates, conformance reviews, and Working Group activities.

What an AARM System Does

A system conforming to AARM:

  1. Intercepts AI-driven actions before they reach target systems
  2. Accumulates Context — tracks session state, the user's original request, prior actions, data accessed, and tool outputs in a tamper-evident, append-only log
  3. Evaluates the action against static policy and contextual alignment with stated intent
  4. Enforces one of five authorization decisions: ALLOW, DENY, MODIFY, DEFER, or STEP_UP (require human approval)
  5. Records tamper-evident receipts capturing action, context, decision, and outcome for forensic reconstruction

AARM is not a product, library, or service you install. It is a specification used to design and build a runtime security system, or to evaluate whether existing solutions meet the bar.

The Runtime Security Gap

Traditional security paradigms fail to address five characteristics of AI-driven actions:

  • Irreversibility: Tool executions produce permanent effects. Once a database is dropped or data is exfiltrated, the damage is done.
  • Speed: Agents execute hundreds of actions per minute, far beyond human review capacity.
  • Compositional risk: Individual actions may satisfy policy while their composition constitutes a breach.
  • Untrusted orchestration: Prompt injection and indirect attacks mean the AI layer cannot be trusted as a security boundary.
  • Privilege amplification: Agents operate under static, high-privilege identities misaligned with least privilege. Small reasoning failures produce large-scale impact.

Existing tools do not close this gap. SIEM observes events after execution. API gateways verify who is calling, not what the action means. Firewalls protect perimeters, but agents operate inside with legitimate credentials. Prompt guardrails filter text, not actions. Human-in-the-loop does not scale. IAM and RBAC evaluate permissions in isolation and cannot detect compositional threats.

The gap lies at the intersection of prevention and context-awareness. AARM fills this gap.

Current Focus Areas


Specification Maintenance and Evolution. AARM v1.0 is published. The Working Group maintains the specification through versioned releases on GitHub, with formal change control and public peer review for substantive amendments.

Threat Model. AARM addresses eleven attack vectors specific to AI-driven actions: prompt injection, malicious tool outputs, confused deputy, over-privileged credentials, data exfiltration, goal hijacking, intent drift, memory poisoning, cross-agent propagation, side-channel leakage, and environmental manipulation. The Working Group continues to expand the threat model as new attack patterns emerge in the agent ecosystem.

Conformance Requirements. Systems claiming AARM compliance must satisfy nine requirements (R1 through R9), grouped into AARM Core (R1 through R6, baseline runtime security guarantees) and AARM Extended (R1 through R9, comprehensive runtime security with operational maturity features). Conformance reviews are conducted by independent reviewers and published openly.

Implementation Architectures. AARM defines four implementation architectures with distinct trust properties: Protocol Gateway, SDK / Instrumentation, Kernel / eBPF, and Vendor Integration. The Working Group publishes architecture selection guidance and layered deployment patterns for defense-in-depth.

Builders Registry. A public registry of conformant and aligned implementations, enabling buyers to discover vendors and open-source projects that meet AARM requirements.

Benchmarks. The Working Group is developing open benchmarks to measure AARM-conformant systems on detection efficacy, decision latency, and resilience against the eleven threat categories, giving buyers and builders a shared yardstick for runtime security performance.

Working Group Leadership

Josh Buker
Josh Buker

Josh Buker

Research Analyst, CSA

Working Group Co-Chairs

Herman Errico
Herman Errico

Herman Errico

Akul Loomba
Akul Loomba

Akul Loomba

Diana Kelley
Diana Kelley

Diana Kelley

Chris Hughes
Chris Hughes

Chris Hughes

Co-Founder and CISO at Aquia

Chris currently serves as the Co-Founder and CISO of Aquia. Chris has nearly 20 years of IT/Cybersecurity experience. This ranges from active duty time with the U.S. Air Force, a Civil Servant with the U.S. Navy and General Services Administration (GSA)/FedRAMP as well as time as a consultant in the private sector. In addition, he also is an Adjunct Professor for M.S. Cybersecurity programs at Capitol Technology University and University of...

Read more

Publications in ReviewOpen Until
Confidential Computing: Simplifying Trust in the Modern EnterpriseMay 20, 2026
CSA Zero Trust Program Management GuidanceMay 30, 2026
Zero Trust Microsegmentation GuidanceJun 10, 2026
View all
Who can join?

Anyone can join a working group, whether you have years of experience or want to just participate as a fly on the wall.

What is the time commitment?

The time commitment for this group varies depending on the project. You can spend a 15 minutes helping review a publication that's nearly finished or help author a publication from start to finish.

Virtual Meetings

Attend our next meeting. You can just listen in to decide if this group is a good for you or you can choose to actively participate. During these calls we discuss current projects, and well as share ideas for new projects. This is a good way to meet the other members of the group. You can view all research meetings here.

Open Peer Reviews

Peer reviews allow security professionals from around the world to provide feedback on CSA research before it is published.

Learn how to participate in a peer review here.

Confidential Computing: Simplifying Trust in the Modern Enterprise

Open Until: 05/20/2026

Confidential Computing, a paradigm securing data in its active state, emerges as a pivotal safeguard in an era where data u...

CSA Zero Trust Program Management Guidance

Open Until: 05/30/2026

As organizations adopt Zero Trust (ZT) security strategies, it is critical they have the appropriate guidance and resources...

Zero Trust Microsegmentation Guidance

Open Until: 06/10/2026

Microsegmentation is a foundational Zero Trust strategy that strengthens security by enforcing explicit, fine-grained commu...

Premier AI Safety Ambassadors

Premier AI Safety Ambassadors play a leading role in promoting AI safety within their organization, advocating for responsible AI practices and promoting pragmatic solutions to manage AI risks. Contact [email protected] to learn how your organization could participate and take a seat at the forefront of AI safety best practices.