API Security Deep Dive: Safeguard Your Digital Assets
summary
Enterprise modernization at scale creates API sprawl across 7,000+ apps, so first step is inventory and automated periodic checks that let owners sign off or deprecate endpoints. Practical fixes: enforce TLS 1.3 and zero trust, apply rate limits (author cites a 2.3 Tbps DDoS example), block GraphQL introspection and depth to avoid queries that can return 6 million objects after four levels, prefer opaque tokens for immediate revocation, layer gateways, monitor and run professional pen tests.
AI-written summary · about
chapters (18)
- 0:00Start
- 0:39Intro
- 1:20API Basics Explained
- 5:38AT&T API Modernization
- 8:22API Capabilities Overview
- 9:45API Inventory Management
- 10:18API Standardization Techniques
- 11:30Introduction to GraphQL
- 14:09API Monitoring Strategies
- 14:47API User Rate Limiting
- 15:27Understanding CORS in APIs
- 16:53OWASP Security for APIs
- 18:18JWT vs PEG Token Comparison
- 19:27API Payload Challenges
- 20:25Advanced API Monitoring
- 20:48Using API Gateways
- 21:43API Security Tools
- 22:40Future Trends in API Technology
related talks
24mAPI Security in DevSecOps: Built-In, Not Bolted On
14mAPI sprawl & open API: Potential risks of application modernization
48mAPI Security for Enterprises fireside chat
18mAPI Security Simplified: A 5-Pillar Approach
24mSecuring the Modern API Ecosystem
31mAPI security
08mAPI Security Risks
19mAvoid These API Security Pitfalls: Expert Insights