53-1003145-02

13 February 2015

Fabric OS FIPS and

Common Criteria
Configuration Guide

Supporting Fabric OS 7.3.0 for FIPS and 7.3.0a1 for Common Criteria
© 2015, Brocade Communications Systems, Inc. All Rights Reserved.

ADX, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, HyperEdge, ICX, MLX, MyBrocade, OpenScript, The Effortless
Network, VCS, VDX, Vplane, and Vyatta are registered trademarks, and Fabric Vision and vADX are trademarks of Brocade
Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be
trademarks of others.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any
equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document
at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be
currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in
this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to the
accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the computer programs that
accompany it.
The product described by this document may contain open source software covered by the GNU General Public License or other open
source license agreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to
the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.
Contents

Preface..................................................................................................................................... 5
Document conventions......................................................................................5
Text formatting conventions.................................................................. 5
Command syntax conventions.............................................................. 5
Notes, cautions, and warnings.............................................................. 6
Brocade resources............................................................................................ 7
Contacting Brocade Technical Support.............................................................7
Document feedback.......................................................................................... 8

About this document................................................................................................................. 9

Supported hardware and software.................................................................... 9
What's new in this document.............................................................................9

Overview of FIPS......................................................................................................................11
FIPS overview................................................................................................. 11
Public and private key management for FIPS compliance .................11
Firmware upgrade and downgrade considerations......................................... 12
FIPS mode firmware upgrade and downgrade considerations........... 12
Non-FIPS mode firmware upgrade and downgrade considerations... 13
Firmware downloading considerations............................................................13

Zeroization Functions..............................................................................................................15
Overview of zeroization ..................................................................................15
Restrictions on zeroization.................................................................. 15
Zeroization functions described ..................................................................... 15
Zeroizing a switch for FIPS............................................................................. 17

FIPS Configuration..................................................................................................................19
Overview of FIPS mode configuration.............................................................19
Displaying the FIPS configuration................................................................... 19
Fabric OS feature behaviors in FIPS and non-FIPS mode ............................ 19
LDAP functionality in FIPS mode.................................................................... 21
Setting up LDAP for FIPS mode......................................................... 22
LDAP CA certificates and FIPS mode ................................................23
Importing an LDAP CA certificate....................................................... 23
Exporting an LDAP CA certificate....................................................... 24
Deleting an LDAP CA certificate......................................................... 24

FIPS Switch Preparation..........................................................................................................25

Overview of preparing a switch for FIPS.........................................................25
Enabling FIPS mode....................................................................................... 25
Notes on enabling FIPS mode ........................................................... 30
Power-on self-tests......................................................................................... 30
Power-on firmware checksum test...................................................... 30
Conditional tests..............................................................................................31

Fabric OS FIPS and Common Criteria Configuration Guide 3

53-1003145-02
 Common Criteria Certification............................................................................................... 33
Overview....................................................................................................... 33
TOE network interface.................................................................................. 33
TOE firmware update....................................................................................34
Firmware Download:......................................................................... 34
Configuring the FOS switch for Common Criteria......................................... 35
Cryptographic Configurations in Common Criteria........................................36
Self tests....................................................................................................... 37
Commands supported in Common Criteria...................................................38
Audit messages.............................................................................................38

4 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
Preface

● Document conventions......................................................................................................5
● Brocade resources............................................................................................................ 7
● Contacting Brocade Technical Support.............................................................................7
● Document feedback.......................................................................................................... 8

Document conventions
The document conventions describe text formatting conventions, command syntax conventions, and
important notice formats used in Brocade technical documentation.

Text formatting conventions

Text formatting conventions such as boldface, italic, or Courier font may be used in the flow of the text
to highlight specific words or phrases.

Format Description
bold text Identifies command names
Identifies keywords and operands
Identifies the names of user-manipulated GUI elements
Identifies text to enter at the GUI

italic text Identifies emphasis

Identifies variables
Identifies document titles

Courier font Identifies CLI output

Identifies command syntax examples

Command syntax conventions

Bold and italic text identify command syntax components. Delimiters and operators define groupings of
parameters and their logical relationships.

Convention Description
bold text Identifies command names, keywords, and command options.
italic text Identifies a variable.
value In Fibre Channel products, a fixed value provided as input to a command
option is printed in plain text, for example, --show WWN.

Fabric OS FIPS and Common Criteria Configuration Guide 5

53-1003145-02
Notes, cautions, and warnings

Convention Description

[] Syntax components displayed within square brackets are optional.

Default responses to system prompts are enclosed in square brackets.

{x|y|z} A choice of required parameters is enclosed in curly brackets separated by

vertical bars. You must select one of the options.
In Fibre Channel products, square brackets may be used instead for this
purpose.

x|y A vertical bar separates mutually exclusive elements.

<> Nonprinting characters, for example, passwords, are enclosed in angle

brackets.

... Repeat the previous element, for example, member[member...].

\ Indicates a “soft” line break in command examples. If a backslash separates

two lines of a command input, enter the entire command at the prompt without
the backslash.

Notes, cautions, and warnings

Notes, cautions, and warning statements may be used in this document. They are listed in the order of
increasing severity of potential hazards.

NOTE
A Note provides a tip, guidance, or advice, emphasizes important information, or provides a reference
to related information.

ATTENTION
An Attention statement indicates a stronger note, for example, to alert you when traffic might be
interrupted or the device might reboot.

CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or cause
damage to hardware, firmware, software, or data.

DANGER
A Danger statement indicates conditions or situations that can be potentially lethal or
extremely hazardous to you. Safety labels are also attached directly to products to warn of
these conditions or situations.

6 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 Brocade resources

Brocade resources
Visit the Brocade website to locate related documentation for your product and additional Brocade
resources.

You can download additional publications supporting your product at www.brocade.com. Select the
Brocade Products tab to locate your product, then click the Brocade product name or image to open the
individual product page. The user manuals are available in the resources module at the bottom of the
page under the Documentation category.

To get up-to-the-minute information on Brocade products and resources, go to MyBrocade. You can
register at no cost to obtain a user ID and password.
Release notes are available on MyBrocade under Product Downloads.
White papers, online demonstrations, and data sheets are available through the Brocade website.

Contacting Brocade Technical Support

As a Brocade customer, you can contact Brocade Technical Support 24x7 online, by telephone, or by e-
mail. Brocade OEM customers contact their OEM/Solutions provider.

Brocade customers
For product support information and the latest information on contacting the Technical Assistance
Center, go to http://www.brocade.com/services-support/index.html.
If you have purchased Brocade product support directly from Brocade, use one of the following methods
to contact the Brocade Technical Assistance Center 24x7.

Online Telephone E-mail

Preferred method of contact for non- Required for Sev 1-Critical and Sev [email protected]
urgent issues: 2-High issues:
Please include:
• My Cases through MyBrocade • Continental US: 1-800-752-8061
• Problem summary
• Software downloads and licensing • Europe, Middle East, Africa, and
• Serial number
tools Asia Pacific: +800-AT FIBREE
(+800 28 34 27 33) • Installation details
• Knowledge Base
• For areas unable to access toll • Environment description
free number: +1-408-333-6061
• Toll-free numbers are available in
many countries.

Brocade OEM customers

If you have purchased Brocade product support from a Brocade OEM/Solution Provider, contact your
OEM/Solution Provider for all of your product support needs.
• OEM/Solution Providers are trained and certified by Brocade to support Brocade® products.
• Brocade provides backline support for issues that cannot be resolved by the OEM/Solution Provider.

Fabric OS FIPS and Common Criteria Configuration Guide 7

53-1003145-02
Document feedback

• Brocade Supplemental Support augments your existing OEM support contract, providing direct
access to Brocade expertise. For more information, contact Brocade or your OEM.
• For questions regarding service levels and response times, contact your OEM/Solution Provider.

