Resilient Secure Software Development Through Insights Learned from Adversarial Attack Campaigns
summary
Claims a repeatable method that maps MITRE ATT&CK mitigations into concrete secure development controls by crosswalking them with NIST SSDF and OWASP ASVS and feeding campaign telemetry into a threat library. Cites that 56% of incidents trace to web/app issues and 12% of groups use public‑facing app exploits. Gives a concrete example: T1573 (encrypted channel) mitigated by disabling insecure TLS versions in code/config, and argues this yields measurable increase in resiliency and fewer exploitable weaknesses.
AI-written summary · about
chapters (6)
- 0:00Start
- 1:36Big Questions!
- 11:34Defender's / Preventer's Dilemma
- 13:22Let's "Learn Right" while we "Shift Left"
- 15:14Modelling Threats and Adversaries - 101
- 17:57MITRE ATT&CK 101
related talks
58mMITRE ATT&CK for Developers
01h 11m2024 Security BSides // Adam Pennington
39mSoftware Security Engineering (Learnings from the past to fix ...)
37mHow to get developers to want to adopt AppSec
51mSecure Applications, By Design
28mImplementing Critical Cybersecurity Controls in a DevOps Environment
28mAdversarial Intelligence: Redefining Application Security Through the Eyes of an Attacker
20mHow to Use Your Vulnerabilities to Train Your Developers on Security