808bits

CHR Cryptographic Module

FIPS 140-2 certificate #2946 · Bull Atos Technologies · data as of 2026-10-09

CHR Cryptographic Module, from Bull Atos Technologies, holds FIPS 140-2 certificate #2946 at overall level 3. 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: None

Certificate

Certificate number2946
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorBull Atos Technologies · website
Hardware versions006/A
Firmware versionsV1.06-02L

Module description

Quoted from the NIST CMVP entry for this certificate.

The Atos CHR is a multi-chip standalone security module providing functionality for the secure loading of applications. The CHR is the corner stone of a range of security products developed and signed by Atos as Application Provider and known as "CRYPT2Protect HR" and "CRYPT2Pay HR" product range available for different domain of applications including Banks and Financial Institutions. Additional products may be developed by Application Providers, based on the CHR.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (2)

AlgorithmCAVP certificates
RSA1884
SHS3067

Tested configurations

  • N/A

Validation history

DateTypeLab
2017-06-29InitialCGI Information Systems & Management Consultants Inc
2022-04-14UpdateAcumen Security
2022-08-23UpdateAcumen 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: 2017-06-29, 2022-04-14, 2022-08-23

Source documents