808bits

Entrust IdentityGuard PIV Credential

FIPS 140-2 certificate #1882 · Entrust, Inc. · data as of 2026-08-28
Historical. 01-2999 was dropped so this certificate is moving to the historical list.. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with PIN policies configured as indicated in the Security Policy Section 9

Certificate

Certificate number1882
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle-chip
VendorEntrust, Inc. · website
Hardware versionsSCHW 1.0
Firmware versionsSCOS 1.0 with Entrust IdentityGuard PIV Applet 1.0.1 Patch 172799

Module description

The Entrust IdentityGuard PIV Credential is a cryptographic module intended for use by US Federal agencies and other markets that require smartcards conformant with the PIV standards. The module can also be configured for use in markets where the set of keys and data objects, or the access control rules governing their use, differ from the PIV data model.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES1769
CVL5
CVL219, 223
ECDSA237
RNG942
RSA885
Triple-DES1144
Triple-DES MACvendor affirmed

Other algorithms

HW RNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); AES (Cert. #1769, key wrapping; key establishment methodology provides 256 bits of encryption strength); Triple-DES (Cert. #1144, key wrapping; key establishment methodology provides 112 bits of encryption strength)

Validation history

DateTypeLab
2013-02-08InitialUL Verification Services, Inc.
2014-02-06Update
2014-05-28Update

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: 2013-02-08, 2014-02-06, 2014-05-28

Source documents