The OWASP Top 10 Proactive Controls is a catalog of ten practices — covering access control, cryptography, input validation and more — that developers build into code to prevent security issues before they happen, maintained by the OWASP Foundation. Where the better-known OWASP Top 10 documents the vulnerability categories most likely to show up in a web application, Proactive Controls documents the other side of that coin: the practices a developer can build into the code from the start to avoid those categories ever appearing. OWASP's own index page for the project describes proactive controls as "a catalog of better practices, a set of items developers can embrace and implement in their code bases to avoid many common security issues."
Key takeaways
- Every control page follows the same structure, per the index page: Description, Threats, Implementation, Vulnerabilities Prevented, References and Tools.
- The control numbers moved, so a "C5" in a 2019 code-review checklist is not the C5 of 2024.
- OWASP's Related OWASP Projects page states that "each control in this document will map to one or more items in the risk-based OWASP Top 10," with the mapping in each control's "Vulnerabilities Prevented" section.
- C6, Keep your Components Secure, is the control that maps most directly onto supply-chain security work SoftWSP already covers in its firmware SBOM and SBOM minimum elements guides.
Who is it for?
The project's "About this Project" page is explicit about audience and scope: it is "primarily written for developers," though "development managers, product owners, Q/A professionals, program managers, and anyone involved in building software can also benefit from this document." It also sets realistic expectations about depth, describing itself as "a starting point rather than a comprehensive set of techniques and practices" — a foundational awareness document, not a full requirements specification.
What are the 10 controls (C1-C10)?
OWASP's own Top 10 index page lists these controls, in this order, in the current (2024) edition:
| # | Control | What it covers |
|---|---|---|
| C1 | Implement Access Control | Enforcing who may access which resource, consistently across every layer (business logic, database rows, every API and UI path) |
| C2 | Use Cryptography to Protect Data | Protecting sensitive data in storage and transit, especially data covered by privacy or financial-data rules |
| C3 | Validate all Input & Handle Exceptions | Treating all input as untrusted and failing safely when it's malformed |
| C4 | Address Security from the Start | Designing a secure architecture during initial design rather than remediating after the fact |
| C5 | Secure By Default Configurations | Shipping and deploying with secure defaults rather than requiring a user to opt into safety |
| C6 | Keep your Components Secure | Tracking and patching the libraries and frameworks an application depends on |
| C7 | Secure Digital Identities | Authentication, session management and identity assurance |
| C8 | Leverage Browser Security Features | Using browser-enforced controls (headers, cookie flags, CSP and similar) as a defense layer |
| C9 | Implement Security Logging and Monitoring | Recording and actively reviewing security-relevant events during runtime |
| C10 | Stop Server Side Request Forgery | Preventing a server from being coerced into making requests on an attacker's behalf |
Every control page follows the same structure, per the index page: Description, Threats, Implementation, Vulnerabilities Prevented, References and Tools.
OWASP's own navigation also shows archived 2014, 2016 and 2018 editions of this project, plus — as checked for this guide — a draft future edition, so this exact ordering and the C10 entry (new in the 2024 edition) are not guaranteed to be stable across releases; a team citing a specific control number in internal documentation should link the specific edition rather than just "the OWASP Proactive Controls." The project's site configuration on GitHub labels that draft section "Future Top 10 (WIP)"; on 12 November 2026 its C1-C10 titles matched the 2024 list.
What changed from the 2018 list?
The control numbers moved, so a "C5" in a 2019 code-review checklist is not the C5 of 2024. The 2018 titles below come from the 2018 archive; the "closest 2024 control" column is this guide's reading of the two lists, as OWASP does not publish a crosswalk:
| 2018 control | Closest 2024 control |
|---|---|
| C1 Define Security Requirements | C4 Address Security from the Start (in part) |
| C2 Leverage Security Frameworks and Libraries | C6 Keep your Components Secure |
| C3 Secure Database Access | C3 Validate all Input & Handle Exceptions (injection) |
| C4 Encode and Escape Data | C3 (output escaping) |
| C5 Validate All Inputs | C3 |
| C6 Implement Digital Identity | C7 Secure Digital Identities |
| C7 Enforce Access Controls | C1 Implement Access Control |
| C8 Protect Data Everywhere | C2 Use Cryptography to Protect Data |
| C9 Implement Security Logging and Monitoring | C9 (same title) |
| C10 Handle All Errors and Exceptions | C3 (exceptions) |
| — | C5 Secure By Default Configurations, C8 Leverage Browser Security Features, C10 Stop Server Side Request Forgery (no 2018 equivalent) |
The net effect: four 2018 controls about data handling collapsed into one C3, and three slots went to secure defaults, browser defenses and SSRF.
Which Top 10 risks does each control prevent?
OWASP's Related OWASP Projects page states that "each control in this document will map to one or more items in the risk-based OWASP Top 10," with the mapping in each control's "Vulnerabilities Prevented" section. Those sections cite the 2021 Top 10; the 2025 column follows the changes OWASP describes in its Top 10:2025 guide:
| Control | Vulnerabilities Prevented (2024 page) | Top 10:2025 equivalent |
|---|---|---|
| C1 | A01:2021 Broken Access Control; CWE-862, CWE-863 | A01:2025 |
| C2 | A02:2021 Cryptographic Failures | A04:2025 |
| C3 | SQL, OS command, command and code injection (2023 CWE Top 25) | A05:2025; exceptions also A10:2025 |
| C4 | A04:2021 Insecure Design; business logic flaws | A06:2025 |
| C5 | A05:2021 Security Misconfiguration | A02:2025 |
| C6 | Vulnerable and outdated components (A06:2021) | A03:2025 |
| C7 | A07:2021 Identification and Authentication Failures | A07:2025 |
| C8 | XSS, CSRF, clickjacking, session hijacking | spread across A01, A05, A07 |
| C9 | Brute-force attacks against login mechanisms | A09:2025 |
| C10 | A10:2021 Server-Side Request Forgery | inside A01:2025 |
The C3 page adds a caution that teams often miss: input validation "should not be used as the primary method of preventing XSS, SQL Injection and other attacks" — parameterized queries and output encoding do that job.
What do four of the controls say in detail?
C1, Implement Access Control, is framed around a layering problem as much as a single check: OWASP's own C1 page notes access control "often applies on multiple levels, e.g., given an application with a database backend, it applies both on the business logic level as well as on a database row level," and that every path into the application — API or UI — "must be aligned, i.e., use the same access control checks." It also distinguishes Role-Based Access Control (permissions tied to roles) from Attribute-Based Access Control (permissions evaluated from arbitrary user, resource and environment attributes), and warns that re-engineering access control after the fact, once a pattern is chosen, is "often difficult and time-consuming."
C6, Keep your Components Secure, is the control that maps most directly onto supply-chain security work SoftWSP already covers in its firmware SBOM and SBOM minimum elements guides. OWASP's own C6 page recommends maintaining Software Bills of Materials (SBOMs) and using continuous monitoring tooling (it names OWASP's own Dependency-Track project as an example) to detect publicly disclosed vulnerabilities in dependencies automatically, rather than relying on a one-time audit at release time.
C9, Implement Security Logging and Monitoring, separates two related but distinct activities. OWASP's own page frames logging as something "most developers already use for debugging and diagnostic purposes," with security logging as the same concept applied specifically to security-relevant runtime events, while monitoring is the live, ideally automated, review of those logs with the explicit goal of detecting and responding to incidents — logging without review does not satisfy C9 on its own.
C10, Stop Server Side Request Forgery, is the newest addition and the only control named after a specific attack rather than a defensive practice. OWASP's own page distinguishes it from ordinary injection: "while Injection Attacks typically target the victim server itself, Server-Side Request Forgery (SSRF) attacks try to coerce the server to perform a request on behalf of the attacker," letting an attacker reuse the server's own network position and credentials against internal systems the attacker could not otherwise reach directly.
How do the controls apply to firmware and device software?
The controls are written with web applications in mind, but each one has a direct firmware reading. The middle column quotes the 2024 control pages:
| Control | What OWASP says | Firmware / device practice |
|---|---|---|
| C1 | "access control should always be denied" when code throws an error | Every CGI handler, local API and debug UART menu runs the same authorization check; failures deny |
| C2 | "Do not implement cryptographic routines"; "Build application features to support and handle key rotation" | Use the SoC's crypto engine or a maintained library; per-device keys, not one key in every image |
| C3 | Check data is "syntactically and semantically valid (in that order)" | Length and range checks before memcpy in protocol parsers; reject malformed packets without crashing |
| C4 | "Identify and minimize your exposed components" | Remove Telnet, sample CGI and unused daemons from release builds |
| C5 | "Software should start in a secure state without requiring extensive user configuration" | No shared default password; remote services off until set up |
| C6 | Create SBOMs "from within the build pipeline" and monitor them | One SBOM per firmware release, matched against new CVEs for the support period |
| C7 | Points to NIST SP 800-63B and its three assurance levels | Per-device credentials for the web UI and cloud pairing; MFA on the vendor's fleet console |
| C8 | Lists browser defenses against XSS, CSRF and clickjacking | Set CSP, HttpOnly and SameSite on the embedded web server |
| C9 | "Do not log sensitive information"; "Protect log integrity" | Log failed logins and config changes, never Wi-Fi keys; forward to a central service where the device has one |
| C10 | "check the target against an allow-list" for outgoing requests | NTP, update and "test connection" URL fields cannot reach internal or link-local addresses |
The C5 page also lists among its threats "default, weak, or well-known credentials that haven't been changed from their out-of-the-box state". The C2 page warns against keeping secrets "in code, config files or pass them through environment variables," which for firmware means keys do not sit in the root filesystem. For the device-specific verification standard behind these practices, see OWASP ISVS; for the boot-time half of C2 and C6, see secure boot and hardware root of trust.
Worked example: how would a team review one firmware feature against the controls?
Synthetic example, not a customer case. A smart-plug team adds "upload configuration backup" to its embedded web UI and reviews the change against the ten controls before merge:
C1:the upload handler sits behind the same session check as other admin routes, and an exception in the check returns 403. Pass. C3:the parser accepts any file size. Fix: reject files above 64 KB and check every field length and range before copying into the config struct. C2:the backup holds the Wi-Fi password in clear text. Fix: encrypt it with a per-device key held in the secure element. C5:the feature is on by default with no confirmation. Accepted, because it requires an authenticated admin session. C6:the new JSON library is added to the SBOM, and its version is checked for known CVEs before release. C9:each restore writes a log line with time and source address, without the file contents. C10:the restore can set the update server URL. Fix: allow only the vendor's update hostnames.
Three of the seven checks needed a fix (C2, C3 and C10), and a review limited to "is it behind a login?" would have missed all three.
What are the common pitfalls?
- Citing a control number without the year. "C3" means Secure Database Access in 2018 and Validate all Input & Handle Exceptions in 2024.
- Using it as an audit checklist. OWASP calls it "a starting point"; pass/fail requirements belong in ASVS.
- Skipping C8 and C10 as "web only." An embedded web server is a web server, and a device that fetches URLs on request can be steered by SSRF.
- Relying on input validation alone. C3 itself says it is not the primary defense against injection.
- Treating C6 as a one-time scan. New CVEs keep arriving for components in firmware already shipped.
Where does it fit next to the rest of the OWASP catalog?
Proactive Controls, ASVS and SAMM answer three different questions and are designed to be used together rather than as alternatives: Proactive Controls teaches a developer what to do while writing code; ASVS gives a verifiable, testable requirements checklist to build or audit an application against; SAMM assesses and matures an organization's software security process over time, independent of any one application. A device maker or firmware team already working through SoftWSP's CRA or IEC 62443-4-1 secure development lifecycle guidance can treat Proactive Controls as the developer-facing training layer underneath those program-level requirements, not a replacement for them. For testing the finished firmware, see the cluster's OWASP Firmware Security Testing Methodology.
How should a team start?
Use it for onboarding, not auditingProactive Controls is written to teach practices, not to generate a pass/fail compliance report — use ASVS for that. Start with C1 and C3Access control and input validation remain the controls most directly tied to the highest-impact vulnerability categories in the OWASP Top 10. Treat C6 as a continuous process, not a release gateNew vulnerabilities are disclosed in existing dependencies constantly; a one-time dependency audit at ship time misses everything disclosed afterward. Re-check the edition you're citingOWASP maintains multiple archived editions side by side; confirm whether your team's internal references point at the 2018 or 2024 control numbering before relying on a specific "Cx" label in documentation.
SoftWSP supports C6 for firmware: it extracts an SBOM from the image as CycloneDX 1.6 JSON, matches the components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report that an engineer reviews; watchlist alerts flag new CVEs by CVE id or vendor-product. Severity per finding can be checked in the free CVSS calculator. See device & firmware security services.
This guide summarises a public OWASP community project; it does not constitute legal or compliance advice.
Put this guide to work
Frequently asked questions
What is the OWASP Top 10 Proactive Controls?
A catalog of ten secure-coding practices maintained by the OWASP Foundation. The project's own page states its goal is "to raise awareness about application security by describing the most important areas of concern that software developers must be aware of," and its index page describes proactive controls as "a catalog of better practices, a set of items developers can embrace and implement in their code bases to avoid many common security issues." The project states it is "primarily written for developers," though it adds that "development managers, product owners, Q/A professionals, program managers, and anyone involved in building software can also benefit from this document."
What are the 10 controls, in order?
Per the project's own Top 10 index page: C1 Implement Access Control, C2 Use Cryptography to Protect Data, C3 Validate all Input & Handle Exceptions, C4 Address Security from the Start, C5 Secure By Default Configurations, C6 Keep your Components Secure, C7 Secure Digital Identities, C8 Leverage Browser Security Features, C9 Implement Security Logging and Monitoring, and C10 Stop Server Side Request Forgery. This is the 2024 edition's ordering and naming; OWASP's own site also shows archived 2014, 2016 and 2018 editions and, as checked for this guide, a draft future edition, so the exact list can change between releases.
How is this different from the OWASP Top 10?
The OWASP Top 10 (see our [OWASP Top 10:2025 guide](/guides/owasp-top-10-2025/)) documents the most critical web application vulnerability *categories* an organization is likely to have — it describes what tends to go wrong. Proactive Controls instead documents *practices a developer does during coding and design* to avoid those issues in the first place; OWASP's own framing is that proactive controls are something developers "embrace and implement" rather than a list of risks to audit against. The two projects are complementary, not competing: a Top 10 vulnerability category like broken access control is exactly what Proactive Controls' C1 is meant to prevent.
How does this relate to OWASP ASVS and SAMM?
Proactive Controls explicitly positions itself as a starting point, not a full specification: the project's own "About" page states it serves as "a starting point rather than a comprehensive set of techniques and practices" for foundational secure-coding awareness. For a verifiable, testable set of security requirements to build or audit against, OWASP's own guidance points to the [Application Security Verification Standard (ASVS)](/guides/owasp-asvs/); for assessing and maturing an organization's overall software security *process* rather than individual code practices, see [OWASP SAMM](/guides/owasp-samm/). A reasonable order of adoption: Proactive Controls to train developers, ASVS to define and verify requirements, SAMM to measure program maturity over time.
Sources
- OWASP: Top 10 Proactive Controls — project page
- OWASP: Top 10 Proactive Controls — About this Project
- OWASP: Top 10 Proactive Controls — The Top 10 (C1-C10 index)
- OWASP: C1 — Implement Access Control
- OWASP: C2 — Use Cryptography to Protect Data
- OWASP: C4 — Address Security from the Start
- OWASP: C6 — Keep your Components Secure
- OWASP: C9 — Implement Security Logging and Monitoring
- OWASP: C10 — Stop Server Side Request Forgery
- OWASP: Top 10 Proactive Controls 2024 archive
- OWASP: Top 10 Proactive Controls 2024 — Related OWASP Projects (each control maps to the OWASP Top 10)
- OWASP: C3 (2024) — Validate all Input & Handle Exceptions
- OWASP: C5 (2024) — Secure By Default Configurations
- OWASP: C7 (2024) — Secure Digital Identities
- OWASP: C2 (2024) — Use Cryptography to Protect Data (key life cycle, secrets)
- OWASP: Top 10 Proactive Controls 2018 — C10 Handle All Errors and Exceptions
- GitHub: OWASP/www-project-proactive-controls — mkdocs.yml (site navigation: Future Top 10 (WIP), 2024, 2018, 2016, 2014)
About this guide
SoftWSP Firmware Security Desk
Covers the Firmware vulnerabilities & fixes cluster: 131 guides.

In this cluster
Questions about this page?
