Apisecure, 14 & 15 March 2023 - Christine Bevilacqua, Head Of Marketing at APIsec.
summary
Argues that API security moves left by auto-generating tests at the gateway, analyzing definitions and creating thousands of API-specific attack playbooks in seconds to minutes, then assigning risk scores and auto-opening Jira tickets for critical flaws; cites deployments across hundreds to thousands of APIs (financial, telecom, healthcare) that gate builds and expand coverage after initial success; recommends integrating Postman, GitHub, Kong/MuleSoft and CI/CD so that every build is tested in CI/CD and notes 40,000+ signups for the free pen‑testing course.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:26Shift left security for APIs
- 9:15Three pillars of API security
- 15:45Governance for secure APIs
- 16:06Testing APIs before production
- 24:37Bridging Dev and Security
- 34:11API security success stories
- 47:00Best practices for shift left
- 51:01Q&A
related talks
24mAPI Security in DevSecOps: Built-In, Not Bolted On
31mAPI security
16mDo the Right thing, shift Left!
42mAPI Security: Code-to-Cloud Context for Complete Protection
33mWhy Developers Struggle with API Security
55mAPI Security Assurance via E2E Testing
41mTest Smarter Security Essentials for Quality Engineers
26mOffensive API Penetration Testing