808bits

Brocade® G620 FC Switch

FIPS 140-2 certificate #3128 · Brocade Communications Systems, Inc. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with tamper evident seals installed as indicated in the Security Policy. When installed, initialized and configured as specified in Security Policy Section 3.1.3

Certificate

Certificate number3128
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorBrocade Communications Systems, Inc. · website
Hardware versions{BR-G620-48-32G-F Switch (P/N 80-1009066-02) with FRU (P/N 80-1009260-01) and POD License (P/N 80-1009038-01), BR-G620-48-32G-R Switch (P/N 80-1009067-02) with FRU (P/N 80-1009261-01) and POD License (P/N 80-1009038-01)} with FIPS Kit Brocade XBR-000195 (P/N 80-1002006-02)
Firmware versionsFabric OS v8.1.0 (P/N 63-1001736-01)

Module description

The Brocade® G620 switch provides a reliable, scalable Fibre Channel switching infrastructure with Gen 6 32 Gbps technology and capabilities that support demanding, enterprise-class private cloud storage and highly virtualized environments.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES4244
CVL993, 994, 995
DRBG1323
DSA1134
ECDSA984
HMAC2782
RSA2290
SHS3481

Allowed algorithms

Diffie-Hellman (CVL Cert. #993, key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #993 and #995, key agreement; key establishment methodology provides 128 bits of encryption strength); HMAC-MD5; MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2018-02-14InitialAEGISOLVE, 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: 2018-02-14

Source documents