Skip to content

Protect

A web application firewall that's safe to turn on

ArxLayer WAF inspects every request with the OWASP Core Rule Set on the Coraza engine and blocks attacks at the edge, before they reach your origin. Start in detect mode, see exactly what would block, then enforce with confidence.

Incoming requestsProtectedArxLayerWAFengineOWASP CRSSQL injectionXSSPath traversalRCE attemptValid requestWeb appAPIsBlockedAllowed

The problem

Web attacks don't wait for your next deploy

Injection, cross-site scripting, and path traversal target every app the moment it's exposed. A WAF has to catch them without breaking real traffic, and without becoming a black box you can't reason about.

Injection & payload attacks

SQLi, command injection, and malicious payloads hide in query strings, headers, and bodies.

XSS & path traversal

Cross-site scripting and traversal probe every input your application accepts.

False positives break trust

A WAF that blocks real users is a WAF teams turn off. Safe tuning is the hard part.

What you get

OWASP CRS protection you can reason about

Detection runs on the open OWASP Core Rule Set on the Coraza engine, a transparent, community-vetted baseline, not a proprietary black box.

OWASP Core Rule Set

Industry-standard detection for the OWASP Top 10, on the Coraza engine.

Anomaly scoring & paranoia levels

Tune sensitivity per app so blocking is deliberate, not all-or-nothing.

Detect, tune, block

Run in detection on live traffic, review would-block events, then enforce.

One-click false-positive fixes

Clear a false positive with a scoped exclusion, no rule-writing required.

Versioned, reversible policy

Every change is a new version you can review and roll back in seconds.

No keys in enforcement

The WAF stores no private keys, a cleaner security boundary.

How it works

Protected in three steps

Connect, tune safely, and switch on blocking when you're ready, no lengthy rollout.

Point your domain

Route traffic through ArxLayer Edge. A balanced managed policy protects you from the start.

Watch in detect mode

See exactly what would block on your real traffic, with evidence behind each detection.

Switch on enforcement

Turn on blocking with confidence, and roll back any change instantly.

FAQ

Questions, answered

Which rule set does ArxLayer WAF use?
The OWASP Core Rule Set (CRS) on the Coraza engine, an open, community-vetted baseline you can tune with anomaly scoring and paranoia levels.
Will it block my real users?
Not if you use the detect to block path. Run in detect mode first, review what would block, apply scoped exclusions for false positives, then enforce.
Does the WAF store my TLS private keys?
No. The enforcement layer holds no private keys; certificate lifecycle and key custody live behind separate boundaries.

Turn on a WAF you can trust

Start in detect mode and see exactly what ArxLayer would block, then enforce when you're ready.