GB/T 18336.2-2024Cybersecurity technology—Evaluation criteria for IT security—Part 2: Security functional components (English PDF)

Foreword

GB/T 18336 "Information technology - Security techniques - Evaluation criteria for IT security" includes the following 3 parts.

-- Part 1: Introduction and general model;

-- Part 2: Security functional components;

-- Part 3: Security assurance components.

This Part is part 2 of GB/T 18336.

This Part is drafted in accordance with specifications in GB/T1.1-2009.

This Part shall replace GB/T 18336.2-2008 "Information technology - Security techniques - Evaluation criteria for IT security - Part 2: Security functional components".

The main differences between this Part and GB/T 18336.2-2008 are as follows.

— "assurance" is replaced by "assurance" [Translator note. This is mainly adjustment on Chinese. In English, the same word "assurance" should remain the most appropriate, given that "Assurance" is still used in the corresponding ISO/IEC 15408-2:2008.This translation still uses the term "Assurance"];

— "10.4 Export outside TSF control (FDP_ETC)" is amended as "10.4 Export from TOE (FDP_ETC)";

— "10.7 Import from outside TSF control(FDP_ITC)" is amended as" 10.7 Import from outside TOE (FDP_ITC)";

— "14.1 Bottom abstract machine test (FPT_AMT)", "14.10 Referring to arbitration (FTP_RVM)" and "14.11 Domain separation" in "14 FPT class. TSF protection" are deleted;

— "14.12 Test of external entity(FPT_TEE)" is added in "14 FPT class. TSF protection";

— "16.3 Session lock (FTA_SSL)" is amended as "16.3 Session lock and termination(FTA_SSL)";

— "threshold value" is replace by "critical value" [Translator note. As the corresponding ISO/IEC 15408-2:2008 still uses term "Threshold value", this translation follows the term "Threshold value", given that "This Part uses translation method to equivalently adopt the international standard ISO/IEC 15408-2:2008"];

— "mediate" is replaced by "promote" [Translator note. This is mainly adjustment on Chinese. In English, the same word "mediate" should remain the most appropriate, given that "Mediate" is still used in the corresponding ISO/IEC 15408-2:2008.This translation still uses the term "Mediate"];

This Part uses translation method to equivalently adopt the international standard ISO/IEC 15408-1:2008 "Information technology - Security techniques - Evaluation criteria for IT security – Part 2: Security functional components".

The domestic documents that are consistently corresponding to the normative international references in this Part are as follows.

— GB/T 18336.1 "Information technology - Security techniques - Evaluation criteria for IT security Part 1: Introduction and general model". (GB/T 18336.1-2015, ISO/IEC 15408-1:2009, IDT)" this Part has the following editorial amendments.

— There is editorial error in the original text of sub-clause 4.1; it is now amended as "Those who author PP or ST should refer to clause 3 and relevant annexes of ISO/IEC 15408-1 for relevant structures, rules, and guidance".

This Part was proposed by and shall be under the jurisdiction of China Information Security Standardization Technical Committee (SAC/TC 260).

The main drafting organizations of this Part. China Information Technology Security Evaluation Centre, Information Technology Security Test and Evaluation Centre, The Third Research Institute of Ministry of Public Security AND China Information Technology Security Evaluation Centre Jilin Centre.

Introduction

Security functional components, as defined in this Part, are the basis for the security functional requirements expressed in a Protection Profile (PP) or a Security Target (ST).

These requirements describe the desired security behaviour expected of a Target of Evaluation (TOE) and are intended to meet the security objectives as stated in a PP or an ST. These requirements describe security properties that users can detect by direct interaction (i.e. inputs, outputs) with the IT or by the IT response to stimulus.

Security functional components express security requirements intended to counter threats in the assumed operating environment of the TOE and/or cover any identified organisational security policies and assumptions.

The audience for this Part includes consumers, developers, and evaluators of secure IT products. ISO/IEC 15408-1 Clause 5 provides additional information on the target audience of ISO/IEC 15408, and on the use of ISO/IEC 15408 by the groups that comprise the target audience. These groups may use this Part as follows.

a) Consumers, who use this Part when selecting components to express functional requirements to satisfy the security objectives expressed in a PP or ST. ISO/IEC 15408-1 provides more detailed information on the relationship between security objectives and security requirements.

b) Developers, who respond to actual or perceived consumer security requirements in constructing a TOE, may find a standardised method to understand those requirements in this Part. They can also use the contents of this Part as a basis for further defining the TOE security functionality and mechanisms that comply with those requirements.

c) Evaluators, who use the functional requirements defined in this Part in verifying that the TOE functional requirements expressed in the PP or ST satisfy the IT security objectives and that all dependencies are accounted for and shown to be satisfied.

Evaluators also should use this Part to assist in determining whether a given TOE satisfies stated requirements.

Information technology - Security techniques -Evaluation criteria for IT security - Part 2: Security functional components

1 Scope

This Part of GB/T 18336 defines the required structure and content of security functional components for the purpose of security evaluation. It includes a catalogue of functional components that will meet the common security functionality requirements of many IT products.

2 Normative references

The articles contained in the following documents have become part of this document when they are quoted herein. For the dated documents so quoted, all the modifications (including all corrections) or revisions made thereafter shall be applicable to this document.

ISO/IEC 15408-1, Information technology - Security techniques - Evaluation criteria for IT security - Part 1: Introduction and general model

3 Terms and definitions

For the purposes of this document, the following terms and definitions given in ISO/IEC 15408-1 apply.

4 Overview

ISO/IEC 15408 and the associated security functional requirements described herein are not meant to be a definitive answer to all the problems of IT security. Rather, this standard offers a set of well understood security functional requirements that can be used to create trusted products reflecting the needs of the market. These security functional requirements are presented as the current state of the art in requirements specification and evaluation.

This Part does not presume to include all possible security functional requirements but rather contains those that are known and agreed to be of value by this Part's authors at the time of release.

Since the understanding and needs of consumers may change, the functional requirements in this Part will need to be maintained. It is envisioned that some PP/ST authors may have security needs not (yet) covered by the functional requirement this component should be used when a trusted communication channel between the TSF and another trusted IT product is required.

M.1.2.2 Operations

M.1.2.2.1 Selection

In FTP_ITC.1.2, the PP/ST author must specify whether the local TSF, another trusted IT product, or both shall have the capability to initiate the trusted channel.

M.1.2.2.2 Assignment in FTP_ITC.1.3, the PP/ST author should specify the functions for which a trusted channel is required. Examples of these functions may include transfer of user, subject, and/or object security attributes and ensuring consistency of TSF data.

M.2 Trusted path (FTP_TRP) M.2.1 User notes this family defines the requirements to establish and maintain trusted communication to or from users and the TSF. A trusted path may be required for any security-relevant interaction. Trusted path exchanges may be initiated by a user during an interaction with the TSF, or the TSF may establish communication with the user via a trusted path.

M.2.2 FTP_TRP.1 Trusted path M.2.2.1 User application notes this component should be used when trusted communication between a user and the TSF is required, either for initial authentication purposes only or for additional specified user operations.

M.2.2.2 Operations

M.2.2.2.1 Selection

In FTP_TRP.1.1, the PP/ST author should specify whether the trusted path must be extended to remote and/or local users.

In FTP_TRP.1.1, the PP/ST author should specify whether the trusted path shall protect the data from modification, disclosure, and/or other types of integrity or confidentiality violation.

M.2.2.2.2 Assignment ......