API security, mitigate API abuses using machine learning
summary
Many organizations miss APIs: a survey finds 51% of orgs unsure which APIs they expose, leading to leaks like the Landmark White property-data exposure and token abuse like the USPS case. Concrete blind spots include SOAP-to-REST bypasses that ignore new auth rules, a Kubernetes API JSON-patch DoS, negative-quantity e‑commerce fields, and hundreds of thousands of secrets on GitHub. Mitigation builds a model from real traffic so PingIntelligence for APIs spots anomalous outside-the-app use and cuts detection from months to minutes.
AI-written summary · about
chapters (8)
- 0:00API security blind spots
- 1:08API layer security importance
- 3:59API security blind spot examples
- 12:31Gaps in API security foundations
- 15:46Mitigating risks with ML
- 19:21ML benefits for API security
- 20:29Hacker deception solutions
- 22:19Q&A on false positives
related talks
31mAPI security
19mAvoid These API Security Pitfalls: Expert Insights
31mStandard Classification: API Security Top 10 - A Beginner's Guide to Mitigation
24mSecuring the Modern API Ecosystem
26mAPI and Application Security - The Future
25mThe New API Vulnerability Frontier
01h 29mAPI Vulnerabilities and What to Do About Them
31mWhy securing models without securing APIs creates a false sense of control