An Ant in a World of Grasshoppers
summary
Security failures persist not for lack of warnings but because of tradeoffs: consumer devices ship with exposed baby monitors and millions of web‑visible cameras, inboxes see 100–300 messages a day, users maintain ~100 passwords, and teams drown in long security backlogs that treat every issue as an emergency. Practical fixes that work include disable SMBv1 as a pragmatic WannaCry mitigation, scan ports for 3–6 months then auto‑close unused ones, use a password manager with paper backups when needed, and simple design choices like wake word on the box to reduce misuse.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:52Cyber Security Today
- 2:32Patching
- 3:02Security
- 3:51Voting Machines
- 4:29Factors of Security
- 5:36Consumer Advice
- 9:16Security Requirements
- 9:44Security Teams
- 12:19Gotcha
- 12:56What does work
- 13:20Partnering with people
- 15:37Make security easy
- 16:50Reasonable security advice
- 18:04Building technology once
- 19:07Looking forward
- 19:56Questions
- 21:36Product Liability Laws
- 22:30Security vs Design
- 24:29Security vs User Participation
- 25:23Customer Data
- 26:20Security Mindset
- 27:24Is there any way to get the information out
- 28:24Threat modeling
- 29:43Security breaches
related talks
01h 03mWhy Don't Users Do What They are Supposed to Do? A look at users and security
48mSecuring The Internet Of Things
46mFire, Brimstone, and Bad Security Decisions
42mKeynote: How much security is too much?
58mSecuring a World of Physically Capable Computers
41mSecurity: The world is broken and you are guilty
27mProtecting Businesses from Breaches: Simple Lessons Still Unlearned
48mSecurity from zero