Document feedback
To send feedback and report errors in the documentation you can use the feedback form posted with
the document or you can e-mail the documentation team.
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a topic
needs further development, we want to hear from you. You can provide feedback in two ways:
• Through the online feedback form in the HTML documents posted on www.brocade.com.
• By sending your feedback to [email protected].
Provide the publication title, part number, and as much detail as possible, including the topic heading
and page number if applicable, as well as your suggestions for improvement.

8 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
About this document

● Supported hardware and software.................................................................................... 9

● What's new in this document.............................................................................................9

Supported hardware and software

Brocade recommends to confirm if the Fabric OS device and the software version is FIPS and Common
Criteria certified.
To determine if the Fabric OS device and current software version is FIPS certified, refer to http://
csrc.nist.gov/groups/STM/cmvp/validation.html.
To determine if the Fabric OS device and current software version is Common Criteria certified, refer to
https://www.niap-ccevs.org/CCEVS_Products/pcl.cfm.

What's new in this document

The following items are new or revised in this version of the Fabric OS FIPS and Common Criteria
Configuration Guide:
• Added Common Criteria information.

Fabric OS FIPS and Common Criteria Configuration Guide 9

53-1003145-02
What's new in this document

10 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
Overview of FIPS

● FIPS overview................................................................................................................. 11
● Firmware upgrade and downgrade considerations......................................................... 12
● Firmware downloading considerations............................................................................13

FIPS overview
The Federal Information Processing Standards (FIPS) are a set of U.S. Federal government standards
which describe information technology practices and requirements (including document processing,
encryption algorithms and device access restrictions) for use within non-military government agencies
and by government contractors and vendors who work with those agencies.
Fabric OS 6.0.0 and later provided the capability to configure a switch to be FIPS-compliant. This guide
describes how to prepare and configure a switch for FIPS using Fabric OS 7.3.0. In this guide, “FIPS
mode” identifies a switch that is configured and operating in compliance with the FIPS standards.

NOTE
This guide also contains instructions on how to configure a Brocade FOS switch to Common Criteria
standards. Configuration instructions for Common Criteria and FIPS are mutually exclusive. Please
refer to the Common Criteria Certification on page 33 for details on how configure the Brocade FOS
switch to Common Criteria standards.

ATTENTION
When it is enabled, FIPS mode is a chassis-wide setting that affects all logical switches. Once enabled,
FIPS mode cannot be disabled.

Public and private key management for FIPS compliance

To provide Federal Information Processing Standards (FIPS) support, Fabric OS 7.3.0 firmware is
digitally signed using the OpenSSL utility (version 1.0.1e which contains the patch for the “Heartbleed”
vulnerability (CVE-2014-0160)). To use this digitally signed software, you must configure the switch to
enable signed firmware download. If it is not enabled, the firmware download process ignores the
firmware signature and performs as before.
For signed firmware that supports FIPS, Brocade requires RSA authentication using 2048-bit length
private-public key pairs. The private key with the SHA256 digest is used to sign the firmware files when
the firmware is generated. The public key is packaged in an RPM package as part of the firmware, and
is downloaded to the switch. After it is downloaded, it can be used to validate the firmware to be
downloaded next time when you run the firmwareDownload command.
The public key file on the switch contains only one public key. It is only able to validate firmware signed
using one corresponding private key. If the private key changes in future releases, you must change the
public key on the switch by using the firmwareDownload command. When a new firmware is
downloaded, firmware download always replaces the public key file on the switch with what is in the
new firmware. This allows you to have planned firmware key changes.

Fabric OS FIPS and Common Criteria Configuration Guide 11

53-1003145-02
Firmware upgrade and downgrade considerations

Firmware upgrade and downgrade considerations

The following firmware upgrade and downgrade restrictions must be taken into consideration.

NOTE
Brocade recommends that firmware upgrade/downgrade for switches in FIPS mode should only be
done between FIPS-certified versions of Brocade Fabric OS. Currently these are releases 7.1.0, 7.2.1,
and 7.3.0.

FIPS mode firmware upgrade and downgrade considerations

When upgrading to Fabric OS 7.3.0:
• The firmware is signed with RSA 2048-bit keys using SHA-256 hash encryption. Upgrades will only
accept RSA 2048-bit signature keys.
• Upgrading to Fabric OS 7.3.0 in FIPS mode is supported only from Fabric OS 7.2.0 or later. It is not
possible to upgrade directly from Fabric OS 7.0.x or Fabric OS 7.1.x to Fabric OS 7.3.0 in FIPS
mode, as those versions do not have RSA 2048-bit signature keys. To upgrade from these versions
in FIPS mode, you must perform a progressive upgrade from these earlier versions to version 7.2.x
before you can upgrade to Fabric OS 7.3.0.
• For Fabric OS 7.3.0 to be in compliance with FIPS regulations, all required configurations cannot be
made before the firmware is upgraded. Some configurations can only be made after the upgrade.
To be in compliance, the following tasks must be followed to ensure a nondisruptive upgrade.
• Configuration prerequisites
‐ Parameters required for SP800-131A compliance for SSH sessions will be enforced. Thus,
to connect to the switch after an upgrade, the SSH client must:
‐ Support signature generation and verification with SHA-256 encryption.
‐ Support diffie-hellman-group-exchange-sha256 (OpenSSH 5.4 and later).
‐ Support host key authentication with ecdsa-sha2-nistp256.
‐ The SSH server must:
‐ Provide a 2048-bit RSA Host key size.
‐ Support signature generation and verification with SHA-256.
‐ Support diffie-hellman-group-exchange-256, ecdh-sha2-nistp256, ecdh-sha2-
nistp384, and ecdh-sha2-nistp521.
‐ To support logging in without a password, 2048-bit RSA or 256-bit ECDSA public keys
must be imported for users.
‐ Before upgrading, you must import the switch certificates generated with RSA 2048-bit
keys using SHA-256.
• If you are upgrading to Fabric OS 7.2.x, the following configuration changes must be made. (These
are not required when upgrading from 7.2.x to 7.3.0 in FIPS mode.):
‐ Group type and encryption hash type must be changed to group 4 and SHA-256 for fabric
authentication.
‐ FCAP certificates, if used, must be generated with RSA 2048-bit keys using SHA-256
encryption, and imported on both the peers.
‐ Reinitiate authentication by entering either authutil-authinit port_number to authenticate
the specified port, or authutil -authinit all to authenticate all ports on the switch.

12 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 Non-FIPS mode firmware upgrade and downgrade considerations

NOTE
Once you have upgraded the switch firmware to Fabric OS 7.3.0, if you want to use SHA1-based
signature generation and verification for SSH connections, you can disable the SHA-256 encryption by,
entering fipscfg -disable sha256. This is not recommended.

ATTENTION
A switch is considered to be in FIPS mode only if the output of fipscfg -verify fips lists the compliance
of all parameters as PASS. It is considered to be FIPS-compliant only if all parameters are passed and
the anti-tampering labels are correctly applied to the switch body.

Non-FIPS mode firmware upgrade and downgrade considerations

In non-FIPS mode, firmware upgrades and downgrades are supported for the previous two versions of
firmware signature keys. The following table lists the possible firmware upgrades and downgrades if you
are not in FIPS mode.

TABLE 1 Possible firmware upgrades and downgrades in non-FIPS mode

If you are running You can upgrade directly to You can downgrade directly to

7.0.x 7.1.x, 7.2.x --

7.1.x 7.2.x, 7.3.x 7.0.x

7.2.x 7.3.x 7.1.x, 7.0.x

7.3.x -- 7.1.x, 7.2.x

Refer to the Fabric OS Administrator's Guide for more information on upgrading or downgrading your
firmware.

Firmware downloading considerations

