Maxar AEDS
Maxar AEDS, from Maxar Technologies, holds FIPS 140-2 certificate #4649 at overall level 2. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.
Caveat: The tamper evident seals are installed as indicated in the Security Policy. This module contains the embedded module NPCT6XX TPM 2.0 validated to FIPS 140-2 under Cert. #2627 operating in FIPS mode.
Certificate
| Certificate number | 4649 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Maxar Technologies · website |
| Hardware versions | Revision 1 |
| Firmware versions | 1.0.6.1558.2958 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Maxar AEDS is a network based ground to spacecraft AES GCM & CTR mode encryption/decryption appliance hosted on a 1U network security server. It can support multiple channels simultaneously on up to 6 different subnets with speeds over 75 Mbit/s. There is a web based Crypto Operator interface for easy set-up and configuration. The User interfaces are TCP/IP socket based and follow a straightforward ICD. Both are protected with TLS 1.2.
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms (10)
| Algorithm | CAVP certificates |
|---|---|
| AES | A2061 |
| CKG | vendor affirmed |
| CVL | 2178, C585 |
| DRBG | A2061 |
| HMAC | A2061 |
| KAS | |
| KAS-SSC | A2062 |
| KTS | |
| RSA | A2061, A2090 |
| SHS | A2061 |
Allowed algorithms
RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength); NDRNG
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2023-10-27 | Initial | UL Verification Services, 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 at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2023-10-27