CAPABILITIES
What it provides
- 17 semantic engines covering SQL, XSS, commands, SSRF, injection families, and other attack patterns.
- OWASP CRS through Coraza, with sensitivity filtering and configurable clean-result suppression.
- Per-project block and log thresholds, path policies, and request-size limits.
- Decision records with matched signals and context for investigation.
DEPLOYMENT WORKFLOW
How to use it
- 01
Route application traffic through a connected WAF agent and configure its upstream.
- 02
Set sensitivity, thresholds, and relevant path policies for the application.
- 03
Observe decisions in log mode, review legitimate traffic, and enable enforcement for the validated policy.
CONFIGURATION & OPERATION
Where it fits in your setup
Configure the project’s WAF settings. Connected agents receive configuration bundles over gRPC with mutual TLS. Coraza supplies detection signals; the decision engine controls the WAF verdict.
COVERAGE & LIMITS
What to account for
Detection depends on the payload, available request data, and policy. No WAF guarantees that every attack is detected or every legitimate request is allowed. Tune with representative traffic and retain application-side validation.