SafeNet ProtectDrive Cryptographic Engine
SafeNet ProtectDrive Cryptographic Engine, from SafeNet, Inc., holds FIPS 140-2 certificate #2001 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.
Caveat: When operated in FIPS mode. For Windows 7: With module Microsoft Windows 7 Kernel Mode Cryptographic Primitives Library (cng.sys) validated to FIPS 140-2 under Cert. #1328 operating in FIPS mode
Certificate
| Certificate number | 2001 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | SafeNet, Inc. · website |
| Software versions | 1.0.1 |
Module description
Quoted from the NIST CMVP entry for this certificate.
SafeNet ProtectDrive Cryptographic Engine 1.0.1 provides cryptographic services and key management for the SafeNet ProtectDrive Disk Encryption product. SafeNet ProtectDrive delivers full disk encryption for general purpose computers, laptops and removable media.
Security level exceptions
- Roles, Services, and Authentication: Level 3
- EMI/EMC: Level 3
- Design Assurance: Level 3
Approved algorithms (5)
| Algorithm | CAVP certificates |
|---|---|
| AES | 1998, 1999, 2000 |
| HMAC | 1208, 1209, 1210 |
| PBKDF2 | vendor affirmed |
| RNG | 1048 |
| SHS | 1751, 1752, 1753, 1754 |
Other algorithms
DES; Triple-DES (non-compliant); IDEA; RSA (non-compliant)
Tested configurations
- Windows 7 Ultimate Edition SP1 (X64 version) running on Dell E6400 (single-user mode)
- Windows 7 Ultimate Edition SP1 (X86 version) running on Dell E6400
- Windows XP SP3 (X86 version) running on Dell E6400
Validation history
| Date | Type | Lab |
|---|---|---|
| 2013-09-17 | Initial | CGI Information Systems & Management Consultants Inc |
Status timeline
As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.
- 2026-08-21: first observed by this tracker, status historical
- Validation dates on record: 2013-09-17