Web Application Firewall (WAF)
The Cloudflare Web Application Firewall inspects every HTTP request at the edge and blocks exploit attempts — from SQL injection to zero-day CVEs — before they reach your servers.
Overview
Web applications are attacked constantly and automatically: scanners probe for known CVEs, injection flaws, exposed admin panels and leaked credentials within minutes of a vulnerability becoming public. A web application firewall (WAF) filters this traffic in front of the application, buying your team time to patch and stopping the majority of opportunistic exploitation outright.
Cloudflare's WAF runs in every one of its 300+ locations, so filtering happens close to the client with negligible added latency. Rules are maintained by Cloudflare's security research team and updated continuously — often within hours of a major CVE disclosure — without you redeploying anything.
Key capabilities
- Cloudflare Managed Ruleset covering current exploit techniques and high-profile CVEs, updated continuously
- OWASP Core Ruleset with adjustable paranoia level and scoring threshold
- Custom rules built from any request attribute — path, headers, country, ASN, bot score, JA4 fingerprint and more
- Rate limiting rules to throttle brute force, credential stuffing, scraping and API abuse
- Leaked-credentials detection that flags logins using username/password pairs found in public breaches
- Uploaded-content scanning and sensitive-data detection for responses (Enterprise add-ons)
- Attack-score machine learning that rates every request's likelihood of being malicious (Business/Enterprise)
- Full analytics with per-rule matching, and a log-only mode for risk-free rollout
How it works
Every request to your domain terminates at a Cloudflare edge server, where it is evaluated against your WAF configuration in phases: custom rules, rate limiting rules and managed rulesets. Rules are written in Cloudflare's wirefilter expression language and compile to efficient filters, so evaluation adds well under a millisecond in typical configurations.
The managed rulesets are signature- and heuristic-based protections curated by Cloudflare's security team; the OWASP ruleset works differently, scoring each request against dozens of generic attack patterns and blocking when the cumulative score crosses your chosen threshold. On top of this, Cloudflare's ML-based attack score generalises from known payloads, which lets custom rules catch obfuscated variants and previously unseen exploit attempts.
Actions are granular: a rule can block, challenge (interactive or managed), log, or skip other rules — so you can deploy new protections in log-only mode, review matches in analytics, then switch to blocking with confidence.
Plans & licensing
All plans include custom rules and rate limiting in some quantity. The Free plan ships a slim managed ruleset for critical vulnerabilities; Pro adds the full Cloudflare Managed Ruleset and OWASP Core Ruleset; Business raises rule quotas and adds attack-score-based rules; Enterprise adds advanced rate limiting, payload logging, sensitive-data detection and the highest quotas. Details are accurate as of 2026 and subject to change — confirm current packaging with us.
Deployment with Integrity
As a certified Cloudflare partner for Central and Eastern Europe, Integrity delivers this product end to end — including a free pilot so you see results on your own traffic before committing. A typical rollout:
- Assessment. We inventory your applications, frameworks and known weak points, and review recent attack traffic if you have logs.
- Free pilot. A proof-of-concept zone goes live with managed rulesets in log-only mode, so we can measure real matches with zero user impact.
- Baseline configuration. Managed rulesets are enabled in blocking mode with tuned exceptions; custom rules cover your app-specific paths (admin panels, APIs, login endpoints).
- Rate limiting. Login, checkout and API endpoints get rate limits calibrated from observed traffic.
- Tuning. Two to four weeks of false-positive review with your team, adjusting exceptions until matches are clean.
- Handover or managed WAF. Documentation and training for your team, or ongoing rule management by Integrity — including emergency virtual patching when major CVEs drop.
Ready to start? Contact us to arrange the free pilot.
FAQ
Will the WAF break our application or block real customers?
Deployed carelessly, any WAF can. That is why we start in log-only mode, review every match against real traffic, and add scoped exceptions before enforcing. After tuning, false positives are rare and quickly diagnosable in analytics.
We already patch quickly. Do we still need a WAF?
Yes — patching and filtering are complementary. Exploitation of new CVEs now begins within hours of disclosure, faster than most change windows. A WAF with managed rules acts as virtual patching for the gap, and also stops the generic injection and abuse traffic that never gets a CVE number.
Can we protect APIs, not just websites?
Yes. WAF rules apply equally to API traffic, and rate limiting plus schema-aware protections (API Shield on Enterprise) are designed specifically for JSON APIs, mobile backends and machine-to-machine endpoints.
Further reading
Full WAF documentation
The complete Cloudflare WAF documentation, mirrored and maintained by Integrity (reviewed monthly). Based on the Cloudflare Developer Docs, CC BY 4.0.
Concepts
Get started
Traffic detections
- Overview
- AI Security for Apps
- Example mitigation rules
- AI Security for Apps fields
- Get started with AI Security for Apps
- Log mode versus production mode
- PII detection
- Prompt injection detection
- Token counting
- Unsafe and custom topic detection
- Application Profiles
- Analyze profile detections
- Enforce profiles with Custom Rules
- Fields
- Get started
- Schema Profiles
- WAF attack score
- Leaked credentials detection
- Common API calls
- Example mitigation rules
- Get started
- Terraform configuration examples
- Malicious uploads detection
- Common API calls
- Example rules
- Get started
- Terraform configuration examples
- Threat intelligence
- Example rules
- Threat intelligence fields
- Get started
Custom rules
- Overview
- Create a custom rule via API
- Create a custom rule in the dashboard
- Custom rulesets (zone level)
- Configure a rule with the Skip action
- API examples
- Available skip options
- Common use cases
- Allow traffic from IP addresses in allowlist only
- Allow traffic from specific countries only
- Allow traffic from search engine bots
- Block requests by attack score
- Block traffic by geographical location
- Block Microsoft Exchange Autodiscover requests
- Block traffic from specific countries
- Challenge bad bots
- Issue challenge for admin user in JWT claim based on attack score
- Configure token authentication
- Exempt partners from Hotlink Protection
- Require a specific cookie
- Require specific HTTP headers
- Require specific HTTP ports
- Build a sequence rule within custom rules
- Require known IP addresses in site admin area
- Stop R-U-Dead-Yet? (R.U.D.Y.) attacks
- Update custom rules for customers or partners
Rate limiting rules
- Overview
- Rate limiting best practices
- Create a rate limiting rule via API
- Create a rate limiting rule in the dashboard
- Find appropriate rate limit
- Rate limiting parameters
- Request rate calculation
- Troubleshoot rate limiting rules
- Rate limiting rule examples
Managed Rules
- Overview
- Check for exposed credentials
- Configure exposed credentials checks via API
- Configure exposed credentials checks using Terraform
- How exposed credentials checks work
- Monitor exposed credentials events
- Test your exposed credentials checks configuration
- Upgrade to leaked credentials detection
- Deploy a WAF managed ruleset via API (zone)
- Deploy a WAF managed ruleset in the dashboard
- Log the payload of matched rules
- Command-line operations
- Decrypt the payload content
- Generate a key pair
- Configure payload logging in the dashboard
- Configure payload logging via API
- Store decrypted matched payloads in logs
- View the payload content in the dashboard
- Rulesets reference
- Cloudflare Managed Ruleset
- Cloudflare Exposed Credentials Check Managed Ruleset
- Cloudflare OWASP Core Ruleset
- Concepts
- Configure via API
- Configure in the dashboard
- OWASP evaluation example
- Cloudflare Sensitive Data Detection
- Troubleshoot managed rules
- Create exceptions
- Add an exception via API
- Add an exception in the dashboard
Account-level WAF configuration
- Overview
- Custom rulesets (account level)
- Create a custom ruleset using the API
- Work with custom rulesets in the dashboard
- Managed rulesets
- Deploy a WAF managed ruleset via API (account)
- Deploy a WAF managed ruleset in the dashboard (account)
- Rate limiting rulesets
- Create a rate limiting ruleset via API
- Create a rate limiting ruleset in the dashboard
Analytics
Additional tools
- Overview
- Browser Integrity Check
- IP Access rules
- IP Access rules actions
- Create an IP access rule
- IP Access rules parameters
- Lists
- Create a list in the dashboard
- Custom lists
- Lists API
- Lists API endpoints
- List JSON object
- Managed Lists
- Use lists in expressions
- Privacy Pass
- Replace insecure JS libraries
- Scrape Shield
- Email Address Obfuscation
- Hotlink Protection
- Security Level
- User Agent Blocking
- Validation checks
- Zone Lockdown
Reference
- Overview
- Alerts for security events
- Legacy features
- Firewall rules upgrade
- Rate Limiting (previous version)
- Troubleshoot Rate Limiting (previous version)
- Rate limiting (previous version) upgrade
- WAF managed rules (previous version)
- Troubleshoot WAF managed rules (previous version)
- WAF managed rules upgrade
- WAF phases
Troubleshooting
- Overview
- Bing's Site Scan blocked by a managed rule
- Issues sharing to Facebook
- Fake bot detection blocking legitimate requests
- FAQ
- Rule phase interactions
- SameSite cookie interaction with Cloudflare