Completed
Software mitigations are expensive
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Efficiently Mitigating Transient Execution Attacks Using the Unmapped Speculation Contract
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 Transient execution attacks risk leaking information Linux maintains security using software mitigations
- 3 Software mitigations are expensive
- 4 Goal: faster mitigations
- 5 Transient execution attack example
- 6 Typical mitigation approach
- 7 Ward has a different approach
- 8 Our observation: Unmapped Speculation Contract (USC)
- 9 USC is a good hardware-software contract
- 10 Split kernel to leverage USC
- 11 Syscalls start executing in the Q-domain
- 12 World switches use two stacks
- 13 Redesigning the kernel to avoid switches
- 14 Allocating memory without world switches
- 15 Implementation
- 16 Ward does better on LEBench
- 17 Related Work: Spectrum of defenses
- 18 Open question: what is the best way to mitigate attacks?
- 19 Conclusion
