NonStop Volume Level Encryption (NSVLE)
NonStop Volume Level Encryption (NSVLE), from Hewlett Packard®, Enterprise, holds FIPS 140-2 certificate #2118 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 | 2118 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | Hewlett Packard®, Enterprise · website |
| Software versions | 2.0 and 3.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
HPE NonStop Volume Level Encryption, or NSVLE, is a fully integrated encryption solution using FIPS Approved algorithms to protect data from threats such as theft and unauthorized disclosure.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms (7)
| Algorithm | CAVP certificates |
|---|---|
| AES | 2375, 2376, 4363, 4364, C76, C77 |
| CVL | 228, 1072, C76 |
| DRBG | 311, 1402, C76 |
| HMAC | 1477, 2903, C76 |
| RSA | 1230, 2362, C76 |
| SHS | 2047, 3601, C76 |
| Triple-DES | 1486, 2359, C76 |
Other algorithms
MD5; NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength)
Tested configurations
- Debian Linux HPTE Version 5.0.0 running on an HPE ProLiant DL380p Gen8
- Debian Linux HPTE Version 7.9.1 running on an HPE ProLiant DL380 Gen9
- Debian Linux HPTE Version 8.10 running on an HPE ProLiant DL380 Gen10 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2014-04-03 | Initial | CYGNACOM SOLUTIONS INC |
| 2017-03-17 | Update | CYGNACOM SOLUTIONS INC |
| 2017-03-20 | Update | CYGNACOM SOLUTIONS INC |
| 2019-02-20 | Update | CYGNACOM SOLUTIONS 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: 2014-04-03, 2017-03-17, 2017-03-20, 2019-02-20