What is OWASP?

OWASP is the Open Worldwide Application Security Project, a nonprofit foundation that publishes free security projects: lists of risks, testing guides, cheat sheets, a verification standard and a rule set for web application firewalls. It is a community that writes documents and tools, not a regulator and not a body that certifies anyone.

Section Glossary Updated Describes an organisation

Quick facts

Full name
The Open Worldwide Application Security Project, per OWASP About
Legal form
OWASP Foundation, Inc., a U.S. 501(c)(3) nonprofit, incorporated 21 April 2004 (OWASP About)
Started
1 December 2001 (OWASP About)
Mission
To be the global open community that powers secure software through education, tools and collaboration (OWASP About)

The name changed over time. Older material says "Open Web Application Security Project"; the foundation's own About page now uses "Open Worldwide". Both refer to the same organisation.

What OWASP is

OWASP began as a single project and grew into a foundation that hosts many. Its projects are community-led and open source, and the About page says the tools, documents and resources are free for anyone to use. It also lists vendor neutrality among its values, which is why its documents name risk categories rather than products.

In practice the word is used in three ways, and mixing them up causes most of the confusion. It can mean the foundation, as in "OWASP published a new list". It can mean one project, as in "we follow OWASP" when the speaker has the Top 10 in mind. And it can mean a vocabulary: "OWASP-class attacks" is shorthand for the injection, access-control and misconfiguration problems that the lists keep naming.

The projects people mean

The foundation hosts far more projects than most readers will ever open, and its projects page is the place to see the current set. The ones that come up around web application firewalls are these.

OWASP projects that matter most to a site owner
ProjectWhat it isOn this site
Top 10A ranked list of web application risk categories; the 2025 edition is current on its project pageOWASP Top 10
API Security Top 10The same idea for APIs; the latest edition listed on its project page is 2023OWASP API Security Top 10
Cheat Sheet SeriesShort, practical security guidance for developers and defendersAPI security
ASVSA framework of security requirements for designing, developing and testing web applications and services; version 5.0.0 is current on the ASVS siteNot covered
WSTGThe Web Security Testing Guide, a manual for testing web applicationsNot covered
Core Rule SetGeneric attack-detection rules for ModSecurity or compatible web application firewallsOWASP Core Rule Set

The first two are documents about risk. The Cheat Sheet Series, ASVS and WSTG are guidance for the people who build and test applications. Only the Core Rule Set is software-adjacent in the sense that a firewall can load it. That difference is the useful thing to remember: five of the six are meant to be read, and one is meant to be run.

What OWASP is not

Several claims turn up in marketing copy that OWASP itself does not make.

  • Not a certification body. Nothing in the foundation's mission involves issuing a seal to a product or a site. "OWASP certified" is a phrase worth distrusting; "covers the OWASP Top 10 categories" is a different and more modest statement, and still needs a definition of what covering means.
  • Not a regulator. The Top 10 is an awareness document. A contract, an auditor or a standards body may point at it, but the list has no force of its own.
  • Not a product. OWASP does not sell a firewall, and a vendor that mentions it is borrowing a reference, not describing a partnership. This page makes no claim of partnership, endorsement or certification between OWASP and Bridge WAF.
  • Not a checklist that can be finished. The Top 10 groups categories of weakness. Being free of one category on a given day does not make an application secure.

Where a WAF helps and where it does not

A web application firewall reads requests before they reach the application. For several OWASP categories that view is useful: injection attempts such as SQL injection have a recognisable shape in a request, and a filter can match it. Bridge WAF works from named categories of that kind. It has no custom rules, so it cannot add a pattern for a single weakness in one application.

Plenty of what the lists describe is outside what a filter sees. Broken access control depends on who the user is and what they may open, which the request alone rarely shows. Insecure design and weak authentication are decisions made in the code. Outdated components are fixed by upgrading them, and a filter in front only delays the problem, which is the idea behind virtual patching. A WAF filters requests; it does not correct the application. The page on the OWASP Top 10 goes category by category through what can and cannot be covered.

off

Nothing is inspected. Requests reach your origin as they otherwise would.

monitor

Matches are recorded and every request is still served.

block

Matching requests are refused and still recorded.

Start in monitor. The log shows what would have been refused, and false positives surface while they cost nothing. Move to block once the recorded matches look like attacks and not like your own customers. The procedure is on the monitor mode page.

Using OWASP material sensibly

Read the list for its categories, then ask which of them your own application can exhibit. A shop with user accounts has access-control questions that a static brochure site lacks. Use the testing guide and the verification standard to check the application itself, since a firewall cannot do that for you.

When a vendor cites OWASP, ask which project and which edition. "The OWASP rules" might mean the Core Rule Set, which is a specific, versioned piece of software, or it might mean nothing more than the Top 10 used as a talking point. The Core Rule Set page explains how that rule set scores a request, and the rules section covers how filtering decisions are described on this site. For vocabulary around weaknesses, the glossary is the starting point.

Questions

What does OWASP stand for?

The Open Worldwide Application Security Project. The organisation describes itself as a nonprofit foundation, and its mission is to be the global open community that powers secure software through education, tools and collaboration.

Is OWASP a standard or a certification?

No. OWASP publishes documents, tools and guidance that anyone may use, but it does not certify products or sites. A page that says a product is OWASP certified is not describing something OWASP issues.

Is the OWASP Top 10 a law or a regulation?

No. It is an awareness document that ranks categories of web application risk. Other rules or contracts may refer to it, but the list itself carries no legal force and OWASP is not a regulator.

Is the OWASP Core Rule Set the same as OWASP?

No. The Core Rule Set (CRS) is one OWASP project, a set of generic attack-detection rules for ModSecurity and compatible firewalls. OWASP as a whole is the foundation and the community around many such projects.

Does Bridge WAF have a partnership with OWASP?

This page makes no such claim. Bridge WAF is a feature of Bridge CDN, and OWASP appears here as a reference source for the vocabulary used on this site.