AAK-A2A-008: A2A connection lacks mutual authentication
- Severity
- HIGH
- Category
- A2A Protocol (
a2a-protocol) - Scanner
agent_audit_kit/scanners/a2a_protocol.py- Auto-fixable
- No.
- SARIF name
A2aNoMutualAuth
What it detects
Two agents establish an A2A connection where only the caller authenticates. The callee is trusted by URL alone — easy to spoof.
How to fix
Require mutual authentication and declare it on the card: set mutual (or mutual_tls) to true in the authentication object, or use a scheme such as mtls. The rule fires when the scheme is bearer or OAuth and none of those is present.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-A2A-008
Limitations
Reads authentication.scheme, a single string, and reports it when it contains bearer or oauth and the block declares no mutual flag or mtls scheme. A card that lists its schemes ("schemes": ["Bearer"]) or uses another scheme (apikey, basic) is not reported.
References
- OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse), ASI07 (Insecure Inter-Agent Communication)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-A2A-05
- CSA AI Controls Matrix (AICM): IAM-01
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-A2A-008.md: the page then shows that text, with the registry reference appended under it.