{"id":12567,"date":"2019-12-10T16:28:19","date_gmt":"2019-12-10T16:28:19","guid":{"rendered":"https:\/\/42crdev.prexihost.com\/?p=12567"},"modified":"2022-11-28T15:30:19","modified_gmt":"2022-11-28T15:30:19","slug":"webinar-positive-api-security-model","status":"publish","type":"post","link":"https:\/\/staging2022.42crunch.com\/webinar-positive-api-security-model\/","title":{"rendered":"Positive API Security Model, and Why You Need It!"},"content":{"rendered":"\r\n

Webinar<\/h4>\r\n

Many of the issues on the OWASP API Security Top 10 are triggered by the lack of input or output validation.<\/p>\r\n

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?<\/p>\r\n

What you’ll learn:<\/p>\r\n