Imperva Advanced Bot Protection: the Distil lineage, and where it fits now

Imperva Advanced Bot Protection carries the Distil Networks lineage, one of the older detection stacks in this market. It usually turns up in an evaluation because it is already in a WAF contract rather than because somebody went looking for it.

What it is

The bot mitigation product Imperva built from its 2019 acquisition of Distil Networks, sold alongside Imperva's WAF, API security and DDoS products. Imperva is now part of Thales.

Where it leads

Coverage breadth inside a single security vendor. If your web application firewall, API security and DDoS protection already come from Imperva, adding the bot module keeps the estate consolidated and the procurement simple. For security organisations that value vendor consolidation over best-of-breed, that is the argument and it is a reasonable one.

How it compares to the Forrester-evaluated vendors

Imperva was not evaluated in Forrester's Q2 2026 Bot and Agent Trust Management Wave. As with Akamai and Cloudflare, we would not treat that as a verdict on the product. It does mean you have no current independent read on how the agent trust side is developing, the fastest-moving part of this category.

The questions worth putting to Imperva are the same ones worth putting to every vendor here: what does the customer see when a legitimate request is blocked, who writes the rule when the defaults miss, and can your analysts query the raw events.

What it costs

Quoted, typically bundled. Same problem as Akamai: the marginal cost of the bot module is hard to isolate, so you have a weaker bargaining position at renewal than you would with a standalone contract.

Where data is processed

Imperva's global network, with regional options set by the wider Imperva contract rather than by the bot module alone. Imperva is now part of Thales, a French group, though that does not by itself determine where your traffic is processed. Prosopo Protect can confine processing to the EU. On the Custom plan, customers can also be given a database of their own, with no other site's visitors in it.

How a block gets explained

Through Imperva's console and log export. Test during a trial whether the reason attached to a specific block is specific enough for a support agent to act on without escalating.

Who authors the rules

Customer configuration inside Imperva's policy model.

Which buyers Imperva suits

It is the stronger fit if you are already an Imperva WAF customer and consolidation matters more to you than depth, or if the bot pressure is commodity scraping the module already handles.

How Prosopo compares

If the traffic getting through is solver-service or real-device-farm driven, where client-side behavioural signals are what break the disguise.

If you need a readable reason when explaining a block to a customer, a CFO or a data protection officer.

If you want a standalone contract with published pricing you can model, rather than a module inside a bundle.

Side by side

See the Forrester Wave breakdown for the vendors that were evaluated.