A website, a customer portal, an API for partners — all of these are web applications that anyone on the internet can reach, attackers included. The OWASP Top 10 is the best-known list of the main security risks for web applications. Its new edition, the OWASP Top 10:2025, has replaced the 2021 version.
Below: what is in it in plain words, what changed, what a WAF protects against and what it does not, and where a company should start.
What the OWASP Top 10 is
OWASP (Open Worldwide Application Security Project) is a non-profit community that produces open application security materials. OWASP itself calls the Top 10 a standard awareness document for developers. The 2025 edition is based on data from more than 2.8 million applications and a survey of practitioners.
An important caveat from OWASP itself: the Top 10 is primarily an awareness document. Used as a coding or testing standard, it is the bare minimum and just a starting point. For verifiable requirements, OWASP recommends another of its documents — the ASVS (Application Security Verification Standard).
Ten risks in plain words
| No. | Category | What it means for a business |
|---|---|---|
| A01 | Broken Access Control | A user sees or changes someone else’s data: change a number in the page address and see another customer’s account |
| A02 | Security Misconfiguration | Default passwords, unnecessary features, verbose error messages, open cloud storage |
| A03 | Software Supply Chain Failures | Vulnerable or tampered third-party libraries, build tools, updates |
| A04 | Cryptographic Failures | Data is transmitted or stored without proper encryption |
| A05 | Injection | User data is executed as commands: SQL injection, cross-site scripting (XSS) |
| A06 | Insecure Design | The flaw is built in at the design stage, and code alone cannot fix it |
| A07 | Authentication Failures | Weak passwords, no second factor, nothing stops password guessing |
| A08 | Software or Data Integrity Failures | Updates, code or data are accepted without checking that nobody altered them |
| A09 | Security Logging and Alerting Failures | An attack goes unnoticed: there are no logs, or nobody receives the alerts |
| A10 | Mishandling of Exceptional Conditions | A failure mid-operation leaves the system in an unsafe state: money debited but not credited |
According to OWASP data, some form of broken access control and some form of misconfiguration were found in every application tested.
A recent A03 example is the vulnerability in the Brotli library, built into Node.js, .NET and Linux packages: a vulnerability in one component affects every application that uses it. On A07, see “Two-factor authentication for business”.
What changed since 2021
- Two new categories. A03 extends the former “Vulnerable and Outdated Components” to the whole supply chain — building and distributing software. A10 is entirely new.
- Server-side request forgery (SSRF) is now part of A01.
- Security misconfiguration rose from 5th to 2nd place, and injection dropped from 3rd to 5th.
- A09 now stresses alerting, not just monitoring.
What a WAF is
A WAF (web application firewall) sits in front of a website or API and checks every HTTP request against a set of rules. OWASP describes it as a reverse proxy that protects servers rather than clients. How a WAF differs from a network firewall: “Firewall vs NGFW: what they are, how they differ”.
What a WAF protects against and what not
| Risk | Will a WAF help |
|---|---|
| Injection, XSS (A05) | Yes — this is a WAF’s main job: OWASP notes that its rules generally cover exactly these attacks |
| Known vulnerabilities in components (A03) | Partly: a “virtual patch” blocks the attack while the update is not yet installed |
| Password guessing and bots (A07) | Partly: rate limiting. But a WAF does not replace a second authentication factor |
| Access control, insecure design, failure handling (A01, A06, A10) | Hardly: a request for someone else’s account looks just like one for your own. Such flaws are fixed in the code |
| Logging (A09) | Provides attack logs — but someone has to analyse them |
So a WAF is an important layer of protection, but not a substitute for secure development and testing. OWASP also warns that customising a WAF for an application can be significant and has to be maintained every time the application changes.
A WAF protects against DDoS attacks at the application level — more in “DDoS attack: what it is and how to protect a site”.
When a WAF is required
Since 31 March 2025, the PCI DSS v4.0 standard (requirement 6.4.2) requires an automated technical solution in front of public-facing web applications that continually detects and prevents web-based attacks. It must be up to date, generate audit logs and either block attacks or raise an alert that is immediately investigated. Who the standard applies to: “PCI DSS: what it is and what it requires of IT”.
Where to start
- List your web applications: websites, portals, APIs, admin panels — everything reachable from the internet.
- Test them with a pentest. OWASP recommends at least annual penetration testing, depending on how critical the application is. How it works: “Penetration testing: what it is, types and stages”.
- Update components and scan for vulnerabilities regularly — see “Vulnerability management: where to start”.
- Put public applications behind a WAF and tune the rules for each application.
- Feed WAF and application logs into monitoring, so that alerts do not go unanswered — see “How a SOC works: tiers, processes and metrics”.
- If a contractor develops the application, reference the ASVS in the specification, not just the Top 10.
Checklist
- There is a list of web applications and APIs reachable from the internet
- Web applications are pentested regularly and after significant changes
- Third-party components are tracked and updated
- Public applications run behind a WAF with tuned rules
- Logins to admin panels and portals are protected with a second factor
- WAF and application logs feed into monitoring
- Application security requirements are written into the specification for developers
How Bereg-IT can help
We protect websites and web applications with a WAF: protection against OWASP Top 10 attack categories and their combinations, against DDoS attacks and against mass exploitation of vulnerabilities. Bereg-IT’s own team runs pentests of web applications and APIs with a report and a retest. Vulnerability management helps find vulnerable components, and SOC as a Service analyses events from web applications and the WAF.
The first consultation is free. Send a request and an information security specialist will get in touch.
Sources
- OWASP, OWASP Top 10:2025 — the categories, changes since 2021 and recommendations for an application security programme: https://top10.owasp.org/2025/
- OWASP, Web Application Firewall: https://community.owasp.org/Web_Application_Firewall
- PCI SSC, Self-Assessment Questionnaire D for Merchants, PCI DSS v4.0 (April 2022) — requirement 6.4.2: https://listings.pcisecuritystandards.org/documents/PCI-DSS-v4-0-SAQ-D-Merchant.pdf