LABELING CONVENTION IN NIAP INTERPRETATIONS

[iwg@gibraltar.ncsc.mil (IWG)]

This is a multi-part message in MIME format.

------GIBRALTAR_MIME_PART_HDR_1
Content-Type: text/plain;
LABELING CONVENTION IN NIAP INTERPRETATIONS 
 
The Interpretations Working Group has developed a labeling convention 
for the identification of new and changed classes, families, 
components, elements, EALs, and work units. This labeling scheme was 
developed to make it clear to the national and international users of 
the CC what is new and changed as a result of NIAP interpretations. 
 
CLASS/FAMILY/COMPONENT/ELEMENT/ETC. LABELING 
 
A specific labeling convention is used to identify CC or CEM 
structures (i.e., families, classes, components, elements, work-units) 
modified or added by NIAP interpretations: 
 
NEW ITEMS 
 
For new items created by interpretation I-nnnn, the item is identified 
by NIAP-nnnn-m, where nnnn is the interpretation number, and m is 
either the new tag (for new classes or families) or (for new 
components, elements, or work units) a digit to differentiate the item 
from other new items resulting from the same interpretation. The 
identification is used in the following fashion: 
 
o New Class: If interpretation I-1234 created a new class FEX, the 
  class would be NIAP-1234-FEX. 
 
o New Family: If interpretation I-1234 created a new family EXA in 
  existing class FPT, the new family would be FPT_NIAP-1234-EXA 
 
o New Component: If interpretation I-1234 created a new component in 
  FPT_SEP, the new component would be FPT_SEP.NIAP-1234-1 
 
o New Element: If interpretation I-1234 created a new element in 
  FPT_SEP.1, the new element would be FPT_SEP.1.NIAP-1234-1. Assurance 
  elements would still have "C", "D", or "E" suffixes, as appropriate. 
 
o New Work Unit: If interpretation I-1234 created a new work unit for 
  APE_REQ.1, the new work unit would be APE_REQ.1-NIAP-1234-1. 
 
CHANGED ITEMS 
 
For changes to existing items, a similar NIAP-nnnn notation is used; 
however, there is no "-m" added. The change is indicated by adding the 
NIAP tag after that portion of the item name that identifies the 
changed item, following a dash. For example: 
 
o Changed Class: (this applies only when an entire class is replaced): 
  If interpretation I-1234 replaced the entire FMT class, the 
  replacement class would be FMT-NIAP-1234.  
 
o Changed Family: If interpretation I-1234 replaced the entire FMT_MOF 
  family, the replacement family would be FMT_MOF-NIAP-1234 
 
o Changed Component: If interpretation I-1234 replaced (or relabeled) 
  the FMT_MOF.1 component, the replacement component would be 
  FMT_MOF.1-NIAP-1234.  
 
o Changed Element: If interpretation I-1234 replaced FMT_MOF.1.1, the 
  replacement element would be FMT_MOF.1.1-NIAP-1234. Assurance 
  elements would still have "C", "D", or "E" suffixes, as appropriate. 
 
o Changed Work Unit: If interpretation I-1234 changed work unit 
  1:APE_REQ.1-1, the new work unit would be 1:APE_REQ.1-1-NIAP-1234. 
 
CHANGES TO PREVIOUSLY INTERPRETED THINGS 
 
When the changed item has a label affected by a prior interpretation, 
the previous NIAP-nnnn tag is removed. For example, if existing 
FPT_SEP.1.1-NIAP-1234 is changed by a subsequent interpretation 
I-5678, the changed tag is FPT_SEP.1.1-NIAP-5678, not 
FPT_SEP.1.1-NIAP-1234-NIAP-5678. 
 
AFFECT ON PARAGRAPH NUMBERS 
 
The labeling convention is not used for paragraph numbers.  
 
OCCASIONS WHEN THE CONVENTION IS USED FOR CLAUSES OR SUBCLAUSES. 
 
Normally, the labeling convention is not used for clauses or 
subclauses. The convention is used in the following cases: 
 
o New classes, families, or components added to Part 2 or 3. This will 
  result in new subclauses 
 
o New activities or sub-activities added to the CEM. 
 
WHEN THE NEW CONVENTION IS USED 
 
CC Components are relabeled whenever an existing component is modified 
in a way that would be visible when the component is included in a 
PP/ST. Components are relabeled in the following situations: 
 
o when an existing element in an existing component is changed.  
 
o when the dependencies of an existing component are changed.  
 
o when the AUDIT section for that component is changed  
 
Relabeling is not performed:  
 
o when informative paragraphs in the element (front matter, Annex 
  material) are changed 
 
o when the management sections for a specific component are changed 
  Note: Management and Audit sections are actually written at the 
  level of the family; for changes to the audit section, the component 
  is relabeled, yet the family is not. 
 
o solely due to a change in the corresponding CEM workunits 
  Note: This may result in a case where the methodology has changed, 
  yet the new methodology used in an evaluation is not readily 
  apparent from the security components identified in the 
  PP/ST. However, the new methodology can be derived from the required 
  list in the ETR of all interpretations that are used during the 
  evaluation. 
 
When a CC component is relabeled, the following text is used 
(FPT_SEP.1 is used as an example): 
 
o FPT_SEP.1 is relabeled as FPT_SEP.1-NIAP-1234. Unless otherwise 
  noted in these changes, all normative and informative material 
  associated with FPT_SEP.1 is incorporated unchanged into 
  FPT_SEP.1-NIAP-1234, and all references to FPT_SEP.1 in the CC, CEM, 
  or other Common Criteria documentation are changed to refer to 
  FPT_SEP.1-NIAP-1234. 
 
When elements are incorporated without change into a relabeled 
component, they retain their original numbers. 
 
For example, consider an existing FPT_SEP.1, that has elements 
FPT_SEP.1.1 and FPT_SEP.1.2. If interpretation I-1234 modifies 
FPT_SEP.1.2, the relabeled component would be FPT_SEP.1-NIAP-1234, 
with elements: 
 
o FPT_SEP.1.1  
 
o FPT_SEP.1.2-NIAP-1234 
 
If a subsequent interpretation I-5678 modified FPT_SEP.1-NIAP-1234 to 
change FPT_SEP.1.1 and add a new element, the relabeled component 
would be FPT_SEP.1-NIAP-5678, with elements: 
 
o FPT_SEP.1.1-NIAP-5678  
 
o FPT_SEP.1.2-NIAP-1234  
 
o FPT_SEP.1.NIAP-5678-1 
 

------GIBRALTAR_MIME_PART_HDR_1--