
Overview
Imperva's Managed Rules for IP Reputation allows you to take a proactive approach to security by providing an extensive IP whitelist/blacklist which is regularly monitored and updated. Imperva's reputation feed leverages crowd-sourcing from aggregated attack data to update its list with newly detected malicious sources, taking the burden off of IT teams to account for undiscovered threats.
Highlights
- Proactive approach to threat prevention and security management; Automated protection regularly monitored and updated; Integrates seamlessly with AWS WAF
Unlock automation with AI agent solutions

Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Cost/unit |
---|---|
Charge per month in each available region (pro-rated by the hour) | $40.00 |
Charge per million requests in each available region | $0.40 |
Vendor refund policy
non-refundable
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
For issues related specifically to an Imperva ruleset, you can contact Imperva support by email.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

FedRAMP
GDPR
HIPAA
ISO/IEC 27001
PCI DSS
SOC 2 Type 2
Standard contract
Customer reviews
Does not appear to be kept up to date
We recently subscribed to this rule to try and block carding botnets from hitting our website. We were attacked a few days after subscribing and applying the rule to our WAF - of the more than 250,000 requests this rule blocked 53. Of the 1400 distinct IPs hitting us, this rule blocked 1.
Its work
Best set of rules for AWS WAF. Works fine.
The main problem is the speed of updating the reputation lists. Several hours pass from the moment a bot appears until it is blacklisted
Too broad without granular controls
I really wanted to be able to use this but there doesn't appear to be any granular control, e.g the ability to include known attack IPs but exclude IPs on lists for not having reverse DNS on the IP they send mail from. In our brief examination of how the list would work (using it to count vs block) it would have been blocking clients we would have wanted to allow.
Having the ability to turn on/off specific inclusion criteria in the list, or the vendor providing various confidence level lists would allow me to possibly use this.