808bits

BitArmor Secure Cryptographic Engine

FIPS 140-2 certificate #1229 · BitArmor Systems, Inc. · data as of 2026-10-09

BitArmor Secure Cryptographic Engine, from BitArmor Systems, Inc., holds FIPS 140-2 certificate #1229 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number1229
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorBitArmor Systems, Inc. · website
Software versions1.2

Module description

Quoted from the NIST CMVP entry for this certificate.

BitArmor DataControl is an advanced software solution that provides disk encryption and device independent file/folder encryption. It provides precise access control for data on the Windows operating system. BitArmor DataControl includes automatic key management that is transparent to users and a central console for management of users and access privileges.

Security level exceptions

  • Cryptographic Module Specification: Level 3

Approved algorithms (5)

AlgorithmCAVP certificates
AES1101
HMAC614
RNG613
SHS1024
Triple-DES802

Other algorithms

DES; MD5; HMAC-MD5

Tested configurations

  • Microsoft Windows XP Professional SP3 (32-bit)
  • SuSE Linux Enterprise Server 10.0 (32-bit)
  • Windows 7 Enterprise (32-bit) (single-user mode)
  • Windows Server 2003 (32-bit)
  • Windows Server 2008 (64-bit)

Validation history

DateTypeLab
2009-11-30InitialEWA - Canada
2009-12-11Update

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: 2009-11-30, 2009-12-11

Source documents