808bits

Verdasys Secure Cryptographic Module

FIPS 140-2 certificate #3627 · Digital Guardian, LLC · data as of 2026-09-12

Verdasys Secure Cryptographic Module, from Digital Guardian, LLC, holds FIPS 140-2 certificate #3627 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

Certificate

Certificate number3627
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorDigital Guardian, LLC · website
Software versions1.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The Verdasys Secure Cryptographic Module, VSEC.SYS, is a software module that provides cryptographic services for Digital Guardian's DG Agent for Windows endpoint products. The Verdasys Secure Cryptographic Module is leveraged in a variety of functions including securing communication, protecting agent components, and file encryption.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
AES5322
CKGvendor affirmed
CVL1789
DRBG2052
HMAC3520
KTS
RSA2850
SHS4274

Allowed algorithms

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

Tested configurations

  • Microsoft Windows 10 (64-bit) running on a Dell Latitude E6330 with an Intel Core i7 (single-user mode)

Validation history

DateTypeLab
2020-03-03InitialLeidos Accredited Testing & Evaluation (AT&E) Lab
2020-03-20UpdateLeidos 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: 2020-03-03, 2020-03-20

Source documents