
Overview

Product video
Imperva SecureSphere WAF for AWS extends all of the security and management capabilities of the world's most-trusted web application firewall to Amazon Web Services environments. SecureSphere for AWS is the first enterprise-class Web Application Firewall tailored specifically for Amazon Web Services. Running natively in AWS, and leveraging all its capabilities, SecureSphere for AWS scales on-demand with AWS applications. SecureSphere applies multiple defenses and correlates results to offer laser-accurate attack detection. Certified by ICSA Labs, SecureSphere addresses PCI 6.6 and provides ironclad protection against the OWASP Top Ten, including SQL Injection, XSS and CSRF.
Highlights
- Automated Protection - Patented Dynamic Profiling technology streamlines management and lowers operations costs by learning application changes over time. Security updates from the Imperva ADC protect applications against the latest threats.
- Flexible Deployment Options - The SecureSphere WAF offers organizations automated, adaptable security and easy deployment into Amazon environments with full support for elastic load balancing and CloudFormation.
- Fraud and Automated Attack Protection - With advanced bot detection capabilities, IP Reputation, granular custom rules, and fraud integration, SecureSphere stops dangerous threats like site scraping, application DDoS, comment spam, and web fraud.
Unlock automation with AI agent solutions

Features and programs
Financing for AWS Marketplace purchases
Pricing
Free trial
Dimension | Cost/hour |
---|---|
c5a.2xlarge Recommended | $1.16 |
m6i.2xlarge | $1.16 |
m7i.2xlarge | $1.16 |
c5a.xlarge | $1.16 |
c4.xlarge | $1.16 |
m5.2xlarge | $1.16 |
m4.2xlarge | $1.16 |
m4.xlarge | $1.16 |
m5.xlarge | $1.16 |
m6i.4xlarge | $1.16 |
Vendor refund policy
We do not support refunds, but customers can cancel at any time. Contact Imperva for more information.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Usage instructions
AUTOMATIC DEPLOYMENT (RECOMMENDED)
Imperva simplifies the deployment of your WAF Gateway infrastructure on AWS by providing dynamically generated CloudFormation and Terraform templates tailored to your specific requirements via the Imperva Cloud Template Tool.
For detailed instructions and additional information: https://docs.imperva.com/bundle/v15.0-waf-on-amazon-aws-byol-installation-guide/page/10450.htmÂ
MANUAL DEPLOYMENT
DISCLAIMER: This procedure is not intended for use in large-scale production environments. For a best-practice installation, use the automated deployment method.
- Create a VPC, a key pair and at least one subnet.
- Create a security group for the Management Server and another security group for the Gateway instances.
- Create the following inbound rules:
- [Management Server SG] ==> [Gateway SG] @ TCP:443
- [Gateway SG] ==> [Management Server SG] @ TCP:8083, TCP:8085
- [Administrative IP ranges] ==> [Management Server SG] @ TCP:8083, TCP:22
- [Administrative IP ranges] ==> [Management Server SG] @ TCP:22
- [Administrative IP ranges] ==> [Gateway SG] @ TCP:22
- [Client ranges] ==> [Gateway SG] @ [reverse proxy ports] (variable)
- Launch your first instance using the product's AMI. For the instance's security group, select the Management Server security group you've created.
- Wait for the instance's status checks to pass and SSH into the instance as root using the supplied key pair's private key.
- Execute the First-Time login command below to configure your instance as a Management Server. This process can take up to 20 minutes.
/opt/imperva/impcli/commands/ftl --silent --product WAF --component Management --grub_password <grub_password> --database_password <database_password> --secure_password <secure_password> --system_password <system_password> --timezone <timezone> --model_type AVM150
- Replace all <variables> with your own values.
- After running the FTL, root access via SSH will be blocked by default as a security measure. To undo this, delete the contents of /etc/security/access.conf and add the following line:
+:root:ALL
- Once the First-Time Login has finished successfully, access your Management Server's user interface from a browser (https://<MX_IP>:8083).
- Accept the EULA and set the admin password as requested.
- Supply your license file or FlexProtect activation code (obtained from Imperva). Wait for the license upload to complete and verify you're able to log in as the admin user.
- To create Gateways, launch one or more instances from the same AMI, attached to the Gateway security group.
- Once the instances have passed all status checks, SSH into each instance and execute the following commands to configure it as a Gateway:
bootstrap_set //bootstrap/product/components/gateway/cloud gateway_group "aws"
/opt/imperva/impcli/commands/ftl --silent --component Gateway --model_type <AV1000 or AV2500> --management_ip <management_server_ip> --secure_password <secure_password> --system_password <system_password> --imperva_password <imperva_password> --grub_password <grub_password> --product WAF --timezone UTC --gateway_mode reverse-proxy-hades --gateway_group aws --is_advanced_bridge Disabled
- Replace all <variables> with your own values.
- For <management_ip>, supply the private IP of the Management Server instance created earlier.
- For model_type, enter either AV1000 or AV2500 based on your license's supported Gateway modules. The AV2500 model provides the highest performance.
- After successfully running the FTL on all instances, log in to your Management Server's user interface, navigate to Setup > Gateways and verify that all Gateways appear as Running under the aws Gateway group. This might take up to 5 minutes after completing the FTL.
- Refer to the user guide to configure your environment as desired and protect your applications: https://docs.imperva.com/bundle/v15.3-waf-user-guide/page/70414.htmÂ
Resources
Support
Vendor support
Imperva's team of Support Engineers is positioned across the globe to provide 24x7x365 coverage, and can be contacted by phone, email, or online via our Self Service Support Portal. Visit the Imperva Support page above for more details.
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.

