PD-0094: Site Visit - Alternative Evaluation Methodology

This decision represents a long-term technical decision based on an OD, and may not be the same as the final results of the source OD. With respect to published criteria documentation and scheme documents, it provides suggested guidance on evaluation direction, but is not authoritative. Authoritative decisions are provided through the published criteria documents and published scheme and international interpretations thereof. With respect to published PPs, PDs are authoritative corrections to the PP, based on input from the PP author (if available), that are in force until the publication of the next revision of that PP.

Issue

A site visit is a commonly used methodology for observing the use of the CM system as described in the CM plan, observing the practical application of delivery procedures, and observing the application of security measures during development. However, CEM v1.0 Part 2, paragraph 1813 indicates that other approaches to gain confidence in these processes should be considered, when the methodology provides a equivalent level of assurance (e.g. to analysis of evaluation evidence). What approaches are acceptable?

Resolution

A site visit is the most effective method for the evaluation team to gain confidence in the developer's use/application of various Configuration Management, development, and delivery procedures and tools. They allow the members of the evaluation team to confirm personally that procedures are being followed in practice. Yet, for various reasons, such as developer location, site visits aren't always possible. This is recognized in the CEM, which permits alternative methods to a site visit to be applied on a case by case basis, with adequate justification by the evaluation team. As with any evaluation procedure, the alternative methods must be consistent, repeatable, clearly articulated, and the evidence used must be documented in terms of its content, its source, and its purpose.

The alternative site visit plan to be used by the evaluation team must be documented in sufficient detail for the validator to review and approve prior to its use. The plan must include detailed product, process, and vendor specific references. The approach will be validated based on knowledge of the specific CM system, access controls, and product distribution methods that are to be used. If the validation team does not find the procedure clearly acceptable, they are encouraged to present the procedure to the community in an OR for community concurrence and review.

There are three primary components/work units that refer to a site visit:

1. ACM_CAP.3 (e.g., 3:ACM_CAP.3-11), which indicates that a site visit is expected to confirm that the developer is using the CM system as described in the CM plan.

2. ADO_DEL.1 (e.g., 3:ADO_DEL.1-3), which indicates a site visit is one possible approach to confirm the developer is delivering the product in accordance with the documented delivery procedures.

3. ALC_DVS.1 (e.g., 3:ALC_DVS.1-4), which indicates a site visit can support verification of the developer's compliance with documented development security measures.

Modification History:

2004-08-12

Updated effective date to reflect the date the PD was issued. (August 2004 NIB 6.c.xiv)

References:

• CEM v1.0 Part 2 Subclause B.5 Paragraph 1813

Related NIs:

• None

Related CCIMB-INTERPs:

• None

Source OD: 0214