When downloading updated firmware, the following items should be taken into consideration:
• The public key file must be packaged, installed, and run on your switch before you download a
signed firmware.
• When the download installs a firmware file, it validates the signature of the file. Different scenarios
are handled as follows:
‐ If the firmware file has a signature and the validation succeeds, the firmware download
proceeds normally.
‐ If the firmware file has a signature, but the validation fails, the firmware download will fail.
This usually means that the firmware is not from Brocade, or the contents of the firmware
file have been modified.
‐ If a firmware file does not have a signature, how the file is handled depends on the
signed_firmware parameter on the switch.
‐ If the signed_firmware parameter is enabled, the firmware download will fail.
‐ If the signed_firmware parameter is not enabled, the firmware download process
displays a warning message and then continues. When downgrading to non-FIPS-
compliant firmware, the “signed_firmware” flag must be disabled.

Fabric OS FIPS and Common Criteria Configuration Guide 13

53-1003145-02
Overview of FIPS

NOTE
SAS, DMM, and other third-party application images are not signed.

14 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
Zeroization Functions

● Overview of zeroization ..................................................................................................15

● Zeroization functions described ..................................................................................... 15
● Zeroizing a switch for FIPS............................................................................................. 17

Overview of zeroization
Zeroization is a method of erasing electronically stored data, cryptographic keys, and critical security
parameters (CSPs) by altering or deleting the contents of the data storage to prevent recovery of the
data. Zeroization erases all potentially sensitive information in the switch memory. This includes erasing
the main memory, cache memories, and any memory locations that may contain security data, including
NVRAM and flash memory.

Restrictions on zeroization
• Zeroization parameters cannot be configured.
• Zeroization can only be invoked through the command line interface (CLI).
• Zeroization should only be performed by a local operator who has physical control of the
cryptographic module, with all network connections physically disconnected.

Zeroization functions described

Zeroization functions can be performed at the discretion of the security administrator. These functions
clear the passwords and the shared secrets. Core files and first failure data capture (FFDC) data are
also removed upon FIPS zeroization.

The following table lists the various keys used in the system that will be zeroized in a FIPS-compliant
Fabric OS module. Zeroization for individual keys can be invoked by specific commands, but zeroization
using the fipsCfg command is not configurable.

TABLE 2 Zeroization behavior

Keys Zeroization CLI Description

DH private keys No command required Keys will be zeroized within code before they are released from
memory.

FCAP private key secCertUtil delete -- Removes all FCAP certificates and FCAP private keys.
fcapall -nowarn

Fabric OS FIPS and Common Criteria Configuration Guide 15

53-1003145-02
Zeroization Functions

TABLE 2 Zeroization behavior (Continued)

Keys Zeroization CLI Description

FCSP Challenge secAuthSecret -- The secAuthSecret --create command is used to input the keys,
Handshake remove and the secAuthSecret --remove command is used to remove
Authentication and zeroize the keys. All the DH-CHAP and FCAP authenticated
Protocol (CHAP) ports are disabled after zeroization.
Secret

LDAP CA certificate secCertUtil delete – The given LDAP certificate file is zeroized and deleted from the
ldapcacert certname module.

Passwords passwdDefault The passwdDefault command removes user-defined accounts

and restores the default passwords for the default root, admin, and
user accounts. However, only the root account has permissions for
this command. Users with securityadmin and admin permissions
must use fipsCfg --zeroize, which, in addition to removing user
accounts and resetting passwords, also performs the complete
zeroization of the system.

NOTE
In a dual-CP system, executing the passwdDefault command in
the active CP synchronizes passwords with the standby CP. This
causes user-defined accounts to be removed from both the active
and standby CPs and only the default accounts (root, factory,
admin, and user) are retained. The passwords for these accounts
are then set to the factory defaults.

ATTENTION
To maintain FIPS 140-2 compliance, passwords for the default
accounts (admin and user) must be changed after every
zeroization operation.

RADIUS secret aaaConfig –-remove The aaaConfig --remove command zeroizes the secret and
deletes a configured server. The aaaConfig --add command
configures the RADIUS server.

RNG seed key No command required The /dev/urandom function is used as the initial source of seed for
RNG. The RNG seed key is zeroized on every random number
generation.

SFTP session keys No command required Automatically zeroized on session termination.

SSH RSA private No command required To support passwordless login to the switch.
key

SSH ECDSA private sshUtil delprivkey To support ECDSA Key based passwordless SSH login.
Key

SSH public keys sshUtil delpubkeys Zeroizes the SSH public.

16 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 Zeroizing a switch for FIPS

TABLE 2 Zeroization behavior (Continued)

Keys Zeroization CLI Description

SSH session key No command required This key is generated for each SSH session that is established with
the host. It automatically zeroizes on session termination.

ECDSA K random No command required Used for a session and zeroized after each session.
value

TLS authentication No command required Automatically zeroized on session termination.

key

TLS pre-master No command required Automatically zeroized on session termination.

secret

TLS private keys secCertUtil delkey -all The secCertUtil delkey -all command is used to zeroize these
keys. The secCertUtil genkey command creates the keys. Only
2048-bit RSA keys are allowed in FIPS mode.

TLS session key No command required Automatically zeroized on session termination.

Zeroizing a switch for FIPS

To zeroize a switch for FIPS, complete the following steps.
1. Log in to the switch using either an account with admin or securityadmin permissions, or a user
account with OM permissions for the FIPSCfg RBAC class of commands.
2. Enter fipsCfg --zeroize.

NOTE
The passwords for the default accounts (admin and user) should be changed after every zeroization
operation to maintain FIPS 140-2 compliance.
3. Power-cycle the switch.

Fabric OS FIPS and Common Criteria Configuration Guide 17

53-1003145-02
Zeroizing a switch for FIPS

18 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
FIPS Configuration

● Overview of FIPS mode configuration.............................................................................19

● Displaying the FIPS configuration................................................................................... 19
● Fabric OS feature behaviors in FIPS and non-FIPS mode ............................................ 19
● LDAP functionality in FIPS mode.................................................................................... 21

Overview of FIPS mode configuration

By default, a switch comes up in non-FIPS mode. You can run the fipsCfg --enable fips command to
enable FIPS mode, but you must configure the switch first. Self-test mode must be enabled before FIPS
mode can be enabled. A set of prerequisites (as shown in Table 3 on page 20) must be satisfied for
the system to enter FIPS mode. To be FIPS-compliant, the switch must be power-cycled. Known
Answer Tests (KATs) are run on the reboot. If the KATs are successful, the switch enters FIPS mode. If
the KATs fail, then the switch reboots. If the switch cannot enter FIPS mode and continues to reboot,
you must return the switch to your switch service provider. For information about how to prepare a
service provider case, refer to the Fabric OS Troubleshooting and Diagnostics Guide. When the switch
successfully reboots in FIPS mode, only FIPS-compliant algorithms are run. For SSH sessions with
RSA host key authentication, SHA-256 will be disabled and can be enabled using the fipsCfg
command.

NOTE
Remote Procedure Calls (RPC) are not supported in FIPS mode.

Displaying the FIPS configuration

To display the FIPS configuration (including the SHA-256 and DH modes) for a switch, complete the
following steps.
1. Log in to the switch using an account with admin or securityadmin permissions, or a user account
with OM permissions for the fipsCfg RBAC class of commands.
2. Enter fipsCfg --showall.

Fabric OS feature behaviors in FIPS and non-FIPS mode

Table 3 lists Fabric OS features and their behaviors in FIPS and non-FIPS mode.

Fabric OS FIPS and Common Criteria Configuration Guide 19

53-1003145-02
FIPS Configuration

TABLE 3 Feature behaviors in FIPS mode

Features FIPS mode Non-FIPS mode

Authentication All ports, including Access Gateway, FC router, No restrictions

and F_Ports (except F_ports with SHA-256),
adhere to FIPS guidelines when authentication is
enabled.

configUpload, SCP only FTP and SCP

configDownload, supportSave,
and firmwaredownload

DH-CHAP and FCAP hashing SHA-256 with group 4 MD5 and SHA-1
algorithms
The FCAP certificate must be 2048 bits

DH-CHAP Shared Secret Minimum length of 32 bytes for secret Minimum length of 8 bytes
for secret

