TecSec PIV Eagle Card - Contactless
TecSec PIV Eagle Card - Contactless, from TecSec, Atmel, CPI Card Group, and Athena Smartcard, holds FIPS 140-2 certificate #1118 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.
Caveat: None
Certificate
| Certificate number | 1118 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 3 |
| Module type | Hardware |
| Embodiment | Single-chip |
| Vendor | TecSec, Atmel, CPI Card Group, and Athena Smartcard · website |
| Software versions | P/N TecSec Contactless PIV Applet Version 1.0 JCL |
| Hardware versions | P/N Atmel AT90SC12872RCFT Revision M |
| Firmware versions | P/N Athena ID Protect Duo Version 0107.7099.0105 |
Module description
Quoted from the NIST CMVP entry for this certificate.
TecSec PIV Eagle Card - Contactless is a cryptographic module that may be configured as a contact or contactless PIV application. With this unique solution, a dual-chip product can be created without changing the user experience that assures the information stored on the contact chip is not compromised through the contactless interface. The CM is based on the Athena OS755 Java Card smart card operating system that is compliant with the latest Java Card 2.2.2 and GlobalPlatform 2.1.1 specifications and FIPS 140-2 Level 2 (Level 4 for physical security).
Security level exceptions
- Physical Security: Level 4
Approved algorithms (7)
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
| Date | Type | Lab |
|---|---|---|
| 2009-04-03 | Initial | UL Verification Services, Inc. |
| 2014-02-06 | Update |
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