808bits

TecSec PIV Eagle Card - Contact

FIPS 140-2 certificate #1120 · TecSec, Atmel, CPI Card Group, and Athena Smartcard · data as of 2026-08-28
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 number1120
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentSingle-chip
VendorTecSec, Atmel, CPI Card Group, and Athena Smartcard · website
Software versionsP/N TecSec Contact PIV Applet Version 1.01 JCT
Hardware versionsP/N Atmel AT90SC144144CT Revision G
Firmware versionsP/N Athena IDProtect XL Version 010A.7204.0004

Module description

The TecSec PIV Eagle Card - Contact cryptographic module provides data security for government and enterprise personnel identification. The primary purpose of this device is to enable the creation of a dual-chip PIV smart card as described in [FIPS201] that is fully compliant with the end-point service specified in SP800-73-1. The CM contains two Java Card applets implementing the PIV functionality (the Software) running on a GlobalPlatform Java Card operating system (the Firmware). The CM is physically connected to a smart card contact plate as defined in [7816-1] and [7816-2].

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES639
CVL209
RNG364
RSA292
SHS674
Triple-DES592
Triple-DES MACvendor affirmed

Other algorithms

RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2009-04-03InitialUL Verification Services, Inc.
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: 2009-04-03, 2014-02-06

Source documents