Building an Assurance and Secure Development Program
summary
Covers how Android builds an assurance program by combining an SDL, threat modeling with STRIDE, and concrete tooling: Haiku fuzzing on ~200 devices for native decoder bugs (fuzzing finds Stagefright-class issues), LibFuzzer-based corpora, static analysis (clang/FindBugs) and external pen tests on production, plus an Android Advanced Assurance Program spanning supply chain to incident response. Policies mandate AES-256 everywhere for disk, a security bug bar that refuses RCE and routes sev0 bugs signed by CEO, and a required final security review and playbooks before release.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 3:37History of security assurance
- 6:03Prerequisites for a security program
- 10:38Policy frameworks and artifacts
- 13:27Secure Development Lifecycle basics
- 15:15Security bug bar and risk acceptance
- 18:48Risk assessment and threat modeling
- 27:33Static and dynamic analysis tools
- 31:04Fuzzing and crash testing
- 33:32Final security review and lessons learned
- 35:15Incident response planning
- 37:02Resources and closing
related talks
38mBuilding a Security Assurance Program
42mTesting Android Security
48mMastering Android Security Research: A Guide for the Modern Security Researcher
29mSecuring Android Applications - The not so se…
34mSecuring Android: Tackling Advanced Threats and Enhancing App Security
34mDemystifying Android Security
53mThe Art of Defense - How Vulnerabilities Help Shape Security Features and Mitigations in Android
26mHow to become your app's 'security champion'.