SafeZone FIPS Cryptographic Module
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy
Certificate
| Certificate number | 4588 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Rambus Inc. · website |
| Software versions | 1.2.1 |
Module description
SafeZone FIPS Cryptographic Module is a FIPS 140-2 Security Level 1 validated software cryptographic module from Rambus. The module is a toolkit which provides the most commonly needed cryptographic primitives for a large variety of applications, including but not limited to, primitives needed for DAR, DRM, TLS, and VPN on mobile devices.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | A2468 |
| CKG | vendor affirmed |
| CVL | A2468 |
| DRBG | A2468 |
| DSA | A2468 |
| ECDSA | A2468 |
| HMAC | A2468 |
| KAS-SSC | A2468 |
| KBKDF | A2468 |
| KDA | vendor affirmed |
| KTS | |
| KTS-RSA | |
| PBKDF | vendor affirmed |
| RSA | A2468 |
| SHA-3 | A2468 |
| SHS | A2468 |
Allowed algorithms
MD5; NDRNG
Tested configurations
- Debian 9 Linux (64 bit) running on an ARM Cortex-A53 (ARMv8-A) with PAA
- Debian 9 Linux (64 bit) running on an ARM Cortex-A53 (ARMv8-A) without PAA
- Xubuntu 20.04 LTS (32-bit) running on an ARM Cortex-A7 (ARMv7-A)
- Xubuntu 20.04 LTS (32-bit) running on an Intel Atom x5 (Airmont) with PAA
- Xubuntu 20.04 LTS (32-bit) running on an Intel Atom x5 (Airmont) without PAA
- Xubuntu 20.04 LTS (64-bit) running on an Intel Atom x5 (Airmont) with PAA
- Xubuntu 20.04 LTS (64-bit) running on an Intel Atom x5 (Airmont) without PAA (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2023-09-07 | Initial | Leidos Accredited Testing & Evaluation (AT&E) Lab |
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: 2023-09-07