Englishالعربية Soon
Under attack?
WAF · Web application and API firewall

Your application has a vulnerability today. The patch lands next quarter.

A web application firewall defends applications and APIs against exploitation without touching the application code. Attacks are blocked at the edge while your developers work through the fix on their own schedule.

Beyond signatures

Blocking the attacks nobody has written a rule for yet.

Application and user profiling learn how the application is normally used, so requests that deviate can be blocked before a detection rule exists. Correlation links related events over time instead of judging each request alone.

Bots, users and uptime

Application layer attacks are a business continuity problem.

Automated abuse, credential stuffing, application layer denial of service and attacks aimed at your users are handled at the edge, so the application stays available and the data stays where it belongs.

Capabilities

What the platform gives you

Requirements we hold any application firewall to, on premises or as a subscription.

Known attack classes

The common web attack classes, including everything in the widely used top ten lists, blocked with rules maintained against current exploitation techniques.

Behavioural profiling

The application and its users are profiled, so anomalous requests can be blocked before a signature exists for them.

API protection

Requests against APIs are validated against expected structure and behaviour, not just filtered as generic web traffic.

Bot management

Automated traffic is separated from human traffic, including clients that execute scripts to look like a browser.

Application layer denial of service

Traffic patterns aimed at exhausting the application rather than the link are identified and throttled.

Client side protection

A client module defends users against script injection and request forgery attacks that execute in their browser.

Virtual patching

A known vulnerability can be shielded with a targeted rule, which buys the development team time to fix the code properly.

File upload inspection

Uploaded and downloaded files are scanned with multiple engines before they reach users or storage.

Correlation and custom rules

Related events across sessions are linked, and your own logic can be expressed as rules for the behaviour specific to your application.

Deployment

Three ways to put it in front of an application

The right mode depends on whether you need to see attacks or stop them, and how much you are willing to change the traffic path.

01
Sniffer
A copy of traffic is analysed from a mirror port. Detection only, no change to the traffic path.
02
Reverse proxy
Traffic terminates at the firewall, is decrypted and inspected, and attacks are blocked. The usual choice.
03
Transparent proxy
The firewall bridges the existing path between client and server, blocking inline with minimal reconfiguration.
Most estates start in detection mode to tune out false positives against real traffic, then move to blocking once the policy is proven.
Why it matters

A vulnerability has a lifespan, and it is longer than you think

A flaw exists from the moment the code ships. It is discovered later, disclosed later still, and patched when the release calendar allows. The firewall covers the gap between disclosure and deployment, which is the window attackers actually use.

01
Assess
Applications inventoried, traffic volumes measured and protection mode agreed per application.
02
Deploy
Firewall installed in the chosen mode, certificates and policy templates configured, traffic flowing.
03
Tune
Policies run in detection mode against real traffic, false positives eliminated and exceptions recorded.
04
Enforce
Blocking enabled per application, with rollback defined before anything is switched on.
05
Operate
Rules maintained, new applications onboarded and alerts monitored by your team or by ours.
Delivery model

You own it, we build it

Deployed on your premises under your licences, tuned against your traffic, with your team holding the policy.

Learn more →

Delivery model

We run it as a subscription

Hosted protection with monthly commercial terms, configured and operated by us, with no hardware to buy.

Managed SOC →

Related

Controls that work alongside it

Source code review

Fix the vulnerability in code while the firewall holds the line.

Application assessment

Test the application the way an attacker would, before someone else does.

SIEM

Firewall events correlated with the rest of the estate rather than read in isolation.

Put it in front of one application first.

A pilot on a single application shows you the traffic you are already receiving, in detection mode, before anything is blocked.