808bits

IDPrime PIV v3.0 Applet on IDCore 3130 Platform

FIPS 140-2 certificate #3417 · Gemalto · data as of 2026-08-28
Historical. SP 800-56Arev3 transition - replaced by certificate #4563. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When initialized and configured as specified in Section 13 of the Security Policy

Certificate

Certificate number3417
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle Chip
VendorGemalto · website
Hardware versionsSLE78CFX400VPH with packaging options A1977038 and A2410334 and SLE78CLFX400VPH with packaging option A1714221
Firmware versionsIDCore 3130 (Build09C) with Applets [PIV v3.0 (Build08), PIV Admin v3.0 (Build 08), MoC Server (version 1.1)]

Module description

« IDPrime PIV v3.0 » is the next generation of FIPS201-2 smart card running on latest IDCore 3130 platform, which complies with the latest version of NIST SP800-73-4, SP800-85A-4 and all algorithms of SP800-78-4. The product can be used over Contact and Contactless interfaces (ISO 7816 & 14443) to provide physical and logical accesss control. It embeds latest optimized FIPS POST feature, OPACITY secure messaging with Pairing code, and Biometric Match on card.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES5243
CKGvendor affirmed
CVL1713, 1714, 1715, 1716, 1717
DRBG2005
ECDSA1365
KAS165
KBKDF177
KTS
KTSvendor affirmed
RSA2802, 2803
SHS4221
Triple-DES2651

Allowed algorithms

EC Diffie-Hellman (key agreement; key establishment methodology provides 192 bits of encryption strength); NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2019-03-27InitialUL Verification Services, Inc.
2019-06-06UpdateUL 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: 2019-03-27, 2019-06-06

Source documents