The OWASP Top 10, Explained for Certification Candidates
7 min read6 views
Super Admin
Almost every security certification eventually asks you about web application weaknesses, and the OWASP Top 10 is the vocabulary those questions are written in. You do not need to be a developer to master it, but you do need to know what each category means, what it looks like in practice and which control an examiner expects you to reach for.
This guide walks through the 2021 edition, the one most current study material is built around. OWASP revises the list every few years, so check owasp.org for a newer edition before your exam.
What the OWASP Top 10 actually is
The Open Worldwide Application Security Project is a nonprofit community that publishes free guidance on software security. The Top 10 is its best-known document: an awareness list of the most significant categories of web application risk, ranked using contributed vulnerability data and a community survey.
Two points are worth fixing in your mind before the exam:
- It is an awareness document, not a standard. If you need a testable set of requirements, OWASP points you to the Application Security Verification Standard (ASVS). A question asking which OWASP resource provides verifiable requirements is fishing for ASVS, not the Top 10.
- The entries are categories, not single bugs. "Injection" covers SQL injection, OS command injection, LDAP injection and, since 2021, cross-site scripting. Each category maps to a group of CWE (Common Weakness Enumeration) entries.
The ten categories at a glance
Read the table once for the shape of the list, then come back to it when you review. The "typical control" column is the answer most exam questions are looking for.
| ID | Category | What it means | Typical control |
|---|---|---|---|
| A01 | Broken Access Control | Users can act outside their intended permissions. | Deny by default; enforce authorization on the server for every request. |
| A02 | Cryptographic Failures | Sensitive data is exposed through missing or weak cryptography. | TLS everywhere, strong algorithms, proper key management, slow password hashing. |
| A03 | Injection | Untrusted input is interpreted as code or commands, including XSS. | Parameterized queries, output encoding, input validation. |
| A04 | Insecure Design | The flaw is in the design itself, not the implementation. | Threat modeling, secure design patterns, abuse-case testing. |
| A05 | Security Misconfiguration | Defaults, verbose errors, open storage, unneeded features. | Hardened baselines, automated configuration checks. |
| A06 | Vulnerable and Outdated Components | Libraries or platforms with known vulnerabilities. | Software inventory (SBOM), dependency scanning, patching. |
| A07 | Identification and Authentication Failures | Weak login, session or credential handling. | MFA, rate limiting, secure session management. |
| A08 | Software and Data Integrity Failures | Code or data trusted without verifying its integrity. | Signed updates, protected CI/CD pipelines, safe deserialization. |
| A09 | Security Logging and Monitoring Failures | Attacks are not recorded, noticed or acted upon. | Centralized logging, alerting, a tested incident response process. |
| A10 | Server-Side Request Forgery | The server is tricked into fetching an attacker-chosen URL. | Allow-list destinations, block internal address ranges, segment egress. |
The four categories most worth your study time
Every category can appear, but in practice four come up again and again in exam scenarios because they map neatly onto core security principles. Learn these with an example each and the rest of the list becomes much easier to reason about.
A01 Broken Access Control
This moved to the top spot in 2021. The classic example is an insecure direct object reference: a user views their invoice at a URL ending in an invoice number, changes the number, and sees someone else's invoice. The application authenticated the user but never checked whether this user may read that record.
Other forms include reaching admin functions simply by browsing to them, changing a role field in a request body, and relying on hidden buttons in the user interface as if hiding were enforcement. The exam answer is almost always the same principle: authorization is checked on the server, on every request, and the default is deny.
A02 Cryptographic Failures
Previously called "Sensitive Data Exposure", the category was renamed to point at the root cause. Examples include login pages served over plain HTTP, passwords stored with a fast unsalted hash, hard-coded keys in source code and outdated protocols left enabled for compatibility.
Know the distinction examiners love: passwords should be hashed with a deliberately slow, salted algorithm such as bcrypt, scrypt or Argon2, not encrypted. Encryption is reversible by design; a password store should not be.
A03 Injection
Injection happens when data crosses into an interpreter and is treated as instructions. SQL injection is the textbook case, and cross-site scripting is the same idea aimed at the browser: user input is placed into a page without encoding and the browser executes it as script.
The snippet below is deliberately simplified pseudo-code, not any particular language. It shows why string-building a query is dangerous and what the fix looks like.
// VULNERABLE: user input is concatenated into the query text
query = "SELECT id, name FROM accounts WHERE email = '" + input.email + "'"
db.execute(query)
// An attacker submits: ' OR '1'='1
// The database receives: SELECT id, name FROM accounts WHERE email = '' OR '1'='1'
// Every row matches, so every account is returned.
// FIXED: the query text never changes; the value is sent separately
query = "SELECT id, name FROM accounts WHERE email = ?"
db.execute(query, [input.email])
// The driver treats input.email strictly as data, never as SQL.
Notice what the fix does not rely on: it does not try to strip quotes or blacklist keywords. Input validation is a good additional layer, but parameterization is the primary control because it removes the ambiguity between code and data entirely. For XSS, the equivalent primary control is context-aware output encoding, supported by a Content Security Policy.
A07 Identification and Authentication Failures
This covers everything that lets an attacker assume another identity: permitting credential stuffing with no rate limit, accepting weak or well-known passwords, exposing session identifiers in URLs, failing to invalidate sessions on logout, and weak password recovery flows.
Expect scenario questions that describe a symptom, such as thousands of failed logins from many addresses against many accounts, and ask for the best control. Multi-factor authentication is usually the strongest answer, with throttling, breached-password checks and secure session handling as supporting measures.
How exams frame OWASP questions
Certification exams rarely ask you to recite the list in order. Instead they describe a situation and ask you to classify it or choose a control. A few patterns repeat:
- Symptom to category. "A user changes an ID in the URL and sees another customer's order." That is broken access control, not injection, even though input was modified.
- Category to best control. "Which control most effectively prevents SQL injection?" Parameterized queries beat input filtering and beat a web application firewall, which is a compensating layer.
- Design versus implementation. If the scenario describes a business process with no limit on how many times a discount can be applied, the problem is insecure design. No amount of code review fixes a missing requirement.
- Supply chain. An unpatched open-source library points to A06; an update channel that accepts unsigned packages points to A08.
Connecting the list to testing work
If you are heading towards penetration testing or a role like CySA+, the Top 10 is also a map for structuring an assessment. The companion Web Security Testing Guide describes how to test for each class of weakness, and the OWASP Cheat Sheet Series gives concise defensive guidance per topic.
A sensible study exercise is to take each category and write down three things: one realistic way it appears, one way a tester would detect it, and one control that prevents it. Ten short rows of notes like that will serve you better on exam day than memorizing ranks.
Conclusion
The OWASP Top 10 rewards understanding over memorization. If you can look at a scenario and say which principle failed, whether authorization, cryptography, the boundary between data and code, or identity, you will answer most web security questions correctly. Learn the four core categories deeply, know the primary control for each of the ten, and always confirm which edition your exam is based on.
38 international certifications
Which certification are you preparing for?
Question banks, flashcards and mock exams built on each exam's official outline.
Browse certifications

Discussion (0)
No discussion here yet — be the first to comment.
Please sign in to join the discussion.