808bits

Vormetric Encryption Expert Cryptographic Module

FIPS 140-2 certificate #1721 · Vormetric, Inc. · data as of 2026-09-14

Vormetric Encryption Expert Cryptographic Module, from Vormetric, Inc., holds FIPS 140-2 certificate #1721 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 number1721
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorVormetric, Inc. · website
Software versions4.4.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The Vormetric Encryption Expert Cryptographic Module is a loadable kernel module also known as "SECFS" (SECure File System). This module is a file system layer that enforces an access and encryption policy upon selected data on end-user systems. The policy specifies a key to be used when writing data to disk and while reading data from disk. This module contains the Vormetric Encryption Expert Cryptographic Library, which provides all cryptographic services.

Security level exceptions

  • Design Assurance: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES1820
HMAC1075
SHS1596
Triple-DES1173

Other algorithms

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

Tested configurations

  • HPUX 11i v3 64-bit (single-user mode)
  • Redhat Linux 5.7 64-bit
  • Solaris 10 64-bit
  • Windows 2003 32-bit
  • Windows 2008 64-bit

Validation history

DateTypeLab
2012-05-23InitialCYGNACOM SOLUTIONS INC
2012-06-05Update

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: 2012-05-23, 2012-06-05

Source documents