808bits

ypsID

FIPS 140-2 certificate #1459 · Morpho - e-Documents Division · data as of 2026-10-09

ypsID, from Morpho - e-Documents Division, holds FIPS 140-2 certificate #1459 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 number1459
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentSingle-chip
VendorMorpho - e-Documents Division
Hardware versionsP/N AT90SC25672RCT-USB
Firmware versions01029069 - FFFFFFF or 020000202 - FFFFFFF

Module description

Quoted from the NIST CMVP entry for this certificate.

The ypsid common cryptographic module lies at the core of the Sagem Orga authentication and signature tokens for corporate employees, civil servants, and e-commerce / e-banking online clients. This module is the base for : ypsid SmartCard S2 converged smart card access badges with PKI, minex II approved biometric fingerprint Match-on-card and One time password (OTP) and ypsid Keys: E*, E1, and E2 USB cryptographic keys presenting driverless and zero footprint two factor OTP authentication and digital signature.

Security level exceptions

  • Physical Security: Level 4

Approved algorithms (5)

AlgorithmCAVP certificates
RNG671
RSA580, 581
SHS1113
Triple-DES872
Triple-DES MACvendor affirmed

Other algorithms

Triple-DES (Cert. #872, key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant)

Validation history

DateTypeLab
2010-11-29InitialUL Verification Services, Inc.
2011-04-06UpdateUL Verification Services, Inc.
2011-07-19UpdateUL 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: 2010-11-29, 2011-04-06, 2011-07-19

Source documents