Mercury Systems ASURRE-Stor™ SSD
Mercury Systems ASURRE-Stor™ SSD, from Mercury Systems, Inc., holds FIPS 140-2 certificate #2884 at overall level 2. 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
Certificate
| Certificate number | 2884 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-Chip Embedded |
| Vendor | Mercury Systems, Inc. · website |
| Hardware versions | P/Ns ASD256AM2R-0yzIF, 3.0; ASD512AM2R-0yzIF, 3.0; ADR256AM2R-0yzIF, 3.0; ADR512AM2R-0yzIF, 3.0 (as described in Security Policy, Table 4) |
| Firmware versions | 1.5.0 and 1.5.1 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Mercury Systems ASURRE-Stor™ SSD implements an industry standard 2.5" secure solid state hard drive. Unlike many secure SSDs, the ASURRE-Stor™ SSD does not depend on a TPM device, TCG, or OPAL to implement security. Instead the ASURRE-Stor™ SSD implements security using AES-256 XTS encryption and several key management techniques that are compatible with the ATA specification. These techniques provide superior and flexible solutions for mission critical defense applications and have no requirements for unencrypted shadow MBR sectors or 3rd party OPAL software.
Security level exceptions
- Cryptographic Module Specification: Level 3
- EMI/EMC: Level 3
- Design Assurance: Level 3
- Mitigation of Other Attacks: N/A
Approved algorithms (7)
Other algorithms
NDRNG
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2017-04-19 | Initial | UL Verification Services, Inc. |
| 2019-12-18 | Update | UL Verification Services, 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: 2017-04-19, 2019-12-18