“Closing Panel: Spectre”

on YouTube ↗43m

" summary

Discussion covers concrete mitigations, tradeoffs and timelines: OS fixes and microcode updates (IBRS/IBPB), firmware interfaces on ARM, and compiler/runtime changes like retpoline and serializing fences that hurt benchmarks but patch attack vectors. Browsers and JITs are high risk—site-level processes leak via shared VMs unless site isolation or per-site processes are used. Cloud vendors roll fixes and customers must plan regular VM/kernel updates. Windows-style Virtualization-based Security and Credential Guard are examples of usable isolation.

AI-written summary · about

" chapters (10)

1. 0:00Introduction and ground rules
2. 1:05Panelist introductions
3. 3:42Performance impact of fixes
4. 7:05Browser security challenges
5. 11:50Spectre in cloud environments
6. 14:41Fixing architectural failures
7. 18:08Security in C++ and native code
8. 25:46ARM, IBM, and microcode updates
9. 30:56Isolation and cryptographic security
10. 36:40Future hardware and conclusions

" related talks

• 50mPractical Ghostbusting: Meltdown, Spectre and YouIan Coldwater · NDC Minnesota 2018
• 46mRethinking Architectures and Abstraction for a World Where Security Improvements Matter More than Performance GainsPaul Kocher · USENIX Security '18
• 30mSpectre, Meltdown, & LinuxGreg Kroah-Hartman · LinuxCon + ContainerCon + CloudOpen China 2018
• 25mThe Memory of a MeltdownShane Cota, Chris Magistrado · BSidesSF 2018
• 51mKeynote |The Microarchitectures That I Saw And The Ones That I Hope To One Day SeeRodrigo Rubira Branco · Hardwear.io USA 2023
• 01h 01mTutorial: Side-Channel Attacks and Transient Execution Vulnerab...Allison Randal, Giorgos Christou · RISC-V Summit 2022
• 52mSecuring The Unseen: Vulnerability Research In Confidential ComputingJosh Eads, Cfir Cohen · Hardwear.io USA 2023
• 44mMake It FixablePatricia Aas · NDC London 2018