3e-520 Secure Access Point Cryptographic Module
3e-520 Secure Access Point Cryptographic Module, from 3e Technologies International, Inc., holds FIPS 140-2 certificate #1971 at overall level 2. 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: When installed, initialized and configured as specified in the Security Policy Section 3.1
Certificate
| Certificate number | 1971 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip embedded |
| Vendor | 3e Technologies International, Inc. · website |
| Hardware versions | 1.0 |
| Firmware versions | 5.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The 3e-520 Secure Access Point acts as an access point for the universal wireless family of devices from 3eTI. The 520 board is installed inside the wireless devices and provides the cryptographic functionality for the device. The access point allows for wireless clients or wireless bridges to securely connect wirelessly with the module and send encrypted data.
Security level exceptions
- Roles, Services, and Authentication: Level 3
- Design Assurance: Level 3
Approved algorithms (8)
| Algorithm | CAVP certificates |
|---|---|
| AES | 2060, 2078, 2105 |
| CVL | 22 |
| DRBG | 822 |
| ECDSA | 303 |
| HMAC | 1253, 1259 |
| KTS | |
| RSA | 1072 |
| SHS | 1801, 1807 |
Other algorithms
MD5; NDRNG; RSA (key wrapping, key establishment methodology provides 112 bits of encryption strength)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2013-07-03 | Initial | SAIC-VA |
| 2016-02-26 | Update | CYGNACOM SOLUTIONS INC |
| 2018-03-16 | Update | 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: 2013-07-03, 2016-02-26, 2018-03-16