Зарубежные нормативные документы и критерии на английском / CCPART2V21

Part 2: Security functional requirements

Structure of the notes

526

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

527

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

requirements of the CC.

A.1.1

Class structure

528

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

Functional

Class

Class

Name

Class

Key

Introduction

The Functional Class

can contain multiple

Functional

Functional Families.

l

Families

Figure A.1

- Functional class structure

A.1.1.1

Class name

529

This is the unique name of the class defined within the normative elements of this

part of the CC.

August 1999

Version 2.1

Page 173 of 354

A - Security functional requirements application notes

Structure of the notes

A.1.1.2

Class introduction

530

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

531

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

diagrammatic form.

Functional

Family

Family name

User notes

Key

Evaluator notes

The Functional Family

can contain multiple

Components

Components.

Figure A.2 - Functional family structure for application notes

A.1.2.1

Family name

532

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

533

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

534

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.

Page 174 of 354

Version 2.1

August 1999

Structure of the notes

A - Security functional requirements application notes

535

These User Notes and Evaluator Notes sections are not mandatory and appear only

if appropriate.

A.1.3

Component structure

536

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

Component

Component

Identification

Component

Rationale &

Application notes

Permitted

Operations

Figure A.3 - Functional component structure

A.1.3.1

Component identification

537

This is the unique name of the component defined within the normative elements of

this part of the CC.

A.1.3.2

Component rationale and application notes

538

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).

539

This section is not mandatory and appears only if appropriate.

A.1.3.3

Permitted operations

540

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

of the component.

541

This section is not mandatory and appears only if appropriate.

August 1999

Version 2.1

Page 175 of 354

A - Security functional requirements application notes

Dependency table

A.2

Dependency table

542

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

A

A

A

A

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

D

G

V

V

A

A

A

A

C

C

C

C

D

D

D

D

D

D

D

D

I

I

I

M M M M M M P

P

P

P

P

P

P

T

T

V

D

A

A

U

U

U

U

S

S

S

S

P

P

P

P

P

P

P

P

A

A

A

T T T T T T R

T

T

T

T

T

T

P

P

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_ _ _ _ _ _ _

_

_

_

_

_

_

_

_

S

A

C

C

G

S

S

S

C

C

C

C

A

A

I

I

I

I

I

U

A

U

U

M M M M M S U

A

F

I

S

T

T

I

T

P

D

C

C

E

A

A

T

K

K

K

O

C

C

F

F

T

T

T

I

T

A

I

O S S S T M N

M L

T

T

D

S

T

R

M M A

A

N

A

R

G

M M M P

C

F

C

F

C

T

T

T

D

U

D

F A A A D R O

T S

T

M C

T

C

P

. . .

.

.

.

.

.

. . . .

.

.

.

.

.

.

.

.

.

.

.

. . . . . . .

. .

.

. .

.

.

.

1

1

1

3

1

1

1

1

1

2

4

1

1

1

1

1

1

1

2

1

1

1

1

1

1

2

3

1

1

1

1

1

1

1

1

1

1

1

FAU_ARP.1

-

x

-

FAU_GEN.1

x

FAU_GEN.2

x

x

-

FAU_SAA.1

x

-

FAU_SAA.2

x

FAU_SAA.3

FAU_SAA.4

FAU_SAR.1

x

-

FAU_SAR.2

-

x

-

FAU_SAR.3

-

x

-

FAU_SEL.1

x

-

x

-

-

FAU_STG.1

x

-

FAU_STG.2

x

-

FAU_STG.3

-

x

-

Page 176 of 354

Version 2.1

August 1999

Dependency table

A - Security functional requirements application notes

A

A

A

A

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

F

D

G

V

V

A

A

A

A

C

C

C

C

D

D

D

D

D

D

D

D

I

I

I

M M M M M M P

P

P

P

P

P

P

T

T

V

D

A

A

U

U

U

U

S

S

S

S

P

P

P

P

P

P

P

P

A

A

A

T T T T T T R

T

T

T

T

T

T

P

P

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_ _ _ _ _ _ _

_

_

_

_

_

_

_

_

S

A

C

C

G

S

S

S

C

C

C

C

A

A

I

I

I

I

I

U

A

U

U

M M M M M S U

A

F

I

S

T

T

I

T

P

D

C

C

E

A

A

T

K

K

K

O

C

C

F

F

T

T

T

I

T

A

I

O S S S T M N

M L

T

T

D

S

T

R

M M A

A

N

A

R

G

M M M P

C

F

C

F

C

T

T

T

D

U

D

F A A A D R O

T S

T

M C

T

C

P

. . .

.

.

.

.

.

. . . .

.

.

.

.

.

.

.

.

.

.

.

. . . . . . .

. .

.

. .

.

.

.

1

1

1

3

1

1

1

1

1

2

4

1

1

1

1

1

1

1

2

1

1

1

1

1

1

2

3

1

1

1

1

1

1

1

1

1

1

1

FAU_STG.4

x

-

FCO_NRO.1

x

FCO_NRO.2

x

FCO_NRR.1

x

FCO_NRR.2

x

FCS_CKM.1

-

-

o

x

o

-

-

-

-

-

-

-

x

-

-

FCS_CKM.2

-

o

-

x

-

-

-

-

-

o

-

-

x

-

-

FCS_CKM.3

-

o

-

x

-

-

-

-

-

o

-

-

x

-

-

FCS_CKM.4

-

o

-

-

-

-

-

-

-

o

-

-

x

-

-

FCS_COP.1

-

o

-

x

-

-

-

-

-

o

-

-

x

-

-

FDP_ACC.1

-

x

-

-

-

-

-

-

FDP_ACC.2

-

x

-

-

-

-

-

-