AAK-A2A-002: Agent Card lacks authentication requirement
- Severity
- HIGH
- Category
- A2A Protocol (
a2a-protocol) - Scanner
agent_audit_kit/scanners/a2a_protocol.py- Auto-fixable
- No.
- SARIF name
A2aNoAuth
What it detects
An A2A Agent Card does not require authentication for interactions.
How to fix
Add an authentication object to the Agent Card that names a real scheme (for example OAuth 2.0 or an API key) rather than none. The rule reads the card's authentication (or auth) field and fires when it is missing or its type is none.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-A2A-002
Limitations
Reads the authentication (or auth) key and reports it when it is absent, null, the string none, or an object whose type is none. An empty authentication: {} or an object that lists no real scheme ({"schemes": ["none"]}) counts as declared. Only agent-card.json and .well-known/agent.json in the project root and files named *agent-card*.json are read; a card at public/.well-known/agent.json is not.
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-02 (A2A No Auth)
- 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-002.md: the page then shows that text, with the registry reference appended under it.