Skip to content

Intelligence

Threat intelligence that acts at the edge

ArxLayer turns signals seen across the fleet into reputation and rule updates that shape edge decisions in real time. New attack patterns get managed rule updates and virtual patches that roll out everywhere, not a ticket in your backlog.

SignalsApplied toArxLayerThreatIntelcross-fleetFleet signalsReputationEmerging threatsEdge decisionsVirtual patchesWatchlists

The problem

An attack seen once should protect everyone

Threats move fast. A signal that one surface learns the hard way is wasted if it stays trapped on one box.

Isolated signals don't add up

When each edge only knows what it has seen locally, a probing client gets a fresh start on every surface it touches.

New CVEs outrun your deploys

A freshly disclosed vulnerability is exploited within hours, long before most teams can patch and ship a fix.

Raw feeds aren't decisions

A list of bad IPs or indicators is noise until something turns it into a precise, reversible enforcement action.

What you get

Shared signal, enforced safely

Intelligence is gathered across the fleet, scored, and delivered to the edge as reputation and managed rules you can reason about and roll back.

Cross-fleet reputation

Signals seen across protected surfaces build a shared reputation view that informs allow, challenge, and block decisions at the edge.

Privacy-preserving by design

Client IPs are hashed with HMAC for reputation. Raw IPs never leave the edge, so shared signal does not mean shared identity.

Managed rule updates

OWASP Core Rule Set coverage on the Coraza engine is kept current, so new attack classes are covered without you tracking every rule.

Fleet-wide virtual patching

When a new vulnerability surfaces, a virtual patch can block the exploit pattern at the edge across every domain at once.

Simulate before you enforce

Run new intelligence in detect mode on live traffic, review what it would block, then switch on enforcement.

Versioned and reversible

Every intelligence-driven change is a policy version you can review and roll back in seconds if it ever misfires.

How it works

From signal to enforcement

Collect signal across the fleet, turn it into reputation and rules, and roll it out reversibly.

Observe across the fleet

Edges emit privacy-safe signals on attacks and failed challenges, keyed by hashed IP so no raw address is shared.

Score and package

The control plane aggregates signals into reputation and bundles emerging-threat coverage as managed rules and virtual patches.

Roll out at the edge

Updates propagate through event-driven config rollout, applied locally and in memory on the request path, reversible at any time.

FAQ

Questions, answered

Where does the intelligence come from?
From signals observed across the ArxLayer fleet, combined with the maintained OWASP Core Rule Set baseline. It is delivered as reputation and managed rule updates, not raw indicator dumps.
Does sharing reputation expose my visitors' IP addresses?
No. Client IPs are hashed with HMAC for reputation and raw IPs never leave the edge, so the shared view carries signal without identity.
What is virtual patching?
A managed rule that blocks an exploit pattern at the edge, giving you protection against a new vulnerability before you can patch and redeploy the origin.
Can I review intelligence changes before they block traffic?
Yes. Run new intelligence in simulate mode, review the would-block events on your real traffic, then enforce, and roll back any change instantly.

Put fleet-wide intelligence to work

Turn signals seen across every protected surface into reputation and rules that defend yours, reversible at any time.