/cc:*[@boilerplate='yes']//cc:*[@title='Implicitly Satisfied Requirements']

This appendix lists requirements that should be considered satisfied by products successfully evaluated against this . However, these requirements are not featured explicitly as SFRs and should not be included in the ST. They are not included as standalone SFRs because it would increase the time, cost, and complexity of evaluation. This approach is permitted by [CC] Part 1, 8.2 Dependencies between components.

This information benefits systems engineering activities which call for inclusion of particular security controls. Evaluation against the provides evidence that these controls are present and have been evaluated.


/cc:*[@boilerplate='yes']//cc:section[@title='Terms']
The following sections list Common Criteria and technology terms used in this document.

cc:doctype-short

cc:doctype-long

/cc:PP[@boilerplate='yes']//cc:chapter[@title='Conformance Claims']
Conformance Statement
An ST must claim exact conformance to this , as defined in the CC and CEM addenda for Exact Conformance, Selection-Based SFRs, and Optional SFRs (dated May 2017).
CC Conformance Claims
This is conformant to Parts 2 (extended) and 3 (conformant) of Common Criteria .
PP Claim
This does not claim conformance to any Protection Profile.
Package Claim
This .

/cc:*[@boilerplate='yes']//cc:bibliography
[CC]
Common Criteria for Information Technology Security Evaluation -

citeCC
[CC]

/cc:*[@boilerplate='yes']//cc:*[@title='Security Requirements']|/cc:module//cc:*[@title='Security Requirements']

/cc:Module//cc:*[@title='TOE Security Functional Requirements']

/cc:Module//cc:*[@title='Assumptions']

/cc:Module//cc:*[@title='Security Objectives for the Operational Environment']

//cc:ref[@to='sel-based-reqs']

//cc:ref[@to='obj-reqs']

//cc:ref[@to='impl-reqs']

//cc:ref[@to='ref-strict-optional']