Раздел: Документация
0 ... 25 26 27 28 29 30 31 ... 73 acm cap.2.2dThe developer shall use a CM system. acm cap.2.3dThe developer shall provide CM documentation. Content andpresentation of evidence elements: acm cap.2.1cThe reference for the TOE shall be unique to each version of the TOE. acm cap.2.2cThe TOE shall be labelled with its reference. acm cap.2.3cThe CM documentation shall include a configuration list. acm cap.2.4cThe configuration list shall describe the configuration items that comprise the TOE. acm cap.2.5c The CM documentation shall describe the method used to uniquely identify the configuration items. acm cap.2.6c The CM system shall uniquely identify all configuration items. Evaluator action elements: acm cap.2.1e The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. ACM CAP.3 Authorisation controls Objectives A unique reference is required to ensure that there is no ambiguity in terms of which instance of the TOE is being evaluated. Labelling the TOE with its reference ensures that users of the TOE can be aware of which instance of the TOE they are using. Unique identification of the configuration items leads to a clearer understanding of the composition of the TOE, which in turn helps to determine those items which are subject to the evaluation requirements for the TOE. Providing controls to ensure that unauthorised modifications are not made to the TOE, and ensuring proper functionality and use of the CM system, helps to maintain the integrity of the TOE. Dependencies: ACM SCp.1 TOE CM coverage ALC DVS.1 Identification of security measures Developer action elements: acm cap.3.1d The developer shall provide a reference for the TOE. acm cap.3.2d The developer shall use a CM system. acm cap.3.3d The developer shall provide CM documentation. Content and presentation of evidence elements: acm cap.3.ic The reference for the TOE shall be unique to each version of the TOE. acm cap.3.2c The TOE shall be labelled with its reference. acm cap.3.3c The CM documentation shall include a configuration list and a CM plan. acm cap.3.4c The configuration list shall describe the configuration items that comprise the TOE. acm cap.3.5c The CM documentation shall describe the method used to uniquely identify the configuration items. acm cap.3.6c The CM system shall uniquely identify all configuration items. acm cap.3.7c The CM plan shall describe how the CM system is used. acm cap.3.8c The evidence shall demonstrate that the CM system is operating in accordance with the cM plan. acm cap.3.9c The CM documentation shall provide evidence that all configuration items have been and are being effectively maintained under the cM system. acm cap.3.ioc The CM system shall provide measures such that only authorised changes are made to the configuration items. Evaluator action elements: acm cap.3.ie The evaluator shall confirm that the information provided meets all requirements for content and presentation of evidence. ACM CAP.4 Generation support and acceptance procedures Objectives A unique reference is required to ensure that there is no ambiguity in terms of which instance of the TOE is being evaluated. Labelling the TOE with its reference ensures that users of the TOE can be aware of which instance of the TOE they are using. Unique identification of the configuration items leads to a clearer understanding of the composition of the TOE, which in turn helps to determine those items which are subject to the evaluation requirements for the TOE. Providing controls to ensure that unauthorised modifications are not made to the TOE, and ensuring proper functionality and use of the CM system, helps to maintain the integrity of the TOE. The purpose of acceptance procedures is to confirm that any creation or modification of configuration items is authorised. Dependencies: ACMSCP.1 TOE CM coverage ALCDVS. 1 Identification of security measures Developer action elements: acm cap.4.id The developer shall provide a reference for the TOE. acm cap.4.2d The developer shall use a CM system. acm cap.4.3d The developer shall provide CM documentation. Content and presentation of evidence elements: acm cap.4.ic The reference for the TOE shall be unique to each version of the TOE. acm cap.4.2c The TOE shall be labelled with its reference. acm cap.4.3c The CM documentation shall include a configuration list, a CM plan, and an acceptance plan. acm cap.4.4c The configuration list shall describe the configuration items that comprise the TOE. acm cap.4.5c The CM documentation shall describe the method used to uniquely identify the configuration items. acm cap.4.6c The CM system shall uniquely identify all configuration items. acm cap.4.7c The CM plan shall describe how the CM system is used. acm cap.4.8c The evidence shall demonstrate that the CM system is operating in accordance with the CM plan. acm cap.4.9c The CM documentation shall provide evidence that all configuration items have been and are being effectively maintained under the CM system. acm cap.4.i0c The CM system shall provide measures such that only authorised changes are made to the configuration items. acm cap.4.iic The CM system shall support the generation of the TOE. acm cap.4.i2c The acceptance plan shall describe the procedures used to accept modified or newly created configuration items as part of the TOE. Evaluator action elements: 0 ... 25 26 27 28 29 30 31 ... 73
|
