808bits

Self-Defending Key Management Service™

FIPS 140-2 certificate #3326 · Fortanix, Inc. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: The module generates cryptographic keys whose strengths are modified by available entropy. When operated in FIPS mode

Certificate

Certificate number3326
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorFortanix, Inc. · website
Software versions2.0.596 and 2.0.NOAESNI-182

Module description

Fortanix Self-Defending Key Management Service™ (SDKMS) is the world’s first cloud service secured with Intel® SGX and built using Fortanix’s patented Runtime Encryption Technology. With SDKMS, you can securely generate, store, and use cryptographic keys and certificates, as well as secrets, or any blob of data. You can integrate with SDKMS using legacy cryptographic interfaces or using its native RESTful interface. SDKMS ensures that you remain in complete control over your keys and secrets. It provides access control to users and applications to enforce authorized access to keys.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES5328, 5329, 5379, 5380
CKGvendor affirmed
CVL1818, 1822
DRBG2072, 2073
ECDSA1418, 1419
HMAC3526, 3527
KDF191, 195
KTS
KTS
KTS
KTS
RSA2876, 2877
SHS4280, 4281

Allowed algorithms

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

Tested configurations

  • Ubuntu 16.04 running on a General purpose x86 based server (SuperMicro SYS-5019S-MR) with Intel® Xeon® CPU E3-1230 V5 @3.40GHz with PAA
  • Ubuntu 16.04 running on a General purpose x86 based server (SuperMicro SYS-5019S-MR) with Intel® Xeon® CPU E3-1230 V5 @3.40GHz without PAA (single-user mode)

Validation history

DateTypeLab
2018-11-13InitialAEGISOLVE, 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: 2018-11-13

Source documents