808bits

Encryptics® Cryptographic Library

FIPS 140-2 certificate #2162 · Encryptics · data as of 2026-08-28
Historical. 186-2 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated with module Windows Enhanced Cryptographic Provider (RSAENH) validated to FIPS 140-2 under Certs. #1002, #1330, and #1337 operating in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy.

Certificate

Certificate number2162
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorEncryptics · website
Software versions1.0.3.0

Module description

The Encryptics Cryptographic Library underpins Encryptics technology and offers protection by industry-standard, government approved algorithms to ensure that only authorized users and authorized devices are allowed to access private information stored within the .SAFE package. Encryptics for Email and Encryptics Data Protection API both leverage the Encryptics .SAFE Library to ensure use of FIPS 140-2 validated cryptography.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES739, 1168
DRBG
HMAC407, 673, 687
RSA353, 354, 557, 559, 568
SHS753, 1081

Other algorithms

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

Tested configurations

  • Microsoft Windows 7 SP1 (x64 version) with .NET Framework 3.5 running on a HP Compaq dc7600
  • Microsoft Windows Server 2008 R2 SP1 (x64 version) with .NET Framework 4.0 running on a HP Compaq dc7600 (single-user mode)
  • Microsoft Windows Vista SP1 (x64 version) with .NET Framework 3.5 running on a Dell SC430

Validation history

DateTypeLab
2014-05-28InitialCYGNACOM SOLUTIONS INC
2014-07-03Update
2016-06-16UpdateCYGNACOM 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: 2014-05-28, 2014-07-03, 2016-06-16

Source documents