42c Tutorials

42Crunch API Firewall Protection Overview

In previous tutorials, we have covered static analysis with the API security audit, dynamic testing with conformance scan – now it’s time to discuss protection.

Protection Overview

The Protection function is real-time protection of live APIs. You put our API firewall in the line of traffic. It’s an extremely efficient piece of software that we ship as a docker image. It’s been written in C, is highly optimized, less than 20 megabytes in size and has a sub-millisecond overhead.

When put in the line of traffic, our API Firewall uses your secure OpenAPI definition as a whitelist and policies. Essentially, it enforces the contract on all the API calls and all the responses (data coming in, data going out). Therefore, no call with get to your code if it’s outside of your contract, and no response will get sent back if it’s not expected.

To enable Protection, first click on Protect API.

Generating a Token

Next step is to generate a token. (1) Click on Protection Tokens > (2) Create Token > (3) Enter a name > (4) Click Generate Token. (screen shot of naming)


 You then copy the token. Once you copy the token and close out the window there is no way to get the token for security reasons.


API Firewall Deployment Guides

You will then need to configure your network to pass all the API calls and responses through the 42Crunch API Firewall. Click on Deploy Your APIs to follow the proper documentation related to your current deployment.

To see the 42Crunch API Firewall in action, you can watch the demo below.

In our next tutorial we'll give you a quick overview of the protection dashboard reports, troubleshooting issues and settings.