Introduction Section

Updated 29 January 2024

CC:2022 Part 1 (Annex B) requires only that the Introduction include a PP Reference and a PP Overview. In NIAP PPs, the PP Reference appears before the Introduction, so technically only the PP Overview is required in the Introduction.

CC:2022 Part 1 (Annex A) requires that Functional Packages include a Package Overview. In NIAP FPs, the Package Overview is included in the Introduction.

CC:2022 Part 1 (Annex C) requires that PP-Modules include a PP-Module Reference, Identification of PP-Module Base, and a TOE Overview. In NIAP PP-Modules, the Module Reference appears before the Introduction, and the module bases are identified in the TOE Overview.

Note: For some reason CC:2022 Part 1 Annex A refers to a "Package Overview," Annex refers to a "PP Overview," while Annex C refers to a "TOE Overview." For purposes of this wiki, "Package Overview" and "PP Overview" are the same. "TOE Overview" is different.

But the Introduction is not limited to just the Overview. NIAP requirements documents include Terminology Sections and optional sections for Use Cases, Platforms, and Features. Functional Packages include the Terminology Sections, but generally not Use Cases, Platforms, of Features sections. But the PP/FP/Module Author can include other sections that they feel are necessary.

In the XML there are some restrictions on the order of the sections. It is not required that the Overview be in the first section of the Introduction. It could be either before of after the Terminology Sections, but it should be before any Use Cases or Platform or Features Declarations.

• PP Overview or TOE Overview
• Terminology Sections (CC Terms and Tech Terms)
• Other sections (optional)
• Use Cases (optional)
• Platforms Declaration (if EAs depend on platform, e.g. Application PP)
• Features Declaration (if there are Implementation-dependent requirements)
• Other sections (optional)

The PP or TOE Overview may be in the Introductory Text Section or in one of the other optional sections. Generally it includes sub-sections defining Compliant Targets of Evaluation, the TOE Boundary, and expected operational environments. For PP-Modules, it should identify all the Base PPs that the PP-Module may share a PP-Configuration with.

The PP Author may include as many sections as are needed.

The Introduction section must be specified in one of two ways:

  <sec:Introduction> ... </sec:Introduction>

or

  <section title="Introduction" id="sec-intro">  ... </section>

Sections

Generally, sections in the Introduction can cover any topic and contain arbitrary text. The Introduction must contain one section at the beginning followed by a tech-terms section. After that there can be any number of other sections, including a use-cases section. Sections are indicated as follows.

  <section title="Section Title" id="sec-secid" boilerplate="no">

The id attribute must be unique within the XML document.

Some sections have predefined titles. And some predefined sections are automatically populated with boilerplate text. Use the boilerplate attribute to turn off the auto generation if you prefer to write your own. The default value is "yes" if the attribute is not included.