808bits

NPCT7xx TPM 2.0 rev 1.59

FIPS 140-2 certificate #4411 · Nuvoton Technology Corporation · data as of 2026-10-09

NPCT7xx TPM 2.0 rev 1.59, from Nuvoton Technology Corporation, holds FIPS 140-2 certificate #4411 at overall level 2. 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 the Security Policy Section 9.2 and operated in FIPS mode

Certificate

Certificate number4411
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle Chip
VendorNuvoton Technology Corporation · website
Hardware versionsLAG019 in TSSOP28 Package, LAG019 in QFN32 Package, and LAG019 in UQFN16 Package
Firmware versions7.2.3.0, 7.2.3.1

Module description

Quoted from the NIST CMVP entry for this certificate.

Nuvoton NPCT7xx TPM 2.0 is a hardware cryptographic module that implements advanced cryptographic algorithms, including symmetric and asymmetric cryptography; as well as key generation and random number generation.

Security level exceptions

  • Physical Security: Level 3
  • EMI/EMC: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (14)

AlgorithmCAVP certificates
AESA1961
CKGvendor affirmed
CVLA1961
DRBGA1961
ECDSAA1961
ENT
HMACA1961
KAS-SSCA1961
KBKDFA1961
KDAA1961
KTS
KTS-RSA
RSAA1961
SHSA1961

Tested configurations

  • N/A

Validation history

DateTypeLab
2023-01-12InitialEWA - Canada

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-12

Source documents