Designing Like a Hacker
summary
Designers learn that most breaches exploit humans not code: visiting haveibeenpwned shows many accounts already breached, Verizon data says 82% of breaches involve the human element, and 2.9% click rates imply ~33 million exposed records. Real incidents include Log4j remediation chaos, a 2017 Wells Fargo leak of 50,000 customers, and malware-as-a-service dashboards like DuckLogs with leaderboards. Recommended fixes: audit login/reset/checkout flows, remove unnecessary data storage, and add low-friction controls such as Nintendo’s QR mobile login instead of typing complex passwords.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 1:53Why cyber security matters
- 9:51Hacking as a business model
- 16:11Design as social engineering
- 17:16Nine laws of information risk
- 24:00Balancing security and friction
- 28:13Ethical obligations in design
- 35:05Q&A session
related talks
40mData Breaches: Barbarians in the Throne Room
58mSocial Engineering: Hacking Humans
26mThe Risky Business of Risk Illiteracy (Sean Juroviesky)
28mSecurity Through Design - Making Security Better By Designing for People
46mSocial Engineering: Hacking Humans
41mHacking Humans : Social Engineering Techniques and How to Protect Against Them
40mWeb Attacks and Fraud: Lessons Learned from the Deep End of the Pool
44mHacking Humans: Social Engineering Techniques