Follow the Trace: How Traditional AppSec Tools Have Failed Us
summary
Runtime tracing shows actual attack paths by instrumenting a vulnerable Flask app with flame graphs, reproducing an SSRF that reaches an internal service, and then demonstrating the same payload is stopped when a RASP agent is active. The talk claims runtime context cuts false positives and lets teams reprioritize — DataDog analysis finds only 18% of critical vulns require urgent action — and it notes deployment tradeoffs: agents, tuning, monitoring-first versus immediate blocking.
AI-written summary · about
chapters (14)
- 0:00Introduction to talk
- 1:49What is a trace
- 6:49Traditional AppSec tools
- 9:14Interactive AppSec testing
- 11:00WAF vs RASP
- 13:32Why runtime security
- 15:20Vulnerable app demo
- 16:01SSRF attack explained
- 19:13How RASP works
- 21:46Blocking SSRF with RASP
- 22:51Security insights from runtime
- 24:15Challenges of runtime tools
- 25:41Recap and key takeaways
- 27:27Q&A session
related talks
48mMonitoring Application Attack Surface and Integrating Security into DevOps
49mLessons from DevSecOps Trenches
29mFrom Vulnerabilities to Vigilance
59mFlying blind? - The case for API Security and Observability
33mBattle Tested Application Security
01h 32mYour Applications are Under Attack: Protecting each step of the development lifecycle
40mFantastic Red-Team Attacks and How to Find Them
16mI don’t always do AppSec testing, but when I do, it’s in production