So You Think You Can Patch
summary
Panel documents concrete failure modes and mitigations: 4,687 NVD entries in three months, auto‑updates that brick a laptop, organizations that skip patches for two years, FDA forcing recalls of unpatchable medical devices, and patches that introduce new vulnerabilities. Explains causes — vendor end‑of‑life, blocked auto‑update, testing windows that can stretch to years, remote/embedded devices — and practical responses: network segmentation, IPS in front of legacy gear, rip‑and‑replace, improved asset inventory and software bill of materials plus playbooks for when patching isn’t viable.
AI-written summary · about
chapters (10)
- 0:00Welcome to the game
- 2:17Industry survey findings
- 6:11Patch fail stories
- 7:58Reasons systems aren't patched
- 13:32Mandating patching concerns
- 16:22Solutions beyond just patching
- 18:54IoT and patching complexity
- 20:39Community solutions for patching
- 23:27Final Jeopardy round
- 24:51Closing remarks
related talks
23mConflicts in Vulnerability Management and Patching
30mSoftware Patching Needn't Be a Can of Worms
39mTo Patch or Not to Patch OT— A Risk Management Decision
25mYou don’t have to patch!
22mGive up! Just stop patching vulnerabilities!
42mPanel: The Right To Secure; What, Who, How And Why!
34mSafety vs Security: A Tale of Two Updates
35mMeasuring change: Responding to cyber material risk