Specifications

FTP_ITC_(EXT).1.3(2) The TOE IT environment shall initiate communication via the trusted channel for [all

authentication functions, remote logging, time, [remote configuration from WCS/NCS to

Controllers].

6.2.18 FPT_STM.1 Reliable time stamps

FPT_STM.1.1 The TOE IT environment shall be able to provide reliable time and date stamps for the TOE

and its own use.

6.3 TOE Security Assurance Requirements

The TOE security assurance requirements summarized in Table 16: TOE Assurance

Requirements identify the management and evaluative activities required to address the

threats and policies identified in section 3 of this ST. This ST complies with assurance level

EAL4 augmented with ALC_FLR.2. EAL4 was chosen because it permits a developer to

gain maximum assurance from positive security engineering based on good commercial

development practices. EAL4 provides the developers and users a moderate to high le vel of

independently assured security in conventional commercial TOEs. EAL 4 is augmented by

ALC_FLR.2 to help ensure that the customers can report the flaws and the flaws can be

systematically corrected.

Table 16 TOE Assurance Requirements

Assurance Class

Assurance Components

ADV: Development

ADV_ARC.1 Security architecture description

ADV_FSP.4 Complete functional specification

ADV_IMP.1 Implementation representation of the TSF

ADV_TDS.3 Basic modular design

AGD: Guidance documents

AGD_OPE.1 Operational user guidance

AGD_PRE.1 Preparative procedures

ALC: Life-cycle support

ALC_CMC.4 Production support, acceptance procedures

and automation

ALC_CMS.4 Problem tracking CM coverage

ALC_DEL.1 Delivery procedures

ALC_DVS.1 Identification of security measures

ALC_FLR.2 Flaw reporting procedures

ALC_LCD.1 Developer defined life-cycle model