Prev   Contents   Next

Annex A
(informative)

Security functional requirements application notes

This annex contains informative guidance for the families and components defined in the normative elements of this CC Part 2, which may be required by users, developers or evaluators to use the components. To facilitate finding the appropriate information, the presentation of the classes, families and components in this annex is similar to the presentation within the normative elements. The class, family, and component structures in this annex differ from those found in the main body of this part of the CC, as this annex is concerned with only those sections that are informative.

A.1  Structure of the notes

This clause defines the content and presentation of the notes related to functional requirements of the CC.

A.1.1  Class structure

Figure A.1 below illustrates the functional class structure in this annex.

Figure A.1 - Functional class structure

A.1.1.1  Class name

This is the unique name of the class defined in Part 2 of the CC.

A.1.1.2  Class introduction

The class introduction in this annex provides information about the use of the families and components of the class. This information is completed with the informative diagram that describes the organisation of each class with the families in each class and the hierarchical relationship between components in each family.

A.1.2  Family structure

Figure A.2 illustrates the functional family structure for application notes in diagrammatic form.

Figure A.2 - Functional family structure for application notes

A.1.2.1  Family name

This is the unique name of the family defined within the normative elements of this part of the CC.

A.1.2.2  User notes

The user notes contain additional information that is of interest to potential users of the family, that is PP, ST and functional package authors, and developers of TOEs incorporating the functional components. The presentation is informative, and might cover warnings about limitations of use and areas where specific attention might be required when using the components.

A.1.2.3  Evaluator notes

The evaluator notes contain any information that is of interest to developers and evaluators of TOEs that claim compliance with a component of the family. The presentation is informative and can cover a variety of areas where specific attention might be needed when evaluating the TOE. This can include clarifications of meaning and specification of the way to interpret requirements, as well as caveats and warnings of specific interest to evaluators.

These User Notes and Evaluator Notes sections are not mandatory and appear only if appropriate.

A.1.3  Component structure

Figure A.3 illustrates the functional component structure for the application notes.

Figure A.3 - Functional component structure

A.1.3.1  Component identification

This is the unique name of the component defined in Part 2 of the CC.

A.1.3.2  Component rationale and application notes

Any specific information related to the component can be found in this section.

-       The rationale contains the specifics of the rationale that refine the general statements on rationale for the specific level, and should only be used if level specific amplification is required.

-       The application notes contain additional refinement in terms of narrative qualification as it pertains to a specific component. This refinement can pertain to user notes, and/or evaluator notes as described in Subclause A.1.2. This refinement can be used to explain the nature of the dependencies (e.g. shared information, or shared operation).

This section is not mandatory and appears only if appropriate.

A.1.3.3  Permitted operations

This portion of each component contains advice relating to the permitted operations of the component.

This section is not mandatory and appears only if appropriate.

A.2  Dependency table

Table A.1 - Dependency table for functional components, shows their direct, indirect and optional dependencies. Each of the components that is a dependency of some functional component is allocated a column. Each functional component is allocated a row. The value in the table cell indicate whether the column label component is directly required (indicated by a cross 'X'), indirectly required (indicated by a dash '-'), or optionally required (indicated by a 'O') by the row label component. An example of a component with optional dependencies is FDP_ETC.1, which requires either FDP_ACC.1 or FDP_IFC.1 to be present. So if FDP_ACC.1 is present, FDP_IFC.1 is not necessary and vice versa. If no character is presented, the component is not dependent upon another component.