808bits

Trusted Platform Module 2.0 SLB 9670

FIPS 140-2 certificate #3203 · Infineon Technologies AG · data as of 2026-10-21

Trusted Platform Module 2.0 SLB 9670, from Infineon Technologies AG, holds FIPS 140-2 certificate #3203 at overall level 2. 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. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode as specified in Security Policy Sections 1.1 and 8.1

Certificate

Certificate number3203
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle Chip
VendorInfineon Technologies AG · website
Hardware versionsSLB 9670 (Package PG-UQFN-32-1 or PG-VQFN-32-13)
Firmware versions7.83

Module description

Quoted from the NIST CMVP entry for this certificate.

The TPM is a single chip module that provides computer manufacturers with the core components of a subsystem used to assure authenticity, integrity and confidentiality in e-commerce and internet communications within a Trusted Computing Platform. The TPM is a complete solution implementing the Trusted Platform Module Library Specification, Family "2.0", Level 00, Revision 01.16, October 2014 (ISO/IEC 11889:2015, Parts 1-4). See http://www.trustedcomputinggroup.org/ for further information on TCG and TPM.

Security level exceptions

  • Physical Security: Level 3
  • EMI/EMC: Level 3

Approved algorithms (11)

AlgorithmCAVP certificates
AES5069
CKGvendor affirmed
CVL1629, 1630
DRBG1886
ECDSA1314
HMAC3383
KAS157
KBKDF172
KTSvendor affirmed
RSA2749
SHS4129

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2018-06-20InitialUL 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: 2018-06-20

Source documents