
Security Target Version 1.02, 08/16/2013
Assurance Activity – Design
Assurance Activity - Guidance
Assurance Activity - Testing
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 zeros, 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 zeros, 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").
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 the evaluator have a reference implementation
of the algorithms known to be good can produce test
vectors that are verifiable during the test.
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” (ECDSAVS or
ECDSA2VS), and "The RSA Validation System”
(RSAVS) 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 the
evaluator have a reference implementation of the
algorithms known to be good can produce test vectors
that are verifiable during the test.
The evaluator shall use "The Secure Hash Algorithm
Validation System (SHAVS)" as a guide in testing the
requirement above. This will require the evaluator
have a reference implementation of the algorithms
known to be good can produce test vectors that are
verifiable during the test.
The evaluator shall use "The Keyed-Hash Message
Authentication Code (HMAC) Validation System
(HMACVS)" as a guide in testing the requirement
above. This will require the evaluator have a
reference implementation of the algorithms known to
be good can produce test vectors that are verifiable
during the test.
Comentários a estes Manuais