FCAP certificate 2048-bits keys signed with SHA-256. (Refer to No restrictions

Note following table.)

FC-FC routing If FIPS is enabled in an FC router and disabled in No restrictions

an edge switch, the EX_Port on the FC router is
disabled if the edge fabric switch has Diffie-
Hellman groups 4 and hash group SHA-256.
FCR will report that SHA1 is enforced by the edge,
onto a FCR router in FIPS mode.

HTTP and HTTPS access HTTPS only (Refer to Note following table.) HTTP and HTTPS

HTTPS algorithms TDES, AES-128, AES-192 and AES-256 TDES, AES-128,

AES-192 and AES-256

In-flight encryption Not supported No restrictions

Internet Protocol security (IPsec) Usage of AES-XCBC, MD5, and Diffie-Hellman No restrictions
group 1 are blocked. IPsec is not allowed in FIPS
mode.

LDAP CA CA certificate with public key size of 2048 bits and CA certificate is optional
signed with SHA-256 must be available. (Refer to
Note following table.)

Common certificate for FCAP Common Certificate is not supported in FIPS Supported
and HTTPS authentication mode; the FCAP certificate must be 2048 bits.
(Refer to Note following table.)

RADIUS authorization protocols PEAP-MSCHAPv2 CHAP, PAP, and PEAP-

MSCHAPv2

Root account Disabled Enabled

Factory account Disabled Enabled

20 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 LDAP functionality in FIPS mode

TABLE 3 Feature behaviors in FIPS mode (Continued)

Features FIPS mode Non-FIPS mode

Signed firmware download Mandatory firmware signature validation (SCP Optional firmware
only) signature validation (FTP
and SCP)
RSA 2048-bit keys only.

SNMP Read-only operations Read and write operations

SSH algorithms SHA-256 with Diffie-Hellman for RSA and ECDSA No restrictions
pCurve with SHA-256
HMAC-SHA1, HMAC-SHA2-256, HMAC-
SHA2-512
3DES-CBC, AES128-CBC, AES192-CBC, and
AES256-CBC cipher suites

SSH public keys RSA 2048-bit keys with SHA-256, AES-128, and RSA 1024-bit keys, RSA
ECDSA public key with SHA-256 2048-bit keys, and DSA
1024-bit keys

TACACS+ authentication Not supported Supported

Telnet and SSH access Only SSH Telnet and SSH

NOTE
Lower security certificates can be imported, but during the import you will have to confirm that you want
to use such a certificate to continue. This restriction applies to the CA, HTTPS, LDAP, and FCAP
features. This option is provided to support downgrade.

LDAP functionality in FIPS mode

You can configure your Microsoft Active Directory server to use the Lightweight Directory Access
Protocol (LDAP) while in FIPS mode. There is no option provided on the switch to configure Transport
Layer Security (TLS) ciphers for LDAP in FIPS mode. However, the LDAP client checks if FIPS mode is
set on the switch and uses the FIPS-compliant TLS ciphers for LDAP. If FIPS mode is not set and the
Microsoft Active Directory server is configured for FIPS ciphers, the AD server uses the FIPS-compliant
ciphers.
Table 4 lists the differences between FIPS and non-FIPS modes of operation.

TABLE 4 FIPS and non-FIPS modes of operation

FIPS mode Non-FIPS mode

The certificate of the CA that issued the Microsoft There is no mandatory CA certificate installation on the
Active Directory server certificate must be installed switch.
on the switch.

Fabric OS FIPS and Common Criteria Configuration Guide 21

53-1003145-02
Setting up LDAP for FIPS mode

TABLE 4 FIPS and non-FIPS modes of operation (Continued)

FIPS mode Non-FIPS mode

Configure FIPS-compliant TLS ciphers [TDES-168, On the Microsoft Active Directory server, there is no
AES-128, AES-256, SHA-1, and RSA-2048] on the configuration of the FIPS-compliant TLS ciphers.
Microsoft Active Directory server. The host needs
a reboot for the changes to take effect.

The switch uses FIPS-compliant ciphers The Microsoft Active Directory server certificate is validated if
regardless of the Microsoft Active Directory server the CA certificate is found on the switch.
configuration. If the Microsoft Active Directory
server is not configured for FIPS ciphers,
authentication will still succeed.

The Microsoft Active Directory server certificate is If the Microsoft Active Directory server is configured for FIPS
validated by the LDAP client. If the CA certificate is ciphers and the switch is in non-FIPS mode, then user
not present on the switch, then user authentication authentication will succeed.
will fail.

Setting up LDAP for FIPS mode

To set up LDAP for FIPS mode on a switch, complete the following steps.
1. Log in to the switch using an account with admin or securityadmin permissions, or an account with
OM permissions for the RADIUS and switch configuration RBAC classes of commands.
2. Enter dnsConfig to configure the Domain Name Service (DNS) on the switch. The following
example shows how to set the DNS address.
switch:admin> dnsconfig

Enter option
1 Display Domain Name Service (DNS) configuration
2 Set DNS configuration
3 Remove DNS configuration
4 Quit
Select an item: (1..4) [4] 2
Enter Domain Name: [] domain.com
Enter Name Server IP address in dot notation: [] 123.123.123.123
Enter Name Server IP address in dot notation: [] 123.123.123.124
DNS parameters saved successfully
Enter option
1 Display Domain Name Service (DNS) configuration
2 Set DNS configuration
3 Remove DNS configuration
4 Quit
Select an item: (1..4) [4] 4

Specify the DNS IP address using either IPv4 or IPv6. This address is needed for the switch to
resolve the domain name to the IP address because LDAP initiates a TCP session to connect to
your Microsoft Active Directory server. A Fully Qualified Domain Name (FQDN) is needed to
validate the server identity as mentioned in the common name of the server certificate.
3. Set the switch authentication mode and add your LDAP server by using the commands shown in
the following example. Provide the Fully Qualified Domain Name (FQDN) of the Microsoft Active
Directory server for the host name parameter while configuring LDAP.
The following example sets up LDAP for FIPS mode.
switch:admin> aaaconfig --add GEOFF5.ADLDAP.LOCAL -conf ldap -d adldap.local -p
389 -t 3
switch:admin> aaaconfig --authspec "ldap;local"
switch:admin> aaaconfig -show
RADIUS CONFIGURATIONS
=====================
RADIUS configuration does not exist.
LDAP CONFIGURATIONS

22 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 LDAP CA certificates and FIPS mode

===================
Position : 1
Server : GEOFF5.ADLDAP.LOCAL
Port : 389
Domain : adldap.local
Timeout(s) : 3
Primary AAA Service: LDAP
Secondary AAA Service: Switch database
4. Set up LDAP according to the instructions in “LDAP configuration and Microsoft Active Directory” in
the Fabric OS Administrator's Guide, and then configure the following additional Microsoft Active
Directory settings.
a) To support FIPS-compliant TLS cipher suites on the Microsoft Active Directory server, allow
the SCHANNEL settings listed in Table 5 .
TABLE 5 Active Directory keys to modify

Key Sub-key

Ciphers 3DES

Hashes SHA1

SHA-256 key PKCS

exchange algorithm

Protocols TLSv1.0

b) Enable the FIPS algorithm policy on the Microsoft Active Directory server.

LDAP CA certificates and FIPS mode

To utilize the LDAP services for FIPS between the switch and the host, you must generate a certificate
signing request (CSR) on the Microsoft Active Directory server and import and export the CA
certificates. To support server certificate validation, it is essential to have the CA certificate installed on
the switch and Microsoft Active Directory server. Use the secCertUtil command to import the CA
certificate to the switch. This command will prompt for the remote IP and login credentials to retrieve the
CA certificate. The CA certificate should be in any of the standard certificate formats: “.cer”, “.crt”, or
“.pem”.

LDAP CA certificate restrictions

The following restrictions apply to LDAP CA certificates when used with FIPS:
• LDAP CA certificates must use RSA 2048-bit keys using SHA-256 encryption.
• If you want to use the secCertUtil command to import and export certificates, LDAP CA certificate
file names should not contain spaces.

