808bits

G350 Branch Office Media Gateway w/FIPS

FIPS 140-2 certificate #519 · Avaya, Inc. · data as of 2026-10-21

G350 Branch Office Media Gateway w/FIPS, from Avaya, Inc., holds FIPS 140-2 certificate #519 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.

Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number519
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-chip standalone
VendorAvaya, Inc. · website
Hardware versionsP/N 700356249 Version 1.0
Firmware versions23.18.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Avaya G350 Branch Office Media Gateway is a complete branch office business communications system that integrates an IP telephony gateway, an advanced IP WAN router, and a high performance LAN switch into a compact (3U) modular chassis. Ideally suited for enterprise with distributed branch office locations of 8-40 extensions, the G350 replaces 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

  • Roles, Services, and Authentication: Level 2
  • Design Assurance: Level 3

Approved algorithms (6)

AlgorithmCAVP certificates
AES171
HMAC-SHA-1vendor affirmed
RNG21
RSA17
SHS256
Triple-DES273

Other algorithms

DES (Cert. #269); Diffie-Hellman (key agreement); MD5; H248 Link Encryption; Avaya Media Encryption; SSHv2

Validation history

DateTypeLab
2005-04-07InitialUL Verification Services, Inc.
2005-05-05Update

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: 2005-04-07, 2005-05-05

Source documents