Introduction
Intel® Total Storage Encryption (TSE) is a platform-level data protection solution that provides transparent, hardware-assisted encryption for storage devices with minimal impact on system performance. It integrates with Intel® platform security features to safeguard data at rest while maintaining a seamless user experience. Key Capabilities
Available Downloads
- Size: 3.7 MB
- SHA256: 1FFBD2036AC3F5CFA8CC7E334A5A79F3B0BADACE3D3CD269E86396683292F152
Detailed Description
Intel® Total Storage Encryption (TSE) is a platform-level data protection solution that provides transparent, hardware-assisted encryption for storage devices with minimal impact on system performance. It integrates with Intel® platform security features to safeguard data at rest while maintaining a seamless user experience.
Key Capabilities
-
Encryption with minimal system performance impact
- Leverages hardware-assisted encryption mechanisms
- Designed to reduce CPU utilization compared to software-only encryption
-
Transparent OS integration
- Works seamlessly with Windows storage stack and BitLocker
- No changes required to user workflows or applications
-
Full-disk data protection
- Encrypts all data written to supported storage devices
- Helps protect against unauthorized access to physical drives
-
Platform-level security integration
- Integrates with Intel chipset, firmware, and storage drivers
- Supports modern Windows security requirements
-
Enterprise-ready deployment
- Enables OEM integration for client platforms
- Suitable for systems requiring data-at-rest protection with minimal performance overhead
Supported Environments
-
Intel® Core™ Ultra Series 3 vPro platforms (e.g., Panther Lake)
- Windows 11 (24H2 / 25H2)
-
Supported PCIe NVMe pass-thru configurations via either MSFT inbox storage or Intel RST (Rapid Storage Technology) drivers
Disclaimers1
Product and Performance Information
Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.