Importing an LDAP CA certificate

To import the LDAP CA certificate from the remote host to the switch, complete the following steps.
1. Connect to the switch and log in using an account with admin permissions, or an account with OM
permissions for the PKI RBAC class of commands.
2. Enter secCertUtil import -ldapcacert.

Fabric OS FIPS and Common Criteria Configuration Guide 23

53-1003145-02
Exporting an LDAP CA certificate

The following example imports an LDAP CA certificate.

switch:admin> seccertutil import -ldapcacert
Select protocol [ftp or scp]: scp
Enter IP address: 192.168.38.206
Enter remote directory: /users/aUser/certs
Enter certificate name (must have ".crt" or ".cer" ".pem" suffix): LDAPTestCa.cer
Enter Login Name: aUser
Password: <hidden>
Success: imported certificate [LDAPTestCa.cer].

Exporting an LDAP CA certificate

To export the LDAP CA certificate from the switch to the remote host, complete the following steps.
1. Connect to the switch and log in using an account with admin permissions, or an account with OM
permissions for the PKI RBAC class of commands.
2. Enter secCertUtil export -ldapcacert.
The following example exports an LDAP CA certificate.
switch:admin> seccertutil export -ldapcacert

Select protocol [ftp or scp]: scp

Enter IP address: 192.168.38.206
Enter remote directory: /users/aUser/certs
Enter Login Name: aUser
Enter LDAP certificate name (must have ".pem" suffix): swLdapca.pem
Password: <hidden>
Success: exported LDAP certificate

Deleting an LDAP CA certificate

To delete the LDAP CA certificate from the switch, complete the following steps.
1. Connect to the switch and log in using an account with admin permissions, or an account with OM
permissions for the PKI RBAC class of commands.
2. Enter secCertUtil show --ldapcacert to determine the name of the LDAP CA certificate file.
3. Enter secCertUtil delete --ldapcacert , specifying the file name of the LDAP CA certificate on the
switch.
The following example deletes an LDAP CA certificate.
device:admin> seccertutil delete -ldapcacert swLdapca.pem

WARNING!!!
About to delete certificate: swLdapca.pem
ARE YOU SURE (yes, y, no, n): [no] y
Deleted LDAP certificate successfully

24 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
FIPS Switch Preparation

● Overview of preparing a switch for FIPS.........................................................................25

● Enabling FIPS mode....................................................................................................... 25
● Power-on self-tests......................................................................................................... 30
● Conditional tests..............................................................................................................31

Overview of preparing a switch for FIPS

It is important to prepare a switch for the following restrictions that exist in FIPS mode:
• The root account, factory account, and all root-only functions are not available.
• HTTP, Telnet, and SNMP must be disabled. Once these ports are blocked, you cannot use them to
read or write data from and to the switch.
• The configDownload and firmwareDownload commands using an FTP server are blocked.
• All pre-requisite configurations mentioned in Overview of preparing a switch for FIPS must be
completed.
• You must manually disable password distribution on switches running FIPS on Fabric OS 7.3.0
before configuring FIPS. This procedure is described as part of Enabling FIPS mode on page 25.
Refer to Table 3 on page 20 for a complete list of FIPS and non-FIPS mode feature restrictions.

Enabling FIPS mode

ATTENTION
You need both securityadmin and admin permissions to enable FIPS mode.

To enable FIPS mode on a Brocade Fabric OS device, complete the following steps.
1. Connect to the device and log in using an account with admin permissions.
2. Disable password distribution for the switch by completing the following steps.
a) Enter fddcfg --localreject PWD. PWD is the name of the password database
b) Optional: Enter fddcfg --show to confirm that password distribution has been disabled on
this switch.
The following example illustrates this set of commands. The changed setting is called out for
illustrative purposes.
device:admin> fddcfg --localreject PWD
Local Switch Configured to reject policies.

device:admin> fddcfg --show

Local Switch Configuration for all Databases:-
DATABASE - Accept/Reject
---------------------------------
SCC - accept
DCC - accept
PWD - reject <-- Changed setting
FCS - accept
AUTH - accept

Fabric OS FIPS and Common Criteria Configuration Guide 25

53-1003145-02
FIPS Switch Preparation

IPFILTER - accept
(output truncated)
3. Zeroize the switch by completing the following steps.
a) Log in to the switch using an account with securityadmin permissions.
b) Enter fipscfg --zeroize to zeroize the switch.
c) Power-cycle the switch.
Complete the following steps to configure the switch for FIPS.
4. Log in to the switch again using an account with securityadmin permissions.
5. Use the passwd command to change the passwords for all existing user accounts.
6. Use the ipfilter --addrule command to delete or block access to the Telnet port. The rule policy
name and rule number can be arbitrary, but the value for -sip must be any, the value for -dp must
be 23, the value for -proto must be tcp, and the value for -act must be deny.
The following example illustrates this command.
device:admin> ipfilter --addrule new_ipv4 -rule 1 -sip any -dp 23 -proto tcp -act
deny
7. Use the ipfilter --addrule command to delete or block access to the HTTP port. The rule policy
name and rule number can be arbitrary, but the value for -sip must be any, the value for -dp must
be 80, the value for -proto must be tcp, and the value for -act must be deny.
The following example illustrates this command.
device:admin> ipfilter --addrule new_ipv4 -rule 1 -sip any -dp 80 -proto tcp -act
deny
8. Use the ipfilter --show command to display the rule numbers.
The following example illustrates this command.
device:admin> ipfilter --show
Name: default_ipv4, Type: ipv4, State: active
Rule Source IP Protocol Dest Port Action
1 any tcp 22 permit
2 any tcp 23 permit
3 any tcp 80 permit
4 any tcp 443 permit
5 any udp 161 permit
6 any udp 123 permit
7 any tcp 600 - 1023 permit
8 any udp 600 - 1023 permit
Name: default_ipv6, Type: ipv6, State: active
Rule Source IP Protocol Dest Port Action
1 any tcp 22 permit
2 any tcp 23 permit
3 any tcp 80 permit
4 any tcp 443 permit
5 any udp 161 permit
6 any udp 123 permit
7 any tcp 600 - 1023 permit
8 any udp 600 - 1023 permit
9. Use the ipfilter --delrule command to delete or block access to the RPC port. This is accomplished
by removing the last two rules in the policy, using the same rule name as in the previous steps. In
this case they are rules 7 and 8 (based on the results of the previous step).
The following example illustrates these commands.
device:admin> ipfilter --delrule new_ipv4 -rule 8
device:admin> ipfilter --delrule new_ipv4 -rule 7
10.Repeat steps 5 through 7 and then step 9 for the IPv6 policy. (There is no need to repeat step 8.)
The following example illustrates these commands.
device:admin> ipfilter --addrule new_ipv6 -rule 1 -sip any -dp 23 -proto tcp -act
deny
device:admin> ipfilter --addrule new_ipv6 -rule 1 -sip any -dp 80 -proto tcp -act
deny
device:admin> ipfilter --delrule new_ipv6 -rule 8
device:admin> ipfilter --delrule new_ipv6 -rule 7

26 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 FIPS Switch Preparation

11.Optional: Enter ipfilter --show policyrule_name to confirm the rule settings.

The following example shows that ports 80 and 23 (used for HTTP and Telnet, respectively) are
blocked for IPv4.
device:admin> ipfilter --show new_ipv4

Name: new_ipv4, Type: ipv4, State: defined

Rule Source IP Protocol Dest Port Action
1 any tcp 80 deny
2 any tcp 23 deny
3 any tcp 22 permit
4 any tcp 443 permit
5 any udp 161 permit
6 any udp 123 permit
12.Use the seccertutil import command to enable HTTPS.
The following example illustrates this command.
device:admin> seccertutil import -config swcert -enable https -protocol scp -
ipaddr 192.0.2.1 -remotedir /users/home/remote_certs -certname file.crt -login
abcd

