Specifications

Security Target Version 1.0 9/29/2014

The evaluators shall perform a Variable Seed Test. The evaluators shall provide a set of 128 (Seed,

DT) pairs to the TSF RBG function, each 128 bits. The evaluators shall also provide a key (of the

length appropriate to the AES algorithm) that is constant for all 128 (Seed, DT) pairs. The DT

value is incremented by 1 for each set. The seed values shall have no repeats within the set. The

evaluators ensure that the values returned by the TSF match the expected values.

The evaluators shall perform a Monte Carlo Test. For this test, they supply an initial Seed and DT

value to the TSF RBG function; each of these is 128 bits. The evaluators shall also provide a key

(of the length appropriate to the AES algorithm) that is constant throughout the test. The

evaluators then invoke the TSF RBG 10,000 times, with the DT value being incremented by 1 on

each iteration, and the new seed for the subsequent iteration produced as specified in NIST-

Recommended Random Number Generator Based on ANSI X9.31 Appendix A.2.4 Using the 3-

Key Triple DES and AES Algorithms, Section 3. The evaluators ensure that the 10,000th value

produced matches the expected value.

5.2.2.14 Extended: Secure Shell (SSH) (FCS_SSH_EXT.1)

FCS_SSH_EXT.1.1

The TSF shall implement the SSH protocol that complies with RFCs 4251, 4252, 4253, and 4254.

Assurance Activity:

In order to show that the TSF implements the RFCs correctly, the evaluator shall ensure that the

TSS contains the following information:

For each section of each applicable RFC listed for the FCS_SSH_EXT.1 elements, for all

statements that are not 'MUST' (for example, 'MAY', 'SHOULD', 'SHOULD NOT', etc.),

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

functionality is indicated as 'SHOULD NOT' or 'MUST 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 section of each RFC, any omission of functionality related to 'MUST' or

'SHOULD' statements shall be described;

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

alternative implementations allowed by the standard that may impact the security

requirements the TOE is to enforce shall be described.

FCS_SSH_EXT.1.2

The TSF shall ensure that the SSH connection be rekeyed after no more than 2^28 packets have

been transmitted using that key.

Assurance Activity:

The evaluator shall examine the TSS to ensure that it specifies that the TOE rekeys an SSH

connection before more than 2^28 packets have been sent with a given key. If this effect is

achieved by configuration of the TOE, then the evaluator shall examine the operational guidance

to ensure that it contains instructions on setting the appropriate values.

FCS_SSH_EXT.1.3

The TSF shall ensure that the SSH protocol implements a timeout period for authentication as

defined in RFC 4252 of [30 seconds], and provide a limit to the number of failed authentication

attempts a client may perform in a single session to [3] attempts.

Assurance Activity:

The evaluator shall check to ensure that the TSS specifies the timeout period and the method for

dropping a session connection after the number of failed authentication attempts specified in the

requirement. If these values are configurable and may be specified by the administrator, the