Lightware Crypto Core
Caveat: When operated in FIPS mode. No assurance of the minimum strength of generated keys
Certificate
| Certificate number | 4674 |
|---|---|
| Standard | FIPS 140-2 |
| Status | active |
| Sunset date | 2026-09-21 |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Lightware Visual Engineering Plc. · website |
| Software versions | 2.2.1 |
Module description
Lightware Crypto Core is a standards-based cryptographic engine for embedded Linux systems. The module delivers core cryptographic functions to the embedded systems of Taurus product family's hardware devices and features robust algorithm support. Lightware Crypto Core offloads functions for secure key management, data integrity, data at rest encryption, and secure communications to a trusted implementation.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | A2305 |
| CKG | vendor affirmed |
| DRBG | A2305 |
| DSA | A2305 |
| ECDSA | A2305 |
| HMAC | A2305 |
| RSA | A2305 |
| SHS | A2305 |
| Triple-DES | A2305 |
Tested configurations
- CentOS 7.9 running on a HPE ProLiant DL360 G7 with an Intel Xeon X5670 with PAA
- CentOS 7.9 running on a HPE ProLiant DL360 G7 with an Intel Xeon X5670 without PAA
- Free BSD 13.1 running on an XRI-400 with an Intel Atom E3940 with PAA
- Free BSD 13.1 running on an XRI-400 with an Intel Atom E3940 without PAA
- macOS 12 (Monterey) running on an Apple Mac Mini 9,1 with an Apple M1
- Windows Server 2012 R2 running on a Dell PowerEdge R420 with an Intel Xeon E5-2430 with PAA
- Windows Server 2012 R2 running on a Dell PowerEdge R420 with an Intel Xeon E5-2430 without PAA (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2024-01-26 | Initial | Leidos Accredited Testing & Evaluation (AT&E) Lab |
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 active
- Validation dates on record: 2024-01-26