13.07.2015 Views

Administration of the Avaya G350 Media Gateway - Avaya Support

Administration of the Avaya G350 Media Gateway - Avaya Support

Administration of the Avaya G350 Media Gateway - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 21: FIPSThis chapter provides information about (i) <strong>the</strong> <strong>G350</strong> cryptographic module’s compliance with<strong>the</strong> Federal Information Processing Standard (FIPS-140-2) for cryptographic modules, and(ii) how to configure <strong>the</strong> module to work in FIPS mode. This chapter includes <strong>the</strong> followingsections:●●●●●Overview — an overview <strong>of</strong> <strong>the</strong> <strong>G350</strong> (relating to FIPS compliance)Security rules — <strong>the</strong> security rules enforced by <strong>the</strong> cryptographic module to implement <strong>the</strong>security requirements <strong>of</strong> FIPSPassword guidelines — <strong>the</strong> general guidelines for defining passwordsManaging <strong>the</strong> module in FIPS-compliant mode — a description <strong>of</strong> <strong>the</strong> behavior <strong>of</strong> <strong>the</strong>module working in FIPS-approved mode <strong>of</strong> operation<strong>Administration</strong> procedures — step-by-step instructions on how to enter FIPS mode, failurescenarios, repair actions, and error statesOverviewThe <strong>G350</strong> device is a multi-chip stand-alone cryptographic module in a commercial grade metalcase. The module provides:●●●●VPN, Voice over Internet Protocol (VoIP) media-gateway services, E<strong>the</strong>rnet switching, IProuting, and data security for IP trafficStatus output via LEDs and logs available through <strong>the</strong> module’s management interfaceNetwork interfaces for data input and outputA console portThe cryptographic boundary includes all <strong>of</strong> <strong>the</strong> components within <strong>the</strong> physical enclosure <strong>of</strong> <strong>the</strong><strong>G350</strong> chassis, without any expansion modules. Figure 26 illustrates <strong>the</strong>se interfaces anddefines <strong>the</strong> cryptographic boundary.Issue 3 January 2005 289

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!