Philosophizing Security In A "Mobile-First" World
summary
Argues that engineering bias misses real threats and gives concrete findings: user error is the single biggest breach cause, apps now carry 80% of online time, and device checks via RASP show ~20% lack screen lock and ~38% lack biometrics. Describes practical tools—an SDK for runtime protection, targeted fraud detection and in‑app reporting—and a proposal to collect labeled attack vectors for shared, ML‑driven defense; prototypes show promise but wide sharing is not yet realized.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 8:32Mobile security challenges
- 13:14Engineering bias in security
- 18:14User mistakes as weakest link
- 21:07Security versus safety
- 26:09Digital security social contract
- 30:08Mobile-first security gaps
- 31:56Philosophical app security
- 36:30Security theater and trust
- 39:47Productizing security
- 45:21Reporting abuse and defense
- 48:16Attack vector intelligence
- 50:25Key takeaways and closing remarks
related talks
46mKeynote: The Moral Imperatives and Challenges for Modern Application Security
42mKeynote: How much security is too much?
40mBest practices for shielding mobile apps from emerging threats
26mHow to become your app's 'security champion'.
21mWhen Attackers Go Mobile-First: What Developers Need to Know
21mSecuring the Unseen: Advanced Threats, Best Practices & Challenges in Mobile App Security
24mModern Android App Security: Protecting Code, Keys, and Data
44m(in)Security is eating the world