Web Application Security: The OWASP Top 10 in Practice
The OWASP Top 10 is a widely used awareness document that ranks the most critical security risks to web applications, drawing on data contributed by security testers and a community survey. The 2025 edition keeps broken access control first, broadens the old vulnerable components category into software supply chain failures, and adds the mishandling of exceptional conditions. A list is only useful if it changes how software is built, so this article turns the categories into practical controls.
At a glance
- A01
- Broken access control remains the top risk: users reaching data or actions they should not.
- 2025
- The current edition, which updates the 2021 list with new and merged categories.
- Server side
- Every authorisation decision must be enforced on the server, never only in the browser.
- ASVS
- The OWASP Application Security Verification Standard gives testable requirements beyond the Top 10.
The problem
Teams often treat the Top 10 as a checklist for a penetration test at the end of the project. By then, problems such as missing authorisation checks or insecure design are spread across the codebase and expensive to fix.
Web applications for connected products carry extra risk. A flaw in the cloud API can expose every customer device at once, and device management functions such as firmware updates and remote commands are exactly what an attacker wants to reach.
The Top 10 is a starting point for awareness, not a definition of secure. Design the controls in, then test that they hold.
Where to start
Access control causes many of the most serious breaches and is easy to get wrong, so centralise it: one authorisation layer that every API call passes through, denying by default and checking ownership of each object requested, not just whether the user is logged in.
Configuration and the supply chain come next. Use secure defaults, remove sample accounts and debug endpoints, pin and scan dependencies, and verify the integrity of build artefacts. For requirements to test against, OWASP ASVS turns these areas into specific, verifiable statements.
What good looks like
Threat model the application at design time, listing assets, users, trust boundaries and the categories that apply to each interface.
Build the controls into frameworks and shared components: parameterised queries, a central authorisation layer, vetted authentication, and consistent error handling that fails closed.
Test continuously with dependency scanning, static analysis and dynamic scanning in CI, and commission independent testing before major releases.
| Categories | Practical controls |
|---|---|
| A01 Broken Access Control; A07 Authentication Failures | Central server-side authorisation, deny by default, MFA, vetted session handling |
| A02 Security Misconfiguration; A04 Cryptographic Failures | Hardened defaults, no debug in production, TLS everywhere, managed keys |
| A03 Software Supply Chain Failures; A08 Software or Data Integrity Failures | SBOM, dependency scanning, signed builds and updates |
| A05 Injection; A06 Insecure Design | Parameterised queries, output encoding, threat modelling |
| A09 Logging and Alerting Failures; A10 Mishandling of Exceptional Conditions | Audit logs, actionable alerts, errors that fail closed |
Security across the lifecycle
- Design: Threat model, trust boundaries
- Build: Secure frameworks and defaults
- Verify: SAST, DAST, dependency scans
- Deploy: Hardened configuration, managed secrets
- Operate: Logging, alerting, patching
What it changes
Reduced Exposure
The most common and damaging classes of web vulnerability are addressed by design.
Consistent Controls
Shared components apply the same protections to every endpoint.
Faster Response
Logging and alerting reveal attacks while they happen, not months later.
Buyer Confidence
Documented controls and test evidence support customer security reviews.
Where to go next
Map each category to an owner and a control in your own system. The list is generic; the controls have to be specific to your architecture.
Watch for the next edition. OWASP revises the Top 10 every few years, and categories move as attack data changes.
Problems this prevents
- Users reaching another customer's data
- Debug endpoints left in production
- Dependencies with known vulnerabilities
- Attacks noticed only after the damage
Discuss your project
Email support@aavico.com or use Get in Touch when the website finishes loading.