Success: imported certificate [file.crt].

Certificate file in configuration has been updated.
Secure http has been enabled.
13.Complete the following steps to preserve and update the switch configuration.

NOTE
Do not use FTP services for the commands in these steps.
a) Use the configUpload command to save the existing configuration to the server.
device:admin> configupload -all -p scp 192.0.2.3,Administrator,config.out

[email protected]'s password: ******

configUpload complete: All selected config parameters are uploaded
2013/12/04-16:26:32, [CONF-1001], 3, FID 5, INFO, switch5, configUpload
completed successfully for all.
b) Use the configDownload command to load the desired configuration from the server.
device:admin> configdownload -all -p scp 192.0.2.3,Administrator,config.out
c) Use the supportSave -n -l command to save the other support information using the secure
copy protocol.
device:admin> supportsave -n -l scp -h 192.0.2.3 -u Administrator -d
directory
d) Use the firmwareDownload -p scp command to download the switch firmware using the
secure copy protocol.
14.Complete the following steps to set the authentication protocols.

NOTE
FIPS compliance requires that you do not use MD5 and SHA-1 hashes, or Diffie-Hellman groups 0
through 3 within the DH-CHAP and FCAP authentication protocols.
a) Enter authUtil --set -h sha256 to set the hash type for the DH-CHAP and FCAP
authentication protocols to SHA-256.
b) Enter authUtil --set -g 4 to set the Diffie-Hellman group to 4. Group 4 is the only Diffie-
Hellman group allowed for FIPS.
c) Optional: You can verify these configurations using the authUtil --show command.

ATTENTION
Do not define FCIP Internet Key Exchange or Internet Protocol security (IPsec) policies.
15.Enter ipSecConfig --disable to disable IPsec for Ethernet.

Fabric OS FIPS and Common Criteria Configuration Guide 27

53-1003145-02
FIPS Switch Preparation

16.For FX8-24, disable IPsec for FCIP connections. The procedure depends on the type of extension
blade used. For FX8-24 extension blades, enter portCfg fciptunnel [slot]/port modify -ipsec 0.
Refer to theFabric OS Administrator's Guide for instructions on disabling IPsec for FCIP
connections on other devices.
17.Enter portCfg --mgmtif delete to disable in-band management.
18.Use the portDisable port_number command to disable each E_Port on the switch.
You must disable the ports before disabling in-flight encryption.
19.Enter portCfgEncrypt --disable to disable in-flight encryption for the switch E_Ports.
20.Use the portEisable port_number command to re-enable each E_Port on the switch.
The following example illustrates this series of commands for port 0.
device:admin> portdisable 0
device:admin> portcfgencrypt --disable 0
device:admin> portenable 0
21.Optional: If TACACS+ authentication, PAP, or CHAP are configured, enter aaaConfig --authspec
local to disable authspec mode.
22.Install the LDAP CA certificate on the switch and Microsoft Active Directory server.
Refer to LDAP CA certificates and FIPS mode on page 23 for detailed instructions.

NOTE
The LDAP CA certificate should be RSA 2048-bit signed with SHA-256.
23.Enter snmpConfig --set seclevel to turn on SNMP security.
When prompted to select the SNMP GET Security Level, enter 0, for no security. When prompted to
select the SNMP SET Security Level, enter 3, for no access.
The following example illustrates this series of commands.
device:admin> snmpconfig --set seclevel

Select SNMP GET Security Level

(0 = No security, 1 = Authentication only, 2 = Authentication and Privacy, 3 = No
Access): (0..3) [0] 0
Select SNMP SET Security Level
(0 = No security, 1 = Authentication only, 2 = Authentication and Privacy, 3 = No
Access): (0..3) [0] 3
24.Enter fipsCfg --enable selftests to enable KAT and conditional tests on the switch.
25.Use the aaaConfig --change server -conf radius -a peap-mschapv2 command to set the
specified server to use only PEAP-MSCHAPv2 as the authentication protocol.
The RADIUS server must also be configured to use only PEAP-MSCHAPv2. Only Windows 2003
and Windows 2008-based RADIUS servers may be used in a FIPS-compliant configuration.

NOTE
If the switch is set for LDAP, refer to the instructions in Setting up LDAP for FIPS mode on page 22.
26.Enter configure and respond to the following prompts to enable signed firmware:
• System services: No
• cfgload attributes: Yes
• Enforce secure config Upload/Download: Press Enter to accept the default.
• Enforce firmware signature validation: Yes
The following example illustrates this series of commands.
device:admin> configure

Not all options will be available on an enabled switch.

28 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 FIPS Switch Preparation

To disable the switch, use the "switchDisable" command.

Configure...
System services (yes, y, no, n): [no] no
…
cfgload attributes (yes, y, no, n): [no] yes
Enforce secure config Upload/Download (yes, y, no, n): [no] no
Enforce firmware signature validation (yes, y, no, n): [no] yes

NOTE
Security must be off or disabled before you disable switch write access and read-only access.
27.If you are not logged in using the root account, log out and log in with that account.
28.Enter fipsCfg --disable bootprom to disable access to the boot PROM.

NOTE
This command can be entered only from the root account. It must be entered before disabling the
root account.
29.Enter userConfig --change root -e no to disable access to the root account.
By disabling the root account, RADIUS and LDAP users with root permissions are blocked in FIPS
mode.
30.Enter fipsCfg --enable fips to enable FIPS mode.
31.Power-cycle the switch or director. Continue after it has restarted.
32.Enter fipsCfg --verify fips to ensure that all verifications are passed. If a verification passes, “PASS”
is displayed. If a verification fails, “FAIL” is displayed.
The following is an example of a partially FIPS-compliant switch:
device:admin> fipscfg --verify fips

Standby firmware supports FIPS - PASS

SELF tests check has passed - PASS
Root account check has passed - PASS
Radius check has passed - PASS
Authentication uses SHA1 hash algorithm.
Authentication check failed - FAIL
Inflight Encryption check has passed - PASS
IPSec check has passed - PASS
IPv6 policies FIPS compliant - PASS
IPv6 policies FIPS compliant - PASS
SNMP is in read only mode. - PASS
Bootprom access is disabled. - PASS
Firmwaredownload signature verification is enabled. - PASS
Secure config upload/download is enabled. - PASS
SSH DSA Keys check passed - PASS
Inband Management interface is disabled - PASS
Ipsecconfig is disabled. - PASS
Signature Algorithm used in LDAP CA certificate is not Sha256
Signature Algorithm used in FCAP CA certificate is not Sha256
Certificates are not FIPS compliant - FAIL
SSH client's signature gen/verify hash value is NOT FIPS complaint - FAIL
SSH server's signature gen/verify hash value is NOT FIPS complaint - FAIL
SSH config is not FIPS compliant - FAIL

Notice for this switch that ipFilter, SNMP, LDAP and FCAP certificates, and SSH compliance all
failed. This switch would not be FIPS-compliant.
• If there are no FAILS, the switch firmware and certificates are FIPS-compliant. The switch as a
whole is not considered FIPS-compliant until the external tamper-evident seals have been
correctly applied. Refer to FIPS 140-2 Security Seal Application Procedures for instructions on
how to apply these seals.
• If there are FAILS, correct the indicated problems, power-cycle the switch or director, and repeat
this step.

Fabric OS FIPS and Common Criteria Configuration Guide 29

53-1003145-02
Notes on enabling FIPS mode

Notes on enabling FIPS mode

