Resilience starts with code. Any attack starts with code
summary
Argues that most espionage starts with bad or unchecked code, cites cases with over a thousand infections and an uncovered trove of eleven terabytes of artifacts, and shows compromises delivered via drivers, firmware and cheap €500 radio gear rather than exotic kit. Demonstrates that source-code audits and network segmentation plus monitoring and legal diligence expose backdoors and rogue updates, and that independent technical verification consistently finds the actionable evidence missing from policy-only approaches.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 3:10Software flaws and espionage risks
- 12:18Case study Kaspersky Lab software
- 22:17Risk assessment in software development
- 33:06Quality control and espionage prevention
- 36:42Q&A and closing remarks
related talks
58mKeynote: What Got Us Here Wont Get Us There
41mThe Divine and Felonious Nature of Cyber Security
01h 24mCode Red: Navigating the Minefield of Security Programming Blunders
05mEnterprise security: A new hope
32mSoftware security as a force of nature
37mStrengthening the Cybersecurity Ecosystem
54mHacked in hours: Red team assessments unveiling vulnerabilities
32mResilient Secure Software Development Through Insights Learned from Adversarial Attack Campaigns