INTEGRITY Documentation

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

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.

Plan and pricing details reflect Cloudflare’s public packaging as of 2026 and are subject to change. Confirm current terms with us before making decisions based on them.

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:

  1. Assessment. We inventory your applications, frameworks and known weak points, and review recent attack traffic if you have logs.
  2. 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.
  3. Baseline configuration. Managed rulesets are enabled in blocking mode with tuned exceptions; custom rules cover your app-specific paths (admin panels, APIs, login endpoints).
  4. Rate limiting. Login, checkout and API endpoints get rate limits calibrated from observed traffic.
  5. Tuning. Two to four weeks of false-positive review with your team, adjusting exceptions until matches are clean.
  6. 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

Custom rules

Rate limiting rules

Managed Rules

Account-level WAF configuration

Analytics

Additional tools

Reference

Troubleshooting

Glossary

Security features interoperability

Cloudflare Web Application Firewall