Chapter 5
SECURITY REQUIREMENTS
The CC permits four types of operations to be performed on security functional
requirements: selection, assignment, refinement, and iteration. These operations are
identified in this ST in the following manner:
l
Selection: Indicated by surrounding brackets and italicized text, e.g., [selected item].
l
Assignment: Indicated by surrounding brackets and regular text, e.g., [assigned item].
l
Refinement:
strikethrough text, e.g., refined item for deleted items.
l
Iteration: Indicated by assigning a number at the functional component level, for
example: FMT_MTD.1.1 (1), FMT_MTD.1.1 (2), FMT_MTD.1.1 (3), FMT_MTD.1.1
(4) refer to separate instances of the FMT_MTD.1 security functional requirement
component.
Table of Contents
SECURITY FUNCTIONAL REQUIREMENTS ............................................................5-1
SECURITY ASSURANCE REQUIREMENTS ...........................................................5-11
5.1 SECURITY FUNCTIONAL REQUIREMENTS
This section provides functional and assurance requirements that must be satisfied by a
compliant TOE. These requirements consist of functional components from Part 2 of the
CC and an Evaluation Assurance Level (EAL) containing assurance requirements from
Part 3 of the CC.
The security requirements consist of two groups of requirements:
1. the security functional requirements (SFRs): a translation of the security objectives for
the TOE into a standardized language; and
2. the security assurance requirements (SARs): a description of how assurance is to be
gained that the TOE meets the SFRs.
5.1.1 Overview
The security functional requirements for this ST consist of the following components from
Part 2 of the CC.
Table 5-1 TOE Security Functional Requirements
CC Part 2 Security Functional Components
Identifier
FAU_GEN.1
SJ-20110815105844-030|2011/08/19(R1.6)
Indicated by underlined text, e.g., refined item for additions or
Name
Audit data generation
5-1
ZTE CORPORATION