The ten 2021 categories and what automated scanning can do for each
A01: Broken Access Control. DAST probes for privilege escalation, insecure direct object references and missing function-level checks. SAST detects missing authorisation checks in code. Neither knows your business rules, so manual testing still matters here.
A02: Cryptographic Failures. SAST flags MD5, SHA-1, DES, AES-ECB and Math.random() in security contexts. DAST checks TLS configuration and certificate validity.
A03: Injection. DAST sends SQL, NoSQL, OS command and template injection payloads to live endpoints. SAST traces taint flows from user input to dangerous sinks.
A04: Insecure Design. This is a design problem and no scanner finds it directly. Threat modelling and manual penetration testing address it.
A05: Security Misconfiguration. Health checks read security headers (HSTS, CSP, X-Frame-Options, Referrer-Policy) and TLS settings. Active testing adds CORS behaviour, cookie flags and default credentials.
A06: Vulnerable and Outdated Components. SCA checks direct and transitive dependencies against vulnerability databases. An SBOM gives you the component inventory.
A07: Identification and Authentication Failures. DAST tests for broken authentication flows and session handling flaws.
A08: Software and Data Integrity Failures. SCA flags known-bad package versions. Lockfiles, pinned versions and a reviewed build pipeline reduce the exposure.
A09: Security Logging and Monitoring Failures. No scanner can confirm that you log the right events and that someone reads them. A log analysis tool can look for attack traces in the logs you already have.
A10: Server-Side Request Forgery (SSRF). DAST sends SSRF payloads to discovered endpoints, with out-of-band callbacks to catch the blind cases.
What the 2025 edition changed
The 2025 edition keeps Broken Access Control at the top and folds SSRF into it. Security Misconfiguration moves up to second place. Vulnerable and Outdated Components is widened into Software Supply Chain Failures, and a new category, Mishandling of Exceptional Conditions, covers errors that are handled badly or fail open. Cryptographic Failures, Injection, Insecure Design, Authentication Failures, Software or Data Integrity Failures, and Logging and Alerting Failures remain, with some renamed and reordered.
The practical effect on a testing programme is small. The same scanner types cover the same ground, with more weight on dependencies, build pipelines and error handling. If a customer or auditor asks which edition you test against, say which one your reports are labelled with, and check owasp.org for the exact wording of each category.
Getting started
Spoorder's free Health Check (free account required) reads security headers and TLS settings, with results in under a minute. Broader coverage needs DAST, SAST and SCA, which are available on Builder and above, and Log Inspector on Pro and above. A04 and A09 need people and process whichever tools you use.
Ready to scan your application?
Free health check: HTTPS, TLS and security headers for one URL, in about a minute. Free account, no credit card.
Scan your app free →