808bits

Tanium Cryptographic Module

FIPS 140-2 certificate #2736 · Tanium, Inc. · data as of 2026-08-28
Historical. Moved to historical list due to dependency on certificate #1329. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: The module generates cryptographic keys whose strengths are modified by available entropy. When operating with the BCRYPTPRIMITIVES.DLL module validated to FIPS 140-2 under Certificates #1329, #1336, and #1892 operating in FIPS Mode

Certificate

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

Module description

The Tanium Cryptographic Module underpins Tanium's security management platform. Tanium's platform is a security and configuration management solution that provides instant visibility and allows enterprises to collect data and update machines in any-sized network, in seconds. Tanium's platform is able to query information from hundreds of thousands of machines in seconds because of its intelligent peer-to-peer communication model. This speed means that information is current and accurate when assessing a security threat or vulnerability.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES3876
CVL744, 745
DRBG1105
ECDSA836
HMAC2519
SHS3197

Other algorithms

NDRNG

Tested configurations

  • Microsoft Windows 7 (32-bit) running on a Dell PowerEdge R430
  • Microsoft Windows 7 (64-bit) running on a Dell PowerEdge R430
  • Microsoft Windows Server 2008 R2 (64-bit) running on a Dell PowerEdge R430
  • Microsoft Windows Server 2012 (64-bit) running on a Dell PowerEdge R430 (single-user mode)

Validation history

DateTypeLab
2016-09-02InitialEWA - Canada

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: 2016-09-02

Source documents