Avaya G450/G430 FIPS 140-2 Cryptographic Module
Avaya G450/G430 FIPS 140-2 Cryptographic Module, from Avaya, Inc., holds FIPS 140-2 certificate #4635 at overall level 1. 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: When installed, initialized and configured as specified in Section 1.8 of the Security Policy. When operated in FIPS mode
Certificate
| Certificate number | 4635 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Hardware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Avaya, Inc. · website |
| Hardware versions | P/Ns 700506955, 700506955 with 700501368, 700512173 and 700512173 with 700503274 |
| Firmware versions | 41.34.5 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The G450 and G430 Media Gateways are complete branch office business communications systems that integrate TDM and VoIP telephony. Ideally suited for branch office locations of up to 450 extensions, the G450 and G430 replace the complexity and cost of managing disparate key and voice systems with a survivable networked solution that is easy to deploy and can be administered from a central location.
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms (13)
| Algorithm | CAVP certificates |
|---|---|
| AES | A2079, A2082, A2085 |
| CKG | vendor affirmed |
| CVL | vendor affirmed |
| DRBG | A2083 |
| ECDSA | A2084 |
| ENT | |
| HMAC | A2081, A2086 |
| KAS | |
| KAS-SSC | A2078 |
| KTS | |
| RSA | A2087 |
| SHS | A2080, A2088 |
| Triple-DES | A2074 |
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2023-10-11 | 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-11