AWS WAF vs Imperva Data Security

• AWS WAF has the most developer-friendly API to create firewall rules.
• AWS WAF provides OWASP security controls, which reduces developers' burden (i.e., SQL injection and cross-site scripting).
• AWS WAF has customizable web security rules. The user can even push the rules through the API available, which is the great feature and helped me a lot.
• It protects applications at layer 7 (HTTP) of the OSI model and not just layer 4 (TCP).

Read full review

• Alerts when suspicious activity is detected
• Records all database transactions for analysis
• Determines activities in stored procedures

Read full review

• The documentation offered is somewhat confusing, so it would be ideal if it were much more direct and precise.
• Your initial configuration may be confusing, so the best option is to use the rule templates provided by AWS.
• Its configuration is not unified with AWS, so it must be done separately and it takes some time.
• The number of rules to be established is somewhat limited.

Read full review

• Alerts require a lot of tuning to get actionable intelligence
• Certain common encryption ciphers are incompatible with Imperva and have to be disabled at the server level
• Technical support is sometimes a little hard to work with

Read full review

• The overall security of the web application increased effectively after deploying AWS WAF
• No negative impacts were seen in the business
• The developers were more confident in the overall security model of the web application being developed and it was easy to integrate WAF into the existing system as the application was also using AWS platform

Read full review

• Allowed us to meet important compliance requirements.
• When protecting critical data, we can see exactly how it's being used and by whom.
• Licensing costs are very reasonable.
• It takes a fair amount of administration to use properly.

Read full review