{"id":7687,"date":"2019-09-12T16:55:12","date_gmt":"2019-09-12T15:55:12","guid":{"rendered":"https:\/\/staging-site.42crunch.com\/?p=7687"},"modified":"2022-09-24T13:30:45","modified_gmt":"2022-09-24T12:30:45","slug":"api-firewall-nonblocking-mode-latest-release","status":"publish","type":"post","link":"https:\/\/staging2022.42crunch.com\/api-firewall-nonblocking-mode-latest-release\/","title":{"rendered":"New API Firewall Non-blocking Mode in Latest 42Crunch Release"},"content":{"rendered":"

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\u00a0release notes<\/a>\u00a0for additional details on full list of updates.)<\/p>\n


\nNew Feature Highlights<\/strong><\/h3>\n

\u00a0<\/strong><\/p>\n

API Firewall Non-blocking Mode
\n<\/strong>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.<\/p>\n

When configured in non-blocking mode, API Firewall\u00a0instances protecting your API execute security policies normally but\u00a0do not block\u00a0<\/em>any transactions, only report on what\u00a0would<\/em>\u00a0have been blocked. This allows users to:<\/p>\n