OWASP Top 10 (2021) mapping

OWASP Top 10 (2021): 9 of 10 categories

15 rules map to 9 of 10 categories. The table also shows categories that static source or configuration checks cannot cover.

9 of 10 categories have compiled-in coverage

  1. 09 Categories coveredBacked by rules in the engine.
  2. 15 Rules mappedEach mapping is published and inspectable.
  3. ALL Unmapped categoriesEmpty categories remain visible in the table.
Generated from rule metadata in the installed engine

Reach describes how much of a category static source analysis can see. Categories marked poor need runtime data or design review.

CategoryReachRules
A01:2021 Broken Access Controlpartialcsrf-cross-origin-post, open-redirect
A02:2021 Cryptographic Failurespartialweak-crypto
A03:2021 Injectiongoodsql-injection
A04:2021 Insecure Designpoornot reachable from source
A05:2021 Security Misconfigurationgoodcors-permissive, insecure-cookie, security-headers-missing, stack-trace-leak
A06:2021 Vulnerable and Outdated Componentspartialknown-vulnerable-dependency, unpinned-dependency
A07:2021 Identification and Authentication Failurespartialhardcoded-secret
A08:2021 Software and Data Integrity Failurespartialci-unpinned-action, install-lifecycle-script
A09:2021 Security Logging and Monitoring Failurespartialsensitive-data-logged
A10:2021 Server-Side Request Forgery (SSRF)goodssrf

Why A04 has no rules

Insecure Design covers choices such as a missing rate limit or an unsafe recovery flow. Those problems do not have a reliable AST pattern and need design review or runtime evidence.

The other taxonomy

Rules that read agent configuration map to OWASP ASI 2026 instead, and that table is separate because agent-config findings do not increase application Top 10 coverage.

npx owlwarden coverage      # printed from the engine you have installed

Keep reading