About OWASP CRS
The OWASP Core Rule Set, or CRS, is a set of generic attack detection rules meant to be loaded into a web application firewall. It works with OWASP ModSecurity, OWASP Coraza and other compatible engines rather than running as a standalone application. The rules are written to protect web applications against a broad range of attacks while keeping false alerts to a minimum.
Coverage is aimed at threats such as those in the OWASP Top Ten. The project invites reports of false positives, false negatives and evasions through GitHub issues, and asks for the installed version and relevant audit log portions to help reproduce each case. Discussion takes place in a Google Group and the coreruleset channel on OWASP Slack, and the project website links to installation and configuration resources.
The ruleset is released under the Apache-2.0 license, with copyright held by Trustwave and contributors up to 2020 and by the CRS project afterward. The latest release listed is v4.29.0. Because it is a ruleset, it suits teams already operating a compatible WAF who want maintained, community-reviewed detection logic.
Key features
- Generic attack detection rules for web applications
- Compatible with ModSecurity and Coraza
- Targets the OWASP Top Ten threat categories
- Tuned to limit false positives
- Community channels for reporting evasions
Good fit for
- Adding baseline protection to a WAF
- Hardening public-facing web applications
OWASP CRS: questions and answers
- What is OWASP CRS used for?
- OWASP CRS is a collection of generic attack detection rules for ModSecurity, Coraza and other compatible web application firewalls. It is a good fit for adding baseline protection to a WAF and hardening public-facing web applications.
- Is OWASP CRS open source?
- Yes. OWASP CRS is open source under the Apache-2.0 licence. Its source code is on GitHub at coreruleset/coreruleset and is written mainly in Python.
- Is OWASP CRS free?
- Yes. OWASP CRS is open source, so the software itself is free to use.
- Can I self-host OWASP CRS?
- Yes. OWASP CRS can be self-hosted on your own server or infrastructure.
- What are some alternatives to OWASP CRS?
- Similar open-source tools in the Security category include BunkerWeb, ModSecurity and SafeLine. SaaS products in the same category include AttackerView, Socket and Veritio.
- Is OWASP CRS actively maintained?
- Yes. The most recent commit to OWASP CRS was on 12 November 2026, and the latest release is v4.30.0, published on 2 October 2026. The project has 3.4k stars on GitHub, with 54 added in the last 30 days.
Open-source alternatives to OWASP CRS
See all
BunkerWeb
Security
🛡️ Open-source and cloud-native Web Application Firewall (WAF)
AGPL-3.0vs Cloudflare★ 11k
ModSecurity
Security
ModSecurity is an open source, cross platform web application firewall (WAF) engine for Ap
Apache-2.0vs Cloudflare★ 9.9k
SafeLine
Security
CyberServal open-source WAF is a self-hosted WAF with 20.9K GitHub stars. Block SQL inject
GPL-3.0vs Cloudflare★ 23k
CrowdSec
Security
Open-source IDS/IPS, WAF and bot detection for Linux, Windows, Docker and Kubernetes, with
MITvs Cloudflare★ 16k
DefectDojo
Security
Open-Source Unified Vulnerability Management, DevSecOps & ASPM
BSD-3-Clausevs Tenable★ 5.2k
ClamAV
Security
ClamAV - Documentation is here: https://docs.clamav.net
GPL-2.0vs Avast★ 7.5k
SaaS alternatives to OWASP CRS
See all
AttackerView
Security
Security auditor that shows what an attacker can see on your website
SaaS
Socket
Security
Supply chain security that detects risky open source packages before install
SaaS
Veritio
Security
Open-source evidence layer that records app events, code changes and deployments as verifiable hash-linked audit records
SaaS
42Crunch
Security
API security platform that audits OpenAPI definitions and protects APIs at runtime
SaaS
Abnormal Security
Security
Behavior-based cloud email security that blocks phishing and account takeover
SaaS
Adverse Monitor
Security
Cyber threat intelligence tool that watches the dark web for incident claims naming your company
SaaS

