808bits

Thales Alenia Space cryptographic module for Microsemi RTAX FPGA

FIPS 140-2 certificate #4065 · Thales Alenia Space · data as of 2026-10-09

Thales Alenia Space cryptographic module for Microsemi RTAX FPGA, from Thales Alenia Space, holds FIPS 140-2 certificate #4065 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 installed, initialized and configured as specified in Section 12.4 of the Security Policy.

Certificate

Certificate number4065
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorThales Alenia Space · website
Hardware versionsRTAX2000S FPGA; 28C010T EEPROM
Firmware versions3.32.00; 3.32.04

Module description

Quoted from the NIST CMVP entry for this certificate.

Cryptographic module encrypt and decrypt input packets, using one of the thirty two possible keys. There are several TC/TM to check: status, number of packets correctly deciphered, number of ciphered packet, etc. There are three UART interfaces for: ground, key and housekeeping (the last one has a redundant interface).

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (1)

AlgorithmCAVP certificates
AESA1721

Tested configurations

  • N/A

Validation history

DateTypeLab
2021-11-02InitialDEKRA Testing and Certification S.A.U

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: 2021-11-02

Source documents