HP LTO-6 Tape Drive
HP LTO-6 Tape Drive, from Hewlett-Packard Company, holds FIPS 140-2 certificate #2019 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: None
Certificate
| Certificate number | 2019 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Hewlett-Packard Company · website |
| Hardware versions | AQ278A #912 [1], AQ278B #901 [2], AQ278C #704 [3], AQ288D #103 [4], AQ298C #103 [5], and AQ298A #900 [6] |
| Firmware versions | J2AW [1], J2AZ [2], J2AS [3], 32AW [4], 22CW [5], and 22CZ [6] |
Module description
Quoted from the NIST CMVP entry for this certificate.
HP LTO-6 tape drives help to keep pace with data growth with up to 6.25TB compressed data storage per cartridge and capable of compressed data transfer rates of up to 400MB/sec. Ground breaking LTFS technology makes LTO-6 tapes as easy to use as disk and enables easy file access, reliable long term archive retrieval and simpler transportability between systems. LTO-6 tape drives also provide easy-to-enable security to protect the most sensitive data and prevent unauthorized access of tape cartridges with AES 256-bit hardware data encryption.
Approved algorithms (6)
| Algorithm | CAVP certificates |
|---|---|
| AES | 1442, 2189, 2190 |
| CVL | vendor affirmed |
| DRBG | 256 |
| HMAC | 1342 |
| RSA | 1128, 1129 |
| SHS | 1897, 1898 |
Other algorithms
MD5; AES (AES Cert. #2189, key wrapping); RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength); NDRNG
Validation history
| Date | Type | Lab |
|---|---|---|
| 2013-11-07 | Initial | 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: 2013-11-07