808bits

TSPP

FIPS 140-2 certificate #1322 · Thales e-Security Inc. · data as of 2026-10-21

TSPP, from Thales e-Security Inc., holds FIPS 140-2 certificate #1322 at overall level 3. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number1322
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip embedded
VendorThales e-Security Inc. · website
Hardware versionsP/Ns TSPP-A and TSPP-B Version 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4 or 1.0.5
Firmware versions1.10.2

Module description

Quoted from the NIST CMVP entry for this certificate.

Thales' TSPP is the multi-chip embedded cryptographic module in its payShield 9000 family of hardware security modules used in the Banking and Finance sector for securing card-based payment transactions. The product family is also used to provide dedicated functionality for key management and message security using algorithms such as Triple-DES, RSA, SHA, HMAC, and AES. TSPP contains a secure bootstrap that authenticates application loading using DSA 2048, so that only application software written by and "signed" by Thales can be loaded and run on TSPP-based products.

Approved algorithms (2)

AlgorithmCAVP certificates
DSA375
SHS1071

Validation history

DateTypeLab
2010-06-22InitialUL Verification Services, Inc.
2011-03-28UpdateUL Verification Services, Inc.
2011-04-12UpdateUL Verification Services, Inc.
2011-11-08UpdateUL Verification Services, Inc.
2012-01-11UpdateUL Verification Services, Inc.
2012-07-09Update
2013-03-28UpdateUL Verification Services, Inc.
2017-01-30UpdateUL Verification Services, 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
  • Validation dates on record: 2010-06-22, 2011-03-28, 2011-04-12, 2011-11-08, 2012-01-11, 2012-07-09, 2013-03-28, 2017-01-30

Source documents