Additionally, where an EAL rating is mandated for a product to perform a cryptographic function for the protection of data at rest or in transit, as specified within Chapter 17 – Cryptography, products that have not completed an Approved Evaluation do not satisfy the requirement. 12.1.30.C.01. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST [CID:3284] Agencies MUST select products in the following order of preference: a protection profile (PP) evaluated product; products having completed an evaluation through the AISEP or recognised under the Common Criteria Recognition Arrangement (CCRA); products in evaluation in the AISEP; products in evaluation in a scheme where the outcome will be recognised by the GCSB when the evaluation is complete; or If products do not fall within any of these categories, contact the GCSB. 12.1.30.C.02. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST [CID:3286] When choosing a product, agencies MUST document the justification for any decision to choose a product that is still in evaluation and accept any security risk introduced by the use of such a product. 12.1.30.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:3287] Agencies SHOULD select products in the following order of preference: a protection profile (PP) evaluated product; products having completed an evaluation through the AISEP or recognised under the Common Criteria Recognition Arrangement (CCRA); products in evaluation in the AISEP; products in evaluation in a scheme where the outcome will be recognised by the GCSB when the evaluation is complete; or If products do not fall within any of these categories, normal selection criteria (such as functionality and security) will apply. 12.1.31. Evaluated product selection 12.1.31.R.01. Rationale A product listed on the EPL might not meet the security requirements of an agency. This could occur for a number of reasons, including that the scope of the evaluation is inappropriate for the intended use or the operational environment differs from that assumed in the evaluation. As such, an agency should ensure that a product is suitable by reviewing all available documentation. In the case of Common Criteria certified products, this documentation includes the protection profile, target of evaluation, security target, certification report, consumer guide and any qualifications and limitations contained in the entry on the EPL. 12.1.31.R.02. Rationale Products that are in evaluation will not have a certification report and may not have a published security target. A protection profile will, as a rule, exist. A draft security target can be obtained from the GCSB for products that are in evaluation through AISEP. For products that are in evaluation through a foreign scheme, the vendor can be contacted directly for further information. 12.1.31.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:3294] Agencies SHOULD select products that have their desired security functionality within the scope of the product’s evaluation and are applicable to the agency’s intended environment. 12.1.32. Product specific requirements 12.1.32.R.01. Rationale Whilst this manual may recommend a minimum level of assurance in the evaluation of a product’s security functionality not all evaluated products may be found suitable for their intended purpose even if they pass their Common Criteria evaluation. Typically such products will have cryptographic functionality that is not covered in sufficient depth under the Common Criteria. Where products have specific usage requirements, in addition to this manual, or supersede requirements in this manual, they will be outlined in the product’s consumer guide. 12.1.32.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:3299] Agencies MUST check consumer guides for products, where available, to determine any product specific requirements. 12.1.32.C.02. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:3304] Where product specific requirements exist in a consumer guide, agencies MUST comply with the requirements outlined in the consumer guide. 12.1.32.C.03. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:3306] Agencies selecting high assurance products and HGCE MUST contact the GCSB and comply with any product specific requirements, before any purchase is made. 12.1.33. Sourcing non-evaluated software 12.1.33.R.01. Rationale Software downloaded from websites on the Internet can contain malicious code or malicious content that is installed along with the legitimate software. Agencies need to confirm the integrity of the software they are installing before deploying it on a system to ensure that no unintended software is installed at the same time. 12.1.33.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:3310] Agencies SHOULD: obtain software from verifiable sources and verify its integrity using vendor supplied checksums; and validate the software’s interaction with the operating systems and network within a test environment prior to use on operational systems. 12.1.34. Delivery of evaluated products 155 Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents