3e-030-2 Security Server Cryptographic Core
3e-030-2 Security Server Cryptographic Core, from 3e Technologies International, Inc., holds FIPS 140-2 certificate #1563 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.
Certificate
| Certificate number | 1563 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-chip standalone |
| Vendor | 3e Technologies International, Inc. · website |
| Software versions | 4.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The 3e-030-2 Security Server Cryptographic Core (Version 4.0) provides FIPS 140-2 validated cryptographic functionality for the 3eTI Security Server product, a RADIUS based Authentication Server, capable of EAP-TLS authentication of wireless client, support of JITC DoD-signed certificates for PKI usage, and full 802.11i support. The 3e-030-2 provides the following FIPS-approved cryptographic algorithms: AES, SHA-1, SHA-2, HMAC, RSA DSA ECDSA sign/verify, FIPS 186-2 PRNG. The 3e-030-2 also supports the following non-FIPS cryptographic algorithms: Diffie Hellman, ECDH and MD5
Security level exceptions
- Roles, Services, and Authentication: Level 3
- Design Assurance: Level 3
Approved algorithms (8)
Other algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides between 128 and 192 bits of encryption strength); MD5
Tested configurations
- Red Hat Linux Enterprise 5.5 (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2011-06-20 | Initial | CYGNACOM SOLUTIONS 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: 2011-06-20