808bits

Thales CipherTrust Cryptographic Provider (CCP)

FIPS 140-2 certificate #4429 · Thales · data as of 2026-10-09

Thales CipherTrust Cryptographic Provider (CCP), from Thales, holds FIPS 140-2 certificate #4429 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 number4429
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware-Hybrid
EmbodimentMulti-Chip Stand Alone
VendorThales
Software versions1.0
Hardware versionsIntel Xeon Gold 6134

Module description

Quoted from the NIST CMVP entry for this certificate.

Thales CipherTrust Cryptographic Provider (CCP) provides cryptographic functionality either internally to the product or to external clients. The module provides support for a broad range of cryptographic services. The module uses the Intel® AES-New Instructions (AES-NI) for acceleration of AES.

Security level exceptions

  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (6)

AlgorithmCAVP certificates
AESA2124
ECDSAA2124
HMACA2124
RSAA2124
SHSA2124
Triple-DESA2124

Tested configurations

  • MS-Windows Server 2019 on VMWare ESXi 6.7.0 running on a Dell PowerEdge R720 with Intel Xeon Gold 6134 with PAA
  • RHEL Version 8.3 on VMWare ESXi 6.7.0 running on a Dell PowerEdge R720 with Intel Xeon Gold 6134 with PAA (single-user mode)

Validation history

DateTypeLab
2023-01-27InitialAcumen Security

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: 2023-01-27

Source documents