808bits

J-IDMark 64

FIPS 140-2 certificate #713 · Sagem Orga · data as of 2026-10-09

J-IDMark 64, from Sagem Orga, holds FIPS 140-2 certificate #713 at overall level 3. 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: None

Certificate

Certificate number713
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle-chip
VendorSagem Orga · website
Hardware versionsHW P/N AT58829-C-AA, Version 01
Firmware versionsFW Version J-IDMark 64 IDT 005

Module description

Quoted from the NIST CMVP entry for this certificate.

The J-IDMark 64 is a single chip cryptographic module, compliant with Global Platform 2.0.1 and Sun Java Card TM 2.1.1. It runs a proprietary Applet, ID v1, which includes the following features: - A PKI-based digital signature for secure transactions and digital certificate management. - Secure storage of data and identification management rights (driving licenses, health care entitlement, car certificate, etc.). - A Match On Card mechanism which performs fingerprint verification. The J-IDMark 64 module meets the requirements to the Level 4 of FIPS 140-2 for physical security.

Security level exceptions

  • Physical Security: Level 4

Approved algorithms (5)

AlgorithmCAVP certificates
RNG187
RSA137
SHS459, 460
Triple-DES430
Triple-DES MACvendor affirmed

Other algorithms

RSA (Cert. #136; non-compliant); RSA (key wrapping, key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2006-11-02InitialUL Verification Services, Inc.
2014-01-01Update

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: 2006-11-02, 2014-01-01

Source documents