User guide

ManualsBrandsAruba ManualsComputer equipment620

Aruba Networks Security Target

Page 53 of 67

NDPP

Source

Requirement

Assurance

Family

Digital Signature Algorithm Validation System (DSA2VS)", "The FIPS 186-3

Elliptic Curve Digital Signature Algorithm Validation System (ECDSA2VS)", and

"The RSA Validation System (RSA2VS)" as a guide in testing the requirement

above, depending on the selection performed by the ST author. This will require

that the evaluator have a trusted reference implementation of the algorithms that

can produce test vectors that are verifiable during the test.

In order to show that the TSF complies with 800-56A and/or 800-56B, depending

on the selections made, the evaluator shall ensure that the TSS contains the

following information:

 The TSS shall list all sections of the appropriate 800-56 standard(s) to

which the TOE complies.

 For each applicable section listed in the TSS, for all statements that are

not "shall" (that is, "shall not", "should", and "should not"), if the TOE

implements such options it shall be described in the TSS. If the included

functionality is indicated as "shall not" or "should not" in the standard,

the TSS shall provide a rationale for why this will not adversely affect the

security policy implemented by the TOE;

 For each applicable section of 800-56A and 800-56B (as selected), any

omission of functionality related to "shall" or “should” statements shall be

described;

Any TOE-specific extensions, processing that is not included in the documents,

or alternative implementations allowed by the documents that may impact the

security requirements the TOE is to enforce shall be described

ASE_TSS

FCS_CKM

_EXT.4

The evaluator shall check to ensure the TSS describes each of the secret keys

(keys used for symmetric encryption), private keys, and CSPs used to generate

key; when they are zeroized (for example, immediately after use, on system

shutdown, etc.); and the type of zeroization procedure that is performed

(overwrite with zeroes, overwrite three times with random pattern, etc.). If

different types of memory are used to store the materials to be protected, the

evaluator shall check to ensure that the TSS describes the zeroization procedure

in terms of the memory in which the data are stored (for example, "secret keys

stored on flash are zeroized by overwriting once with zeroes, while secret keys

stored on the internal hard drive are zeroized by overwriting three times with a

random pattern that is changed before each write").

ASE_TSS

FCS_COP.

1(1)

The evaluator shall use tests appropriate to the modes selected in the above

requirement from "The Advanced Encryption Standard Algorithm Validation Suite

(AESAVS)", "The XTS-AES Validation System (XTSVS)", The CMAC Validation

System (CMACVS)", "The Counter with Cipher Block Chaining Message

Authentication Code (CCM) Validation System (CCMVS)", and "The

Galois/Counter Mode (GCM) and GMAC Validation System (GCMVS)" (these

documents are available from http://csrc.nist.gov/groups/STM/cavp/index.html)

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.

ATE_IND

10.

FCS_COP.

1(2)

The evaluator shall use the signature generation and signature verification

portions of "The Digital Signature Algorithm Validation System” (DSAVS or

DSA2VS), "The Elliptic Curve Digital Signature Algorithm Validation System”

ATE_IND