808bits

HiCOS PKI Native Smart Card Cryptographic Module

FIPS 140-2 certificate #2595 · Chunghwa Telecom Co., Ltd. · data as of 2026-08-28
Historical. SP 800-131A transition which disallows key wrapping not compliant to SP 800-38F.. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: No assurance of the minimum strength of generated keys

Certificate

Certificate number2595
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle Chip
VendorChunghwa Telecom Co., Ltd. · website
Hardware versionsRS45C
Firmware versionsHardMask: 2.2 and SoftMask: 1.2 and 1.3

Module description

The HiCOS PKI native smart card module is a single chip implementation of a cryptographic module. The HiCOS PKI native smart card module is mounted in an ID-1 class smart card body that adheres to ISO/IEC specifications for Integrated Circuit Chip (ICC) based identification cards. The module consists of the chip (ICC), the contact faceplate, and the electronic connectors between the chip and contact pad, all contained within an epoxy substrate.

Security level exceptions

  • Cryptographic Module Ports and Interfaces: Level 3
  • Roles, Services, and Authentication: Level 3
  • Physical Security: Level 3
  • EMI/EMC: Level 3
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
CVL614
DRBG927
ECDSA731
RSA1846
SHS2953
Triple-DES1999

Other algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength); Triple-DES (Certs. #1999, key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2016-03-29InitialCGI Information Systems & Management Consultants Inc
2017-11-29UpdateCGI Information Systems & Management Consultants 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: 2016-03-29, 2017-11-29

Source documents