Conformance Testing - AARM/CSA Specification v1.0

Validation Process Beta

Conformance validation is performed through the AARM Conformance MCP server. You will be guided by our agent, which runs the assessment end-to-end against your implementation — there are no manual checklists to fill out.

Request an activation key

Submit the form below with your organization name, product name, and target conformance level (Core or Extended). If your organization is on the allow-list, you will receive an activation key by email. Only listed organizations can run the assessment.

Connect to the AARM MCP server

Add the server to Claude Desktop or Claude Code using the instructions below. The server URL is:

https://aarm-conformance-mcp.herman-d10.workers.dev/

Run the assessment

Start a conversation with Claude and ask it to run the AARM conformance assessment. The agent will walk you through each check, collect evidence, and produce a validation report.

Install on Claude Code

Run this in your terminal:

claude mcp add --transport http aarm-conformance https://aarm-conformance-mcp.herman-d10.workers.dev/

Then launch Claude Code and ask it to start the AARM conformance assessment.

Install on Claude Desktop

Open your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the AARM server to the mcpServers section:

{
  "mcpServers": {
    "aarm-conformance": {
      "type": "http",
      "url": "https://aarm-conformance-mcp.herman-d10.workers.dev/"
    }
  }
}

Restart Claude Desktop. The AARM agent will be available in your next conversation.

Request access

Testing Approach

Each conformance requirement (R1 through R9) includes a Verification section describing the minimum test to confirm conformance. Conformance testing covers two areas: technical requirements (R1 through R9), which verify the runtime behavior of the system, and organizational requirements, which verify that the organization meets the conditions for publicly describing its system as AARM-conformant.

What Gets Tested

Organizational Requirements

Condition	Verification	Expected Result
Community engagement	Verify TWG membership or participation in conformance discussions	Organization has an active representative in the AARM community
Production deployment	Confirm the system is deployed and serving active customers	System is live in production, not solely a design document or roadmap
Security certification	Request evidence of certification	Organization holds at least one recognized security certification (e.g., SOC 2 Type II, ISO 27001, FedRAMP) relevant to the operating environment
Benchmarking commitment	Confirm willingness to participate	Organization agrees to participate in future AARM benchmarking efforts measuring policy detection and enforcement metrics

Technical Requirements

Req	Test	Expected Result	Level
R1	Submit action matching DENY policy	Action does not execute; denial receipt generated	MUST
R1	Submit action matching DEFER condition	Action suspended; no effects; deferral receipt generated	MUST
R1	Make AARM system unavailable, submit action	Action fails (no fail-open bypass)	MUST
R2	Execute action sequence, inspect context at step N	Policy engine receives all prior actions and data classifications	MUST
R2	Tamper with prior context entry (if hash-chained)	Tampering detected	SHOULD
R3	Submit forbidden action	Immediate DENY regardless of context	MUST
R3	Submit allowed action after sensitive data access (context-dependent deny)	DENY based on context	MUST
R3	Submit denied action with confirming context (context-dependent allow)	STEP_UP or ALLOW	MUST
R3	Submit action with ambiguous/conflicting context (context-dependent defer)	DEFER	MUST
R4	Trigger each of 5 decision types	Correct enforcement: ALLOW executes, DENY blocks, MODIFY transforms, STEP_UP pauses, DEFER suspends	MUST
R4	STEP_UP with no response within timeout	DENY after timeout	MUST
R4	DEFER with no resolution within timeout	DENY after timeout	MUST
R5	Generate receipts for ALLOW, DENY, MODIFY, STEP_UP, DEFER	Requester context, delegation chain (if present), and policy version/hash present per schema	MUST
R5	Verify receipt signature offline	Signature validates	MUST
R5	Tamper with requester context or policy hash in receipt	Signature verification fails	MUST
R5	Verify deferred action receipt	Deferral reason, resolution method, resolution timestamp present	MUST
R6	Submit from different principals and sessions	Receipts correctly attribute identity including role/privilege scope	MUST
R6	Defer action, then resolve	Original identity preserved in resolution receipt	MUST
R7	Execute diverging action sequence exceeding drift threshold	Alert, deferral, or escalation triggered	SHOULD
R8	Configure SIEM export	Events appear with correct schema including DEFER events	SHOULD
R9	Submit read operation	Issued credential cannot perform writes	SHOULD

Documentation Index

​Validation Process Beta

​Install on Claude Code

​Install on Claude Desktop

​Request access

​Testing Approach

​What Gets Tested

​Organizational Requirements

​Technical Requirements