808bits

TIMAC Cryptographic Module

FIPS 140-2 certificate #507 · ALERTCO RF/RFID · data as of 2026-09-03

TIMAC Cryptographic Module, from ALERTCO RF/RFID, holds FIPS 140-2 certificate #507 at overall level 3. 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: None

Certificate

Certificate number507
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip embedded
VendorALERTCO RF/RFID · website
Hardware versionsP/N EM01-01 Rev. 1.1
Firmware versions; 1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The TIMAC module is a 17 pin header mounted multi-chip embedded firmware microprocessor module used to encrypt and decrypt point-to-point or point-to-multipoint serial data. The device is a FIPS 140-2 Level 3 compliant and certified, high performance device implementing the AES algorithm operating in 128 bit ECB, CBC, and CFB modes. This encryption engine can be incorporated into OEM projects and products with the addition of a simple API to their hardware, for both hardwired and wireless applications, as well as any other highly secured applications such as Government and Financial Institutions. It can be used in other data transmission applications requiring NSA approved serial data encryption.

Approved algorithms (1)

AlgorithmCAVP certificates
AES149

Validation history

DateTypeLab
2005-02-11InitialUL Verification Services, Inc.
2005-04-07Update
2012-01-11UpdateUL Verification Services, 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: 2005-02-11, 2005-04-07, 2012-01-11

Source documents