Imperva API Security vs Project Shield

Imperva API Security brings API discovery, risk assessment, detection, and mitigation into one console for cloud, on-premises, and hybrid environments. It monitors public, private, and shadow APIs, tracks changes, and identifies design flaws and vulnerabilities. Ongoing assessments address risks associated with the OWASP API Security Top 10. For Broken Object Level Authorization, its machine-learning-driven detection profiles traffic for behavioral changes and can block exploits. A separate testing function scans uploaded API specifications for posture gaps, design and configuration weaknesses, and risky endpoints. Teams can choose cloud-managed or self-managed management, with agent-based or agentless deployment options for cloud WAF, microservices, encrypted applications, and network-layer monitoring. Integrations include Kong, Mulesoft, Azure APIM, Apigee, and F5. API sensitivity classification includes government IDs, card details, addresses, and other personal information. With Imperva’s application security platform, it addresses nine OWASP API Top Ten risks; Unsafe Consumption of APIs is not covered. It runs on API, self-hosted, and web platforms. Pricing is on request; there is no free plan, and a 30-day trial may be limited to 100 Mbps, with excess traffic potentially null-routed.

Project Shield has no write-up on Specifiction yet; its figures are above.