Lexmark PrintCryption
Lexmark PrintCryption, from Lexmark International, Inc., holds FIPS 140-2 certificate #757 at overall level 1. 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 | 757 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Firmware |
| Embodiment | Multi-chip standalone |
| Vendor | Lexmark International, Inc. · website |
| Firmware versions | 1.3.1 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Lexmark PrintCryption Card is an option for the Lexmark T, C, W, and X series of output devices that enables the printing of host encrypted data. With this option installed, the printer is capable of decrypting print jobs encrypted with the AES algorithm. The Lexmark PrintCryption Card analyses the encrypted data stream, determines if the correct key was used to encrypt the data, decrypts the data and allows the confidential document to be printed.
Security level exceptions
- Tested: T640, T642, T644, C920, W840, C534, T630, T632, T634, C760, C762, C912, W820, X644e, X646e, X646dte, X850e, X852e, X854e, C772, C782, C935 and X945e
- Lexmark ver. 2.4 O/S
Approved algorithms (6)
| Algorithm | CAVP certificates |
|---|---|
| AES | 273, 274, 275, 276, 277, 452 |
| HMAC | 89, 90, 91, 92, 93, 215 |
| RNG | 100, 101, 102, 103, 104, 237 |
| RSA | 73, 74, 75, 76, 77, 171 |
| SHS | 350, 351, 352, 353, 354, 515 |
| Triple-DES | 356, 357, 358, 359, 360, 470 |
Other algorithms
RSA (key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2007-04-11 | Initial | COACT INC CAFE LAB |
| 2007-05-22 | 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: 2007-04-11, 2007-05-22