Six layers of defense,
enforced at the edge node.
Six layers: access lists, CC, bots, WAF, upload scanning and auto-ban. With Rules Update, virtual patches for exploited vulnerabilities (CISA KEV baseline), emergency rules and the high-risk IP library sync hourly, with no version upgrade.
Filtered layer by layer,
every block on record.
The blocks of each layer are counted separately under Protection results on the security posture screen
- IP and range allow/block lists, global or per site
- Allow or block by country, province or carrier
- Conditions on UA, Referer, request method and JA4 TLS fingerprint
- Rate limits by IP, URL or JA4 TLS fingerprint; challenge or block when exceeded
- JS and slider challenges
- Thresholds per site and per path
- Detects scanners such as nuclei, masscan and zgrab
- Detects spoofed UAs and headless browsers; JA4 fingerprints counter automation that rotates IPs
- Search-engine crawlers are allowed automatically
- Based on OWASP CRS v4, covering SQL injection, XSS, command injection, path traversal, Log4j and more
- Three protection levels, adjustable per site
- New rules only log for 3 days before blocking, to cut false positives
- Dangerous file types are blocked directly
- Trojan / webshell signatures (Plus)
- ClamAV virus library on nodes with ≥ 4 GB RAM (Plus)
- Repeat offenders are banned automatically and released on expiry
- High-risk IP library updated hourly (Rules Update)
- Banned IPs are stopped at the node when they return
Illustration · select a layer for its key pointsDemo
Three protection levels
One default level for all sites, which can be overridden per site
Put the attack picture
on the duty-room screen.
Available with WAF Plus, with full-screen display and automatic refresh. Without it, Security Overview and Attack Logs remain available.

Attack map
Source countries and cities and the targeted edge node; bar height indicates the number of attacks
Live attacks
Refreshed every 5 seconds: time, source IP, target, matched rule, action
Protection results
Blocked requests and origin traffic saved, by protection feature (CC, WAF, auto-ban, region blocking and others)
Protection score
Scored from protection switches and rule sync status; each deduction links directly to the setting to correct
Every block
traces back to the request itself.
Filter by time, IP, site, attack type or matched rule; see the request and where it matched; a source can be banned or allowlisted in one click.


- Events are kept for 7 days; bans lift automatically on expiry
- Attacks from the same IP are grouped together
- A false positive can be excepted in one click, without editing rules
No version upgrade,
and the rules still update.
Virtual patches for exploited-in-the-wild vulnerabilities are tracked against the CISA KEV catalog and pushed hourly to every edge node, with no version upgrade.
Used when no rule pack is available
OWASP CRS v4 conversions + virtual patches for exploited vulnerabilities + emergency rules
Known malicious sources, blocked at the node on a match
20 checks,
to surface the risks you may have missed.
20 checks per site produce a protection score and actionable fixes; results are linked to Security Overview.

Scope
- TLS configuration and certificate status
- Security response headers
- Origin exposure and known-vulnerability probing
Protection baseline
- Baseline by site type (6 types, chosen manually or detected from the last 7 days of traffic)
- Checks WAF level, action, upload scanning and bot handling
- Lists only what a fix would actually change
Remediation and traceability
- One-click fixes and bulk fixes across sites
- Fix batches can be undone within 7 days
- Probes in the last 7 days link to the matching attack logs
Basic protection for everyone,
enhanced capabilities when you need them.
Basic protection is included in every plan; WAF Plus is included by plan or available separately. Rules Update is priced separately; see the cards below
| Basic protection vs WAF Plus | Basic (every plan) | WAF Plus |
|---|---|---|
| Built-in rules for SQL injection, XSS, command injection, path traversal, Log4j and more | Included | Included |
| CC protection, access control, auto-ban | Included | Included |
| Security Overview, Attack Logs | Included | Included |
| Standard / Strict protection levels | Not included | Included |
| Semantic detection (parses syntax, not just keywords) | Not included | Included |
| Advanced bot detection and behavior scoring | Not included | Included |
| Replay protection / page tamper protection / sensitive-data leak prevention | Not included | Included |
| Upload scanning: trojan signatures + virus library | Not included | Included |
| Security posture screen | Not included | Included |
- Deeper detection, fewer false positives
- Standard / Strict protection levels
- Semantic detection (SQL / HTML / JS parsing)
- Advanced bot detection and behavior scoring
How are legitimate visitors protected from false blocks?
New rules only log, without blocking, for their first 3 days. A false positive can be excepted in one click from Attack Logs, for that site and that rule only.
How do the basic rules differ from Rules Update?
Basic rules come with each release upgrade. With Rules Update, CRS converted rules, virtual patches for exploited vulnerabilities (CISA KEV baseline), emergency rules and the high-risk IP library sync hourly to every edge node, with no version upgrade.
How soon after disclosure is a new vulnerability covered?
Vulnerabilities in the CISA KEV catalog that are detectable at the HTTP request layer are covered by virtual patches in Rules Update (flaws invisible at that layer, such as OS kernel bugs, need system patches), which controllers with the add-on sync every hour; others get coverage with the next release.
Is DDoS protection supported?
Application-layer (CC) attacks are covered. High-volume network-layer attacks depend on the protection capability of your data center and network.