Standard contract
Customer reviews
Experience swift configuration with enhanced web and mobile application security
What is our primary use case?
The solution functions just like a firewall, but it operates in the cloud. It is designed to protect web applications and environments hosted on the cloud.Â
It helps protect applications from DDoS attacks and other types of attacks. I handle a wide range of business requirements with it.
What is most valuable?
The solution can be configured in just a couple of minutes. It ensures 99.7% availability for my applications. It provides an additional layer of security for web applications and other applications, including mobile applications. It protects my environment and helps maintain my reputation in the market.
What needs improvement?
It is not a personal firewall, however, I can log my traffic to the Web Application Firewall if my hardware is available on-premise. I am satisfied with all the features available. There is nothing specific where the application firewall is falling short.
For how long have I used the solution?
I have been working with Imperva solutions personally since last month.
What do I think about the stability of the solution?
I would rate the solution ten out of ten in terms of stability.
What do I think about the scalability of the solution?
The solution is highly scalable. I can configure this firewall to expand based on my needs and revert to my basic configuration when traffic is over.
How are customer service and support?
Technical support is divided into two categories: partner side and OEM side. It is easy to contact them, and my queries are resolved efficiently.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is very easy. I just need to route the traffic, similar to configuring an IP on the application firewall. It typically takes no more than a day and is easy, rated at nine out of ten.
What's my experience with pricing, setup cost, and licensing?
The pricing is competitive in the market. The solution helps improve my security posture and operational costs.
Which other solutions did I evaluate?
There are other solutions available in the market, however, Imperva Web Application Firewall is a good solution.
What other advice do I have?
I would recommend Imperva Web Application Firewall to others.Â
Overall, I would rate it eight out of ten as it is a good solution. However, there are other solutions in the market.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Effective security breach prevention with automatic updates and customer-focused support
What is our primary use case?
We are a premier partner with Imperva. We usually recommend Imperva Web Application Firewall (WAF ) more because our customers sometimes get a better deal, and many already have Imperva solutions on-premises. We help them move to the cloud and other related tasks.
How has it helped my organization?
Customers enjoy the rules implemented in Imperva WAFÂ , which are updated automatically any time a new breach is discovered. This eliminates the need for backend changes or manual updates, making the system straightforward.
What is most valuable?
The valuable features of Imperva WAF include its effective security breach prevention through automatically updating rules. The support team answers cases quickly as well.
What needs improvement?
The product's customization capabilities are a bit problematic, requiring support cases for backend modifications.Â
Additionally, the handling of high-traffic volumes could be better, as it doesn't cut you off if you exceed your purchased traffic. Our clients like the guarantee that they won't be charged for exceeding traffic during peak periods. Users also need to be more attentive to false alerts, as the marketing might give a false sense of trust.
For how long have I used the solution?
I have been dealing with Imperva for three years, while my company has been involved for more years.
What do I think about the scalability of the solution?
Imperva WAF does not appear to handle high traffic volumes optimally during peaks as it only notifies clients if they exceed their purchased amount of traffic. However, it does not immediately cause any issue unless the excess persists over time.
How are customer service and support?
Their technical support is rated nine out of ten. Support cases are answered quickly.
How would you rate customer service and support?
Positive
How was the initial setup?
The setup is straightforward. Clients often manage it themselves, and no action is required on their end for implementation.
What about the implementation team?
On occasion, we help our clients get on the cloud as part of our partnership with Imperva.
What's my experience with pricing, setup cost, and licensing?
The pricing tends to be expensive. As premier partners, we get good deals, however, without such deals, it is usually quite costly. The cost also varies based on the plan that clients choose.
What other advice do I have?
Imperva Web Application Firewall is recommended for companies needing a robust cloud-based solution. For on-premises versions, it might be considered outdated.
I'd rate the solution nine out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Enhanced security with profile functionality
What is our primary use case?
I use the service for protection due to the fact that it has profile functionality.
What is most valuable?
Protection is the best solution since it has profile functionality.
Which other solutions did I evaluate?
Interesting alternatives are Akamai and some cloud solutions do exist.
Which deployment model are you using for this solution?
Enhance security with ease through user-friendly administration and comprehensive threat prevention
What is our primary use case?
We use Imperva for our web applications that we have hosted to protect them.
How has it helped my organization?
With our deployment setup, the benefit is regarding the security and how threats have been blocked. It's not studied in terms of resources or speed. The threat prevention is the aspect we are monitoring.
What is most valuable?
Empower administration is user-friendly, and we do not need much for managing day-to-day operations. It is easy to use and has good security. Also, it is very customizable, especially for controlling web browsers and devices.
What needs improvement?
I would prefer AI integrations for user administration, visualization, log analytics, and risk analysis. If they can bring i n generative AI features, that would be useful.
For how long have I used the solution?
I am working with Imperva at the moment and have been using it for maybe six to seven years.
What do I think about the stability of the solution?
It's very stable. We haven't had any issues.
What do I think about the scalability of the solution?
Scalability is not a problem since we have enough resources as it's an on-premises version.
How are customer service and support?
We have escalated to tech support and it's quite good. I would rate them a seven point five out of ten.
Which solution did I use previously and why did I switch?
We didn't use any WAFÂ product before Imperva.
How was the initial setup?
The initial deployment was seamless, and there weren't many complexities.
What about the implementation team?
The deployment was done by a separate company within the company.
Which other solutions did I evaluate?
I do not have much understanding about F5 yet as I am currently evaluating their solution.
What other advice do I have?
I suggest looking for a cloud-based solution rather than on-premises, which might improve availability, stability, and security.
I'd rate the solution nine out of ten.
Which deployment model are you using for this solution?
Offers bot protection and DDoS Protection and protects public-facing portals
What is our primary use case?
We are primarily a customer for Firewall. We're also moving into the managed security space, but we are primarily a customer here.Â
So, it is primarily used for web application firewalls. Protecting web applications against application-layer attacks. There is advanced bot protection and DDoS Protection.Â
What is most valuable?
It's very simple to implement. It works right out of the box once you integrate the application. It does the learning for you and starts applying relevant signatures.Â
It's effective in protecting against different kinds of attacks. For example, it can mitigate DDoS attacks and block application layer attacks like SQL injection, HTTP, and cross-site scripting attacks. The latency is pretty low.
What needs improvement?
Support is one thing I wish Imperva could improve. They follow the phone model and keep rotating you from one customer service person to another. The layer one support isn't very clear about the workings of the product.
My feedback is primarily about Imperva Cloud, not on-premise. On-premise is a whole new story.
Support is the issue for Imperva Cloud. It's also a bit pricey. It's a premium service and very expensive. The licensing model is not very straightforward. Every feature is priced separately, and to enjoy maximum protection, you'll have to spend a lot of money. The licensing model is a bit complex, and each feature is very pricey. For example, API security and web application protection are two separate license packages.
For how long have I used the solution?
For WAF, I have been using it for about four years now.Â
What do I think about the stability of the solution?
The solution is generally stable, but there are sometimes where a link degradation does not involve a failover to another port where you're able to enjoy the service. So your availability is affected because of link degradation. It will not automatically take you to another port. But otherwise, it's generally stable.
What do I think about the scalability of the solution?
The capacity and everything is managed by Imperva. We don't really get to know much about the back end.
It does a good job because we have very busy applications that seem to work well without any issues. The only issue that we experienced recently is that if there's an issue on the uplinks, the traffic does not automatically fail over to another region or another POP. You're still directed to a POP where there's degradation in service. So, if you're affected, you'll have to bear the pain until the issue is resolved before you're able to access the services again. So, there's no automatic failover between POPs from one POP to another in the event of a link degradation along the path.
How are customer service and support?
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We have tried out Radware as a POC just a couple of months ago. There is also Cloudflare .
I'd prefer Cloudflare because of its presence on the Internet, the number of services it offers, and the level of automation that it gives you.Â
I'd look up to Cloudflare because it's more stable. Because of its points of presence everywhere in the world, you're in a better place to enjoy better availability than being on Imperva.Â
And the level of protection from my test, I think it's pretty good. It's next-generation application firewall. So it's something that I look up to.
How was the initial setup?
The deployment was easy. We have quite a number of sites, more than 300. Per site, it can take about ten minutes to integrate, to move your application to the cloud, before you can achieve maximum protection or before you can achieve protection on your site. So, it's a very seamless process.
We had challenges integrating with our on-premise tools, our SIEM tools and SOAR tools. Integration is a bit complex. There's no capability to integrate with our on-premise tools, or if there is, it's very limited.
It's a SaaS service, so everything's maintained by Imperva. It's something that is managed by Imperva.Â
What was our ROI?
So, there is a return on investment in terms of achieving protection for our public-facing portals. We have seen quite a number of DDoS attacks being mitigated by Imperva. We have also seen a few web application attacks that have been blocked.
In terms of time savings, we don't have to go to the data center to do upgrades and other mundane things, so we can focus on more important things.Â
What's my experience with pricing, setup cost, and licensing?
The licensing model is a bit complex and very complicated model.Â
Which other solutions did I evaluate?
We operate a hybrid cloud and on-premise as well, and we're looking for a solution that would suit all of our needs. Right now, for API security, we don't have anything. But for others, for WAF, we do have something. We use Imperva as our WAF, for example.
We carry out research, which is the first step when we're looking to source a product. We do market research, obviously, and an assessment. So it starts with reviewing PeerSpot or what people say about different products, and then we call vendors in. They give us a demo. They give us a POC. Then, we draft the required set of requirements, and then we eventually pick a product based on what we need.
What other advice do I have?
AI functionality in Imperva does do quite a bit of learning, but Imperva can do more. There's little interaction. There's basically just the machine learning bit. So it basically baselines the application and then analyzes traffic towards the application. But in terms of capability to interact with large language models, that is still not at the level where the competitors are.
Overall, I would rate it an eight out of ten.Â