808bits

Saviynt Cryptographic Module

FIPS 140-2 certificate #4120 · Saviynt · data as of 2026-10-21

Saviynt Cryptographic Module, from Saviynt, holds FIPS 140-2 certificate #4120 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.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. No assurance of the minimum strength of generated keys. This validation entry is a non-security relevant modification to Cert. #3080

Certificate

Certificate number4120
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSaviynt · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

Saviynt Cryptographic Module provides core cryptographic functions to the Saviynt Security Manager platform.

Security level exceptions

  • Physical Security: N/A

Approved algorithms (15)

AlgorithmCAVP certificates
AES4702
CKGvendor affirmed
CVL1342, 1343, 1344, 1345
DRBG1600
DSA1244
ECDSA1160
HMAC3114
KASvendor affirmed
KBKDF145
KTSvendor affirmed
PBKDFvendor affirmed
RSA2562
SHA-324
SHS3849
Triple-DES2494

Allowed algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); MD5; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • CentOS 6 and OpenJDK 1.7 running on HP ProLiant DL360 G7 Server with an Intel Xeon X5670 (single-user mode)

Validation history

DateTypeLab
2022-01-03InitialLeidos 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: 2022-01-03

Source documents