API Abuse - Comprehension and Prevention
summary
Claims ability to cut fraudulent API traffic and costs by 90% in 30 days using an embedded SDK plus cloud DNA check that issues short-lived JWT tokens. Case study: a fast‑growing fintech (tens of thousands to 1–2 million monthly users) saw credential stuffing, automated account creation, phishing and rewards abuse; SDK integration takes seven days, checks app integrity every five minutes, leaves user traffic and latency untouched, and blocks bot-driven requests while genuine mobile traffic continues normally.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:11What is API Abuse
- 3:39Is API Abuse real
- 4:59Why would someone abuse the API
- 7:01Types of API abuse
- 9:00Mobile app abuse
- 11:11Who we are
- 12:41Reducing bad traffic
- 15:30Tools
- 16:20Case Study
- 20:11Approved API
- 21:54SDK
- 22:24Platform Support
- 22:38Backend Support
- 23:11API Abuse
- 24:17Summary
related talks
01h 01mApisecure, 14 & 15 March 2023 - Jeremy Ventura, CISO at ThreatX.
24mAPI security, mitigate API abuses using machine learning
32mApisecure, 14 & 15 March 2023 - Shannon Wilkinson, Cybersecurity Founder | Women in Technology [...]
51mThe Next Application Security Frontier: AI-Ready API Defense
50mAPI Abuse through Mobile Apps: New Attacks, New Defenses
31mAPI security
23mWhy an SDK is Needed to Protect APIs from Mobile Apps
30mAttack API Architecture