808bits

Titaniam Core Engine

FIPS 140-2 certificate #4210 · Titaniam, Inc. · data as of 2026-10-09

Titaniam Core Engine, from Titaniam, Inc., holds FIPS 140-2 certificate #4210 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement. Observed moving to historical on 2026-09-22. It was one of the last FIPS 140-2 certificates, all moved at the 140-2 sunset on 2026-09-21.
Caveat: When operated in FIPS mode

Certificate

Certificate number4210
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorTitaniam, Inc. · website
Software versions1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Titaniam Core Engine is a FIPS Approved software only cryptographic module for securing data. The module implements the cryptographic functions for Titaniam products. It includes a wide range of standards-based encryption, digital signature, and encoding algorithms as well as additional operations where FIPS approval is not applicable.

Security level exceptions

  • Cryptographic Module Specification: Level 3
  • Physical Security: N/A
  • EMI/EMC: Level 3
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (4)

AlgorithmCAVP certificates
AESA1388, A1491
HMACA1491
KBKDFA1491
SHSA1491

Tested configurations

  • Ubuntu 18.04.5 LTS running on a PowerEdge T40 Server with an Intel(R) Xeon(R) E-2224G CPU @ 3.50GHz (single-user mode)

Validation history

DateTypeLab
2022-05-04InitialAEGISOLVE, 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 at the time of the earliest snapshot
  • 2026-09-22: observed moving from active to historical
  • Validation dates on record: 2022-05-04

Source documents