Windows 10 Mitigation Improvements
summary
Data-driven exploit analysis finds over 85% of two years of Adobe in-the-wild exploits rely on read/write primitives via vector-length corruption, prompting Flash to use the Windows heap and heap subsegment randomization; a conservative memory garbage collection for the DOM kills most use-after-free classes. An internal offensive red team prototypes bypasses and validates mitigations like Control Flow Guard, 64-bit browsing by default and virtualization-based security with hypervisor-enforced code integrity. Result: zero-day exposure for IE drops from 135 to 45 days and Edge shows ~56% fewer RCE CVEs versus IE.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:03Problem: Augmenting Preventative Security
- 7:23Strategy. Data-Driven Software Defense
- 22:10REDTEAM: Windows and Devices
- 31:48Edge attack surface reduction
- 35:2164-bit browsing by default
- 38:10Control Flow Guard Bypasses & Enhancements
- 40:09Code integrity & image load restrictions
- 41:24Dynamic code restrictions
- 42:22Windows 10 Virtualization-Based Security (VBS)
- 44:11Windows Kernel 64-bit ASLR Improvements
related talks
01h 05mFinding and Fixing Security Bugs in Flash
58mThe Code Behind The Vulnerability
58mExploiting Adobe Flash Player In The Era Of Control Flow Guard
44mCutting Edge: Microsoft Browser Security — From People Who Owned It
39mA landscape of unintended consequences
35mOn Securing Legacy Software Against Code-Reuse Attacks
41mThinking Outside the Sandbox - Violating Trust Boundaries in Uncommon Ways
45mThe Code Behind The Vulnerability