• When FIPS mode is enabled on the switch, the cryptographic key value cannot be configured to
less than 128. This is to ensure compliance with FIPS 140-2.
• Externally generated RSA key pairs will only be imported if they are RSA 2048-bit keys.
• After any certificate operations (for example, importing) enter fipsCfg --verify fips to validate FIPS
compliance.
• For FIPS-compliant SSH sessions, use fipsCfg --enable SHA256 to ensure that the SSH sessions
are signed and verified using SHA-256 encryption. Alternatively, you could use ECDSA host key
authentication.
• SSH clients and servers must support diffie-hellman-group-exchange-256 and the ability to sign and
verify with SHA-256 encrypted keys to connect to the switch.
• You can determine if the cryptographic module is running in FIPS mode or non-FIPS mode by using
fipsCfg --show. If the switch is in FIPS mode, the message "FIPS mode is: Enabled" is displayed.
If the switch is not in FIPS mode, the message "FIPS mode is: Disabled" is displayed.
• For FastIron products, the commands fipscfg -disable dh and fipscfg -disable sha256are not
applicable.

ATTENTION
Before a switch is considered FIPS-compliant, you must also install the removable front cover (if
applicable) and correctly apply the anti-tamper labels. Refer to the FIPS Security Seal Procedures
manual for your switch to get directions on where and how to apply the labels.

Power-on self-tests
A power-on self-test (POST) is invoked by powering on the switch in FIPS mode and does not require
any operator intervention. If any KATs fail, the switch goes into a FIPS Error state, which reboots the
system to start the test again. If the switch continues to fail the FIPS POST, you will need to return
your switch to your switch service provider for repair. Refer to the Fabric OS Troubleshooting and
Diagnostics Guide for information about preparing a case for your service provider.

Power-on firmware checksum test

FIPS requires the check sums of the executables and libraries on the file system to be validated
before Fabric OS modules are launched. This is to make sure these files have not been changed after
they are installed.
When firmware RPM packages are installed during firmware download, the MD5 check sums of the
firmware files are stored in the RPM database on the file system. The check sums go through all of the
binaries in the RPM database. Every file compares its current checksum with the checksum that is in
the RPM database. If they are different, the command line interface displays an output message
informing you of the difference.
Because the validation may take up to a few minutes, it is only performed after a cold reboot of the
switch.

30 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 Conditional tests

Conditional tests
These conditional tests are for the random number generators and are executed to verify the
randomness of the random number generator. The conditional tests are executed each time prior to
using the random number provided by the random number generator.
The results of the POST and conditional tests are recorded in the system log or are output to the local
console. This action includes logging both passing and failing results. Refer to the Fabric OS
Troubleshooting and Diagnostics Guide for instructions on how to recover if your system cannot get out
of the conditional test mode.

Fabric OS FIPS and Common Criteria Configuration Guide 31

53-1003145-02
Conditional tests

32 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
Common Criteria Certification

● Overview......................................................................................................................... 33
● TOE network interface.................................................................................................... 33
● TOE firmware update...................................................................................................... 34
● Configuring the FOS switch for Common Criteria........................................................... 35
● Cryptographic Configurations in Common Criteria..........................................................36
● Self tests......................................................................................................................... 37
● Commands supported in Common Criteria.....................................................................38
● Audit messages...............................................................................................................38

Overview
This chapter contains steps for configuring the Brocade FOS switch for Common Criteria (CC)
standards with version 7.3.0a (NDPP -Protection profile for Network Devices) .
Common Criteria certification for a device enforces a set of security standards and feature limitations on
a device to be compliant with the Common Criteria standards, similar to placing the device in FIPS
mode. To better understand the Common Criteria certification and the associated security functions that
are subjected to certification, refer to the Brocade Communications Systems, Inc. Brocade Directors
and Switches 7.3 (NDPP11e3) Security Target document.
Brocade FOS switches provide switching functionality used in Fibre channel domain. The FOS device
management functions are isolated through authentication. Once administrators log in with specific
credentials, their access is limited to commands for which they have privileges and role-based
permissions. Additionally, network management communication paths are protected against
modification and disclosure using SSHv2.
FIPS 140-2 level2 specifies the security requirements that are satisfied by a cryptographic module
utilized within a security system protecting sensitive information of the system.
Brocade FOS switches running FOS version 7.3.0a1 are designed to support FIPS compliance mode.
All cryptographic algorithms required and used in CC are certified by FIPS certifications.

NOTE
To determine if the FOS device and current software version is Common Criteria certified, see https://
www.niap-ccevs.org/CCEVS_Products/pcl.cfm.

TOE network interface

The Target of Evaluation (TOE) is managed through an Ethernet port where the following processes
respond to process the network packets. All these processes run under root privilege.
• Secd: It is the primary process for major security related functionality. It supports the following:

Fabric OS FIPS and Common Criteria Configuration Guide 33

53-1003145-02
TOE firmware update

‐ Authentication and authorization with LDAP and RADIUS server.

‐ Authentication, authorization and accounting with TACACS.
‐ Role based access control.
‐ Authentication and authorization with the local user database management.
‐ ACL through IP filter on the TCP/UDP connections.
• Authd: It is the process that supports authentication by DH-CHAP and FCAP for the Fibre Channel
data port between the TOEs.
• TCP/IP stack: It is the FOS IP stack from the kernel that accepts all packets from network interface
and applies IP filter rules as configured.
• Syslog-ng: It is the process that supports logging of audit messages through TLS tunnel on a
remote server.
• SSHd: It is the process available on port 22 that provides a terminal session after authentication
using the SSH protocol.
• HTTPS: It is the process available on port 443 that provides web access through HTTPS over TLS
for managing the switch.

TOE firmware update

Firmware packages are signed using the 2048 bit RSA key with SHA256 during firmware build and
verified during firmware installation as specified below.
1. RPM packages are signed with the private key to create a SHA256 digest when the firmware
package is generated.
2. Public key is packaged in an RPM package as part of the firmware and is downloaded as the first
file.
3. As part of firmware download, each package is validated by verifying the signature.
4. Installation begins after the packages are validated.
5. The switch restarts after the successful installation.

NOTE
If the installation fails, an error with details are displayed and the download procedure is terminated.
The public key file on the switch contains only one public key. It is only able to validate firmware
signed using one corresponding private key. If the private key changes in future releases, you must
change the public key on the switch by using the firmwareDownload command. When a new
firmware is downloaded, firmware download always replaces the public key file on the switch with what
is in the new firmware. This allows you to have planned firmware key changes.

Firmware Download:
Perform the following tasks to download the firmware.
1. Brocade uploads the signed firmware as a tar file with its associated MD5 on secure location.

NOTE
File location and version details are provided to the customer.
2. Download and verify with the MD5.

34 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 Configuring the FOS switch for Common Criteria

Configuring the FOS switch for Common Criteria

To configure the Brocade Fabric OS device to operate in the Common Criteria mode, perform the
following tasks:
1. Log in as root user.
2. Enable self-tests using the fipscfg --enable selftests command.
3. Execute the fipscfg --zeroize command to zeroize the Critical Security Parameters (CSPs).
4. Power-cycle the module.
5. Enable secure mode for secure upload and signature verification check using the configurechassis
command to ensure secure communication. For example:
device:swadmin> configurechassis

Configure...

cfgload attributes (yes, y, no, n): [no] y

Enforce secure config Upload/Download (yes, y, no, n): [no] y

Enforce signature validation for firmware (yes, y, no, n): [no] y
6. Configure the system for crypto compliance:
a. SSH compliance using: seccryptocfg --default -type SSH.
b. TLS compliance using: cipherconfig --default -type https (user with root credentials only)
7. Using ipfilter command, block Telnet, HTTP ports, and enable HTTPS port.
a. ipfilter --clone FIPS_v4 -from default_ipv4
b. ipfilter --delrule FIPS_v4 -rule 2
c. ipfilter --delrule FIPS_v4 -rule 5
d. ipfilter --delrule FIPS_v4 -rule 3
e. ipfilter --activate FIPS_v4

NOTE
Repeat steps a to e for default_ipv6 too.
8. Administrator should ensure that the FTP mode of transfer is not selected for the following
operations.
a. Upload the system configuration.
b. Download the system configuration.
c. Save the RASLOG, TRACE, supportshow, core file, FFDC data, and other support
information.
d. Download the firmware.

