Nishanth Lingamneni Program Manager Microsoft Corporation SYS-007T

Introduction Market demand for hardware-enabled encryption Problem statement; value proposition Demo Ecosystem status and opportunities Requirements for eDrive; eDrives versus self-encrypting devices (SEDs) Call to action

What is an eDrive? A regular storage subsystem (Embedded MultiMediaCard, solid-state drive, hard disk drive) that comes with hardware offload to accelerate crypto processing How is it different from SEDs? Self-encrypting drive Trusted Computing Group (TCG) standards Encrypted drive TCG standards + IEEE 1667 Why should the ecosystem care? Initial-time hardware-based encryption is negligible Faster than software-based encryption during standard operation Removes initial and on-going performance hit caused by software- based encryption, be it BitLocker® drive encryption or other third-party software Standardized in-box support can enable broad adoption

Customers/OEMs Data is always encrypted Low opportunity costCustomers/OEMs Data is always encrypted Low opportunity cost Cost savings Eliminates provisioning time Reduces CPU cycles, power Reduces testing, qualification cost Cost savings Eliminates provisioning time Reduces CPU cycles, power Reduces testing, qualification cost Windows experience Seamless out-of-box experience (OOBE) Windows experience Seamless out-of-box experience (OOBE) Compliance Improves ecosystem health through Device Certification; system CertificationCompliance Improves ecosystem health through Device Certification; system Certification

eDrive with Bitlocker in Windows 8 Demo

Goals of feature Short term: Each original equipment manufacturer (OEM) supports few PC configurations with eDrives at Windows 8 general availability (GA); top-tier independent hardware vendors (IHVs) and independent software vendors (ISVs) support eDrive by Windows 8 GA Long term: eDrives are ubiquitous Run-time performance comparison Throughput (in MBPS)* Value proposition recap Initial encryption time eliminated Non-eDrive > 1 hour 20 minutes eDrive < 5 seconds For 150 GB HDD on MSIT standard laptop running Windows 8; Encryption SW used: Bitlocker drive encryption Run-time performance significantly improved * 15 to 35% improvement in data throughput Common scenarios like startup, sleep, hibernate also improved eDrive-enabled systems have improved CPU utilization, battery life * Higher throughput is more desirable..

Tablet storage performance requirements Random 4-KB write IOPs >= 200 Random 4-KB read IOPs >= 2000 Sequential write speed >= 40 MB/s Sequential read speed >= 60 MB/s Max I/O latency < 500 milliseconds Additional I/O latency requirement Maximum of 20 seconds sum-total of user-perceivable I/O latencies over any 1 hour period of a user- representative workload, where a user-perceivable I/O is defined as having a latency of at least 100 milliseconds R/W 2:1 random 4-KB workload IOPS >= 500 eDrive capable eMMC memory supports eDrive functionality in Windows 8 by Active power < 800 mw Idle power < 1.5 mw

Hardware requirements When eDrive is present, must support IEEE 1667-TCG Silo TCG-OPAL, OPAL v2 + Fixed ACL + Additional Data Store Windows 8 system certification requirements UEFI (Section relevant to eDrives), Class II no CSM/Class III