Technical data
Brocade Communications Systems, Inc. Page 18 of 48
failed logons.
FIA_UAU.5
unsuccessful use of the authentication
mechanism
FIA_UID.2
unsuccessful use of the user identification
mechanism, including the user identity
provided
FMT_SMF.1
use of the management functions (specifically,
zone configuration, data encryption
configuration, password management
configuration, authentication attempts
maximum configuration, TOE access filtering
configuration, and setting user attributes)
FMT_SMR.1
modifications to the group of users that are
part of a role
5.1.2 Cryptographic Support
5.1.2.1 Cryptographic operation for trusted path (FCS_COP.1(1))
FCS_COP.1.1(1) The TSF shall perform [SSH and SSL trusted path operations] in accordance with a specified
cryptographic algorithm [shown in column 1 of the table below] and cryptographic key sizes
[shown in column 2 of the table below] that meet the following: [shown in column 3 of the
table below].
Algorithm
Key Sizes
Standards
HMAC-SHA1
160 bit
FIPS 198
3DES-CBC
168 bit
FIPS 46-3
AES128-CBC
128 bit
FIPS 197
AES192-CBC,
192 bit
FIPS 197
AES256-CBC
256 bit
FIPS 197
TLS/AES128
128 bit
FIPS 197
5.1.2.2 Cryptographic operation for user data encryption (FCS_COP.1(2))
FCS_COP.1.1(2) The TSF shall perform [user data encryption] in accordance with a specified cryptographic
algorithm [AES256] and cryptographic key sizes [256 bit] that meet the following: [FIPS 197].
5.1.2.3 Cryptographic key generation (FCS_CKM.1(1))
FCS_CKM.1.1 The TSF shall generate cryptographic keys in accordance with a specified cryptographic key
generation algorithm [pseudo random key generation] and specified cryptographic key sizes
[128, 160, 168, 192 and 256 bits] that meet the following: [ANSI X9.31 DRNG].
5.1.2.4 Cryptographic key generation (FCS_CKM.1(2))
FCS_CKM.1.1(2) The TSF shall generate cryptographic keys in accordance with a specified cryptographic key
generation algorithm [pseudo random key generation] and specified cryptographic key sizes
[256-bit] that meet the following: [ANSI X9.31 DRNG].
5.1.2.5 Cryptographic key destruction (FCS_CKM.4)
FCS_CKM.4.1 The TSF shall destroy cryptographic keys in accordance with a specified cryptographic key
destruction method [zeroize] that meets the following: [none].










