September 12, 2019
The 42Crunch August 2019 release introduces a new API firewall non-blocking mode so you can test how it affects your existing API traffic without impacting consumers, a deeper integration between the security audit and editor for seamless navigation, and an enhanced audit issue view for faster editing. (See the release notes for additional details on full list of updates.)
API Firewall Non-blocking Mode
42Crunch leverages the API contract to enforce security using our micro API firewall. The runtime is fully optimized to be deployed and run in Kubernetes environment and can protect North-South and East-West microservices traffic. With minimal latency and footprint, it can be deployed against hundreds of API endpoints with minimal impact.
When configured in non-blocking mode, API Firewall instances protecting your API execute security policies normally but do not block any transactions, only report on what would have been blocked. This allows users to:
Dashboards are populated normally, so you can easily see what would have happened.
Integrated Security Audit report and Security Editor
The security editor has now a tighter integration with the audit report viewer. Users can:
Improved Audit Issue View
Viewing the issues that Security Audit discovered has been improved in both the audit report and Security Editor: that enhances the capacity to view, navigate and fix issues uncovered by the Audit – helping developers to quickly edit their contracts.
Try our security audit for free. If you want to see the whole platform in action, request a demo now!
For news on all things API – visit APIsecurity.io and sign up for the weekly newsletter.
Point the 42Crunch MCP scan at any MCP server and receive a scored report against the OWASP MCP Top 10 and your regulatory frameworks in under 60 seconds. No agent, no deployment, no commitment required.