Hardware manual

Version 1.1, 03/31/2015
GSS CCT Evaluation Technical Report Page 19 of 56 © 2015 Gossamer Security Solutions, Inc.
Document: AAR-BrocadeNetIron5.8 All rights reserved.
2.2.4 CRYPTOGRAPHIC OPERATION (FOR CRYPTOGRAPHIC SIGNATURE) (FCS_COP.1(2))
2.2.4.1 FCS_COP.1(2).1
TSS Assurance Activities: None Defined
Guidance Assurance Activities: None Defined
Testing Assurance Activities: The evaluator shall use the signature generation and signature verification portions
of 'The Digital Signature Algorithm Validation System' (DSA2VS), 'The Elliptic Curve Digital Signature Algorithm
Validation System' (ECDSA2VS), and 'The RSA Validation System' (RSAVS (for 186-2) or RSA2VS (for 186-3)) as a
guide in testing the requirement above. The Validation System used shall comply with the conformance standard
identified in the ST (i.e., FIPS PUB 186-2 or FIPS PUB 186-3). This will require that the evaluator have a reference
implementation of the algorithms known to be good that can produce test vectors that are verifiable during the
test.
The TOE has been FIPS approved. The RSA certificate numbers are 1413 and 1411.
2.2.5 CRYPTOGRAPHIC OPERATION (FOR CRYPTOGRAPHIC HASHING) (FCS_COP.1(3))
2.2.5.1 FCS_COP.1(3).1
TSS Assurance Activities: None Defined
Guidance Assurance Activities: None Defined
Testing Assurance Activities: The evaluator shall use 'The Secure Hash Algorithm Validation System (SHAVS)' as a
guide in testing the requirement above. This will require that the evaluator have a reference implementation of
the algorithms known to be good that can produce test vectors that are verifiable during the test.