Installation guide

Motorola WS5100 Wireless Switch and RFS7000 RF Switch Security Target
Page 7 of 85
The CC allows several operations to be performed on functional requirements; refinement,
selection, assignment, and iteration are defined in paragraph 2.1.4 of Part 2 of the CC. Each of
these operations is used in this ST.
The refinement operation is used to add detail to a requirement, and thus further restricts a
requirement. Refinement of security requirements is denoted by bold text. Deleted words are
denoted by strike-through text.
The selection operation is used to select one or more options provided by the CC in stating a
requirement. Selections are denoted by italicized text.
The assignment operation is used to assign a specific value to an unspecified parameter, such as
the length of a password. Assignment is indicated by showing the value in square brackets,
[Assignment_value].
The iteration operation is used when a component is repeated with varying operations. Iteration is
denoted by showing the iteration number in parenthesis following the component identifier,
(iteration_number).
The CC paradigm also allows protection profile (PP) and security target authors to create their own
requirements. Such requirements are termed ‘explicit requirements’ and are permitted if the CC
does not offer suitable requirements to meet the authors’ needs. Explicit requirements must be
identified and are required to use the CC class/family/component model in articulating the
requirements. In this ST, explicit requirements will be indicated with the “EXP” following the
component name.
Application Notes are provided to help the developer, either to clarify the intent of a requirement,
identify implementation choices, or to define “pass-fail” criteria for a requirement. For those
components where Application Notes are appropriate, the Application Notes will follow the
requirement component.
Assumptions: TOE security environment assumptions are given names beginning with “A.”-- e.g.,
A.ADMINISTRATION.
Threats: TOE security environment threats are given names beginning with “T.”-- e.g.,
T.SIGNAL_DETECT.
Policies: TOE security environment policies are given names beginning with “P.”—e.g.,
P.GUIDANCE.
Objectives: Security objectives for the TOE and the TOE environment are given names beginning
with “O.” and “OE.”, respectively,—e.g., O.ACCESS and OE.ADMIN.