Final Interpretation for RI # 3 - Unique identification of configuration items in the configuration list

Date: 02/11/2002
Subject: Unique identification of configuration items in the configuration list
CC Part #1 Reference: 
CC Part #2 Reference: 
CC Part #3 Reference: CC Part 3, Section 8.2 (ACM_CAP)
CEM Reference: 

Issue:

Is it required that the configuration list uniquely identify all configuration items, including version numbers as appropriate? ACM_CAP.2.6C requires that the CM system uniquely identify all configuration items, but ACM_CAP.2.4C does not explicitly require that the configuration list itself uniquely identify each configuration item, including version numbers as appropriate.



Interpretation

The intent of ACM_CAP.2 is that the developer provides a unique reference for each version of a TOE configuration item that is submitted, whether draft or otherwise, as evaluation evidence. The configuration list need only contain the version of each configuration item that is specific to the TOE that is being evaluated, and as such the configuration items must be uniquely identified in the configuration list. However, for earlier drafts of configuration items that had been submitted by the developer as evaluation evidence, it is necessary for the evaluator to confirm that these drafts also possess unique identifiers in a manner that is consistent with the unique identification method that is described in the CM documentation.

Specific Changes

In the CC, the following new assurance element is added after ACM.CAP.2.3C, ACM.CAP.3.3C, ACM.CAP.4.3C, and ACM_CAP.5.3C:

"The configuration list shall uniquely identify all configuration items that comprise the TOE."

In the CEM,

Rationale

N/A