Security: The world is broken and you are guilty
summary
Argues that the Internet and common protocols are routinely misused with concrete examples: BGP route hijacks that reroute traffic across continents, local ARP spoofing on Wi‑Fi, and TLS failures because CAs get compromised (Comodo, Trustwave) or servers still support insecure SSL. Recommends specific mitigations: derive requirements from risk analysis and use OWASP ASVS rather than just Top 10, run active scans with a ZAP proxy, and build an internal security‑testing practice that proved effective.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:50About me
- 4:43Security Metric
- 6:27Broken
- 7:31Internet
- 9:22Wireless
- 11:23TLS
- 16:47CI fails
- 18:59Do your own encryption
- 21:36What about applications
- 22:11Wild guess
- 23:35Developers are guilty
- 23:54Security conferences
- 24:34Are we guilty
- 25:15Secure vs insecure
- 26:02Security requirements
- 26:27Is it simple
- 27:14What should you look after
- 27:34What should your customer do
- 28:49CIA triad
- 33:10Security standard
- 34:48What you could do
- 35:19Standard architecture
- 37:20Default Security
- 39:12People
- 40:53Questions
related talks
33mInterview with
13mA Positive Security Talk
38mDo You Feel Secure?
44mA Matter Of Trust: When Security Is Not Enough
59mProactively defending your business
34mWeb security explored through horror movies
55mBreaking and Fixing Web Application Security
01h 00mKeynote - Our Kryptonite: A Defendable Internet