808bits

NITROX XL 1600-NFBE HSM Family

FIPS 140-2 certificate #3280 · Cavium Inc. · data as of 2026-10-21

NITROX XL 1600-NFBE HSM Family, from Cavium Inc., holds FIPS 140-2 certificate #3280 at overall level 3. 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.

Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and initialized and configured per the Security Policy. This validation entry is a non-security-relevant modification to Cert. #3248

Certificate

Certificate number3280
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeSoftware
EmbodimentMulti-Chip Embedded
VendorCavium Inc. · website
Hardware versionsCN1610-NFBE1-3.0-G, CN1620-NFBE1-3.0-G, CN1620-NFBE3-3.0-G, CN1610-NFBE1-2.0-G, CN1620-NFBE1-2.0-G, CN1620-NFBE3-2.0-G and FN1620-NFBE2-G
Firmware versionsCN16XX-NFBE-FW-2.3-180205 and CN16XX-NFBE-FW-2.3-180821

Module description

Quoted from the NIST CMVP entry for this certificate.

The NITROX XL 1600-NFBE HSM adapter family delivers the world's fastest FIPS 140-2 Level 3 Hardware Security Module (HSM) with PCIe Gen 2.0. The HSM family of offers up to 9000 RSA 2k-bit operations per second and 5 Gbps of bulk crypto.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (11)

AlgorithmCAVP certificates
SHS (Certs. #801, #1165 and #1379
AES1265, 2899, 4026
CKGvendor affirmed
CVL166, 847
DRBG32
ECDSA1276
HMAC443, 736, 1677
KAS153
KTS
RSA2701
Triple-DES898, 2204

Allowed algorithms

MD5; NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 128 bits of encryption strength)

Validation history

DateTypeLab
2018-09-05InitialAcumen Security

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: 2018-09-05

Source documents