Field CTO and Co-founder
Many of the issues on the OWASP API Security Top 10 are triggered by the lack of input or
To protect APIs from such issues, an API-native, positive security approach is required: we create an allowlist of the characteristics of allowed requests. These characteristics are used to validate input and output data for things like data type, min or max length, permitted characters, or valid values ranges. But how do we fill the gap between security and development mentioned above?
What you’ll learn:
- Why WAFs fail in protecting APIs
- How an allowlist protects against A3, A6 and A8 of the OWASP API Security Top 10 – (with real-life examples)
- How to build a proper allowlist for API security
Hope you enjoyed the webinar! Below you can download the slide deck, visit our blog
for full Q&A and learn more about 42Crunch!
Free Tools: Check out our free API Security Tools that you can add to your IDE and CI/CD!
Want to learn more? Here are some resources to help you out.
Looking to make OpenAPI / Swagger editing easier? Or want to see how secure your API is? Check out our free tools.Get the Tools!
API Security Top 10
Learn more about the OWASP API Security Top 10, how 42Crunch can help, and download our cheat sheet!Learn More