Audit logging turned off
MediumAV-AUDIT-002Audit & loggingCore packNew in 2.0
What it finds
Audit logging is explicitly switched off.
Why it matters
Without an audit trail you cannot tell what the agent did, for whom, or why — after an incident or for compliance.
What an attacker could do: Agent actions leave no record.
How to fix it
Keep audit logging on in production and record every tool call (who, what, when, result).
Pro shows the corrected code for your exact file, step by step, and re-scans to confirm the fix. See plans
Check details
- Finding code
- AUDIT_LOGGING_DISABLED
- How it detects
- Looks for a specific risky pattern in the code or config.
- Confidence
- Definite: the risky setting is written plainly in the file.
- Scans
- Any text-based agent source or configuration (JS/TS/Python/JSON/YAML)
- OWASP LLM Top 10
- LLM08 - Excessive Agency
- NIST AI RMF
- MS-2.8, GV-1.5
- SOC 2
- CC7.2, CC4.1
Check your agent for this
Paste your agent code or MCP config. The free scan runs all 124 checks in about 10 seconds — no account needed.