808bits

J-IDMark 64 PIV

FIPS 140-2 certificate #774 · Sagem Orga · data as of 2026-09-03

J-IDMark 64 PIV, from Sagem Orga, holds FIPS 140-2 certificate #774 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number774
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle-chip
VendorSagem Orga · website
Hardware versionsP/N AT58803-H-AA
Firmware versions01016221/FFFFFFFF, PIV applet A0000002430015010100010601 V01

Module description

Quoted from the NIST CMVP entry for this certificate.

The J-IDMark 64 PIV is a single chip cryptographic module, which combines a PIV FIPS 201 compliant applet (SP 800-73) loaded on J-IDMark 64 Open, a dual (contact & contactless) interface platform compliant with the latest Java CardTM 2.2/Global Platform 2.1.1 specifications, FIPS 140-2 Level 3 Approved and Level 4 Approved for physical security. Thus J-IDMark 64 PIV module is a reliable and standardized solution for PIV systems, which allow managing physical and logical access to Federal government facilities and systems, by help of identity credentials.

Security level exceptions

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

Approved algorithms (7)

AlgorithmCAVP certificates
AES459
CVL207
RNG244
RSA179, 180
SHS525
Triple-DES480
Triple-DES MACvendor affirmed

Validation history

DateTypeLab
2007-05-18InitialUL Verification Services, Inc.
2008-04-29Update
2014-02-06Update

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: 2007-05-18, 2008-04-29, 2014-02-06

Source documents