808bits

Vormetric Encryption Expert Cryptographic Module

FIPS 140-2 certificate #2342 · Vormetric, Inc. · data as of 2026-10-21

Vormetric Encryption Expert Cryptographic Module, from Vormetric, Inc., holds FIPS 140-2 certificate #2342 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 number2342
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware-Hybrid
EmbodimentMulti-chip standalone
VendorVormetric, Inc. · website
Software versions5.1.3
Hardware versionsE5-2670

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

  • Mitigation of Other Attacks: N/A

Approved algorithms (4)

AlgorithmCAVP certificates
AES2807
HMAC1758
SHS2355
Triple-DES1685

Other algorithms

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

Tested configurations

  • Red Hat Enterprise Linux 6.3 running on a Supermicro X9DR7, SUSE Linux Enterprise Server 11 SP 2 running on a Supermicro X9DR7 (single-user mode)

Validation history

DateTypeLab
2015-03-24InitialCYGNACOM SOLUTIONS 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: 2015-03-24

Source documents