808bits

Fortanix SDKMS Appliance

FIPS 140-2 certificate #4139 · Fortanix, Inc. · data as of 2026-10-09

Fortanix SDKMS Appliance, from Fortanix, Inc., holds FIPS 140-2 certificate #4139 at overall level 3. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: The tamper evident seals installed as indicated in the security policy

Certificate

Certificate number4139
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorFortanix, Inc. · website
Hardware versionsFX2200-II-T-F, FX2200-II-SX-F, FX2200-II-TN-F, FX2200-II-SXN-F
Firmware versions3.6.20

Module description

Quoted from the NIST CMVP entry for this certificate.

Fortanix SDKMS appliance is the building block for running Fortanix Self-Defending Key Management Service (SDKMS), a unified HSM and Key Management solution. With SDKMS, you can securely generate, store, and use cryptographic keys and certificates, as well as secrets, such as passwords, API keys, tokens, or any blob of data.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (10)

AlgorithmCAVP certificates
AESC1628
CKGvendor affirmed
CVLC1628
DRBGC1628
ECDSAC1628
HMACC1628
KBKDFC1628
KTS
RSAC1628
SHSC1628, C1627

Allowed algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2022-01-19InitialAEGISOLVE, 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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2022-01-19

Source documents