NOTE
Since FCIP IKE or IPSec are not certified for CC compliance, do not configure them.
9. Disable IPSec management interface using the ipsecconfig --disable command.
10.Disable In-Band management interface if it is already configured.
11.Disable In-Flight encryption using the portcfgencrypt --disable portnumber command.

NOTE
Do not define TACACS+ authspec mode.
12.Configure PEAP MS-CHAP V2 for RADIUS authentication if required. If RADIUS server is configured
for authentication, obfuscate the RADIUS shared secret during configuration. For example,

Fabric OS FIPS and Common Criteria Configuration Guide 35

53-1003145-02
Cryptographic Configurations in Common Criteria

aaaconfig –add 192.0.2.1 –conf radius –s sharedsecret –e aes256 –a peap-

mschapv2
13.Configure SNMP access list for read-only access using the snmpconfig --set seclevel command.
For example,
device:root> snmpconfig --set seclevel 3
Select SNMP GET Security Level
(0 = No security, 1 = Authentication only, 2 = Authentication and Privacy, 3 = No
Access): (0..3) [0] 0
Select SNMP SET Security Level
(0 = No security, 1 = Authentication only, 2 = Authentication and Privacy, 3 = No
Access): (0..3) [0] 3
14.Externally generated RSA key pairs shall only be imported if they are of the RSA 2048 type.
Generate key pair. Example: seccertutil genkey -keysize 2048 –nowarn
Export CSR. Example: seccertutil export -protocol scp -ipaddr 192.0.2.2 -
remotedir /share/certs -login cert
Import root CA. Example: seccertutil import -config cacert -protocol scp -
ipaddr 192.0.2.2 -remotedir /share/certs -login cert -certname
2048caSHA256.pem
Import switch cert and restart https. Example: seccertutil import -protocol scp -
syslogcacert -ipaddr 192.0.2.1 -remotedir /cert/location -login
certuser -certname cacert.pem
15.Configure secure mode of transport for audit log with syslogadmin command. For example:
seccertutil import -protocol scp -syslogcacert -ipaddr 192.0.2.12 -remotedir /etc/
syslog-ng/ck -login root -certname cacert-sha256.pem
syslogadmin --set -ip 192.0.2.12 -secure -port 6514
16.Enable auditing of security events using auditcfg --class 1,2,3,4,5,7,8,9;auditcfg --enable
command.
17.Disable the Factory and Root roles using the following commands:
a. userconfig –change root –e no
b. userconfig –change factory –e no
18.Login as Administrator. The FOS device is now configured for the CC mode.

Cryptographic Configurations in Common Criteria

The FOS device in CC supports the following cryptographic configurations.
TLS
• TLSv1.0, TLSv1.1, and TLSv1.2 protocol version for TLS communication are supported.
• TLS v1.2 is not supported on RADIUS.
• The AES-128 and AES-256 encryption algorithm (with SHA1 and SHA256 as MAC) are supported.
• RSA is used for authentication.
• DES-based cipher suites are not supported.
SSH
The following algorithm are supported:
• Host authentication - ssh-rsa, and ecdsa-sha2-nistp256.
• Ciphers - aes128-cbc and aes256-cbc.
• Keyed-Hash Message Authentication code (HMAC)- hmac-sha1, hmac-sha2-256, and hmac-
sha2-512.
• Key exchange- ecdh-sha2-nistp256, ecdh-sha2-nistp384, and ecdh-sha2-nistp521- diffie-hellman-
group14-sha1.

36 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 Self tests

Self tests
The table provides detailed information about the tests that are executed during the boot up of the
switch to confirm the authenticity of the algorithms.

NOTE
During a self test failure, Brocade recommends that you restart the system and test again. If the failure
persists, then proceed with the Return Materials Authorization (RMA) request for the Fabric OS device.

Algorithm Description

TDES This module implements a KAT for the encrypt and decrypt operations of Triple
DES in the CBC mode of operation.
The test passes only if the calculated output equals the known output for both
operations. The Triple DES KAT must execute successfully before using Triple
DES functionality

AES This module implements a known answer test (KAT) for encrypt/ decrypt
operation of AES-128 block size and 256 key size in the CBC mode of operation.
The test passes only if the calculated result equals the known result for both
encryption/decryption. The AES KAT must execute successfully before accessing
AES functionality.

HMAC SHA-1 This module implements the short messages test as part of KAT for SHA-1 and
later the HMAC validation testing is done.
Short Messages Test-tests the ability to correctly generate message digests for
messages of smaller length.

HMAC SHA-256 This module implements the short messages test as part of KAT for SHA-256 and
later the HMAC validation testing is done.
Short Messages Test-tests the ability to correctly generate message digests for
messages of smaller length.

DRNG This module tests whether the random number generated is deterministic. This
test compares a known seed and known output against the random number
generated.

RSA sign/verify This module implements a KAT for signing and verification operation of RSA. The
test passes only if the signature is verified. The KAT must execute successfully
before the operator can access RSA functionality.

AES GCM This module implements a KAT for AES encryption and decryption using GCM.

SHA512 This module implements the SHA 512 short message test as of KAT.

HMAC SHA512 This module implements the short messages test as part of KAT for SHA-512 and
later the HMAC validation testing is done.
Short Messages Test-tests the ability to correctly generate message digests for
messages of smaller length.

TLS Implements the KDF for TLS as per the SP800-131A.

SSH Implements the KDF for SSH as per the SP800-131A.

EC DSA Implements the EC DSA pair wise consistency test.

EC DH Implements the EC DH test.

Fabric OS FIPS and Common Criteria Configuration Guide 37

53-1003145-02
Commands supported in Common Criteria

Commands supported in Common Criteria

The following commands are provided for administration purpose:
• aaaconfig
• auditcfg
• bannerset
• bannershow
• cipherconfig
• configurechassis
• configure
• configdownload
• configupload
• date
• fipscfg --enable selftests
• fipscfg --show
• fipscfg --verify fips
• fipscfg --zeroize
• firmwareshow
• ipfilter
• ipsecconfig
• login
• logout
• motd --set
• motd --show
• passwd
• portcfgencrypt
• reboot
• seccertutil
• seccryptocfg
• snmpconfig
• sshutil
• syslogadmin
• timeout
• tsclockserver
• userconfig

Audit messages
Audit messages are generated based on security events. All Audit messages will include ID, time,
module ID, switch name and the message.
• TS-1009: The audit message indicates that the time was updated using the date CLI. For example:
Apr 1 10:10:01 Brocade300AD raslogd: 2013/04/01-10:10:01, [TS-1009], 90, WWN 10:00:00:05:1e:
74:84:73 | FID 128, INFO, Brocade300AD, Date changed by user.
• TS-1010: The audit message indicates that the time was updated from a NTP server. For example:
2015/01/22-11:16:21, [TS-1010], 29, FID 128, INFO, sw0, NTP Server Time Update from
2015/01/22-11:16:19.920251 to 2015/01/22-11:16:21.983630

38 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02
 Common Criteria Certification

• RAS-2006: The audit message indicates that a syslog server IP address has been added. For
example:
Feb 5 21:27:05 10.38.37.150 raslogd: AUDIT, 2015/02/05-21:27:04 (GMT), [RAS-2006], INFO,
SECURITY, admin/admin/NONE/console/CLI, ad_0/Brocade300/CHASSIS, 7.3.0a1, , , , , , , Syslog
server IP address 10.38.37.40 added.
• RAS-2007: The audit message indicates that a syslog server IP address has been removed. For
example:
Feb 5 21:27:43 10.38.37.150 raslogd: AUDIT, 2015/02/05-21:27:43 (GMT), [RAS-2007], INFO,
SECURITY, admin/admin/NONE/console/CLI, ad_0/Brocade300/CHASSIS, 7.3.0a1, , , , , , , Syslog
server IP address 10.38.37.40 removed.

Fabric OS FIPS and Common Criteria Configuration Guide 39

53-1003145-02
Audit messages

40 Fabric OS FIPS and Common Criteria Configuration Guide

53-1003145-02