Specifications

Security Target Version 1.0 9/29/2014

FCS_IPSEC_EXT.1.4

The TSF shall ensure that [IKEv1 SA lifetimes are able to be limited by number of packets and

time: 24 hours for Phase 1 SAs and 8 hours for Phase 2 SAs; IKEv2 SA lifetimes can be

configured by an administrator based on number of packets or length of time].

Assurance Activity:

If IKEv1 requirements are selected, the evaluator checks to ensure that the TSS describes how

lifetimes for IKEv1 SAs (both Phase 1 and Phase 2) are established. If they are configurable, then

the evaluator verifies that the appropriate instructions for configuring these values are included in

the operational guidance. For IKEv2 requirements, the evaluator verifies that the values can be

configured and that the instructions for doing so are located in the operational guidance. The

evaluator also performs the following tests, depending on whether IKEv1, IKEv2, or both are

configured:

Test 1 (IKEv1): The evaluator shall construct a test where a Phase 1 SA is established and

attempted to be maintained for more than 24 hours before it is renegotiated. The evaluator shall

observe that this SA is closed or renegotiated in 24 hours or less. If such an action requires that the

TOE be configured in a specific way, the evaluator shall implement tests demonstrating that the

configuration capability of the TOE works as documented in the operational guidance.

Test 2 (IKEv1): The evaluator shall perform a test similar to Test 1 for Phase 2 SAs, except that

the lifetime will be 8 hours instead of 24.

Test 3 (IKEv1 and v2): The evaluator shall configure a maximum lifetime in terms of the # of

packets allowed; this may be a hard-coded value for IKEv1, otherwise, the evaluator follows the

operational guidance. The evaluator shall establish an SA and determine that once the allowed # of

packets through this SA is exceeded, the connection is closed.

Test 4 (IKEv2): The evaluator shall configure a time-based maximum lifetime for an SA, and then

establish the SA. The evaluator shall observe that this SA is closed or renegotiated in the

established time.

FCS_IPSEC_EXT.1.5

The TSF shall generate the secret value x used in the IKE Diffie-Hellman key exchange ('x' in gx

mod p) using the random bit generator specified in FCS_RBG_EXT.1, and having a length of at

least [112, 160, 256, and 384] bits.

Assurance Activity:

The evaluator shall check to ensure that, for each DH group supported by the TSF, the TSS

describes the process for generating 'x'(as defined in FCS_IPSEC_EXT.1.5) and each nonce. The

evaluator shall verify that the TSS indicates that the random number generated that meets the

requirements in this PP is used, and that the length of 'x' and the nonces meet the stipulations in

the requirement.

FCS_IPSEC_EXT.1.6

The TSF shall generate nonces used in IKE exchanges in a manner such that the probability that a

specific nonce value will be repeated during the life a specific IPsec SA is less than 1 in 2^[80,

128, and 192].

Assurance Activity:

See the Assurance Activity for FCS_IPSEC_EXT.1.5.

FCS_IPSEC_EXT.1.7

The TSF shall ensure that all IKE protocols implement DH Groups 14 (2048-bit MODP) and, [19

(256-bit Random ECP), 20 (384-bit Random ECP), [DH MODP Group 2 (1024-bit group)]]