GB/T 20272-2019Information security technology—Security technical requirements for operating system (English PDF)

3.1 Security of operating system

The confidentiality, integrity, and availability of operating system itself and of the information it stores, transmits, and processes.

3.2 Security subsystem of operating system

The general term for security protection devices in an operating system, including hardware, firmware, software, and a combination responsible for implementing security policies.

6.1 Class 1.user self-protection class

6.1.1 Security function requirements

6.1.1.1 Identity authentication

The identity authentication functions of SSOOS are as follows. […]

6.1.1.2 Discretionary access control

The discretionary access control functions of SSOOS are as follows. […]

6.1.1.3 Data integrity

For user data transmitted internally the operating system (such as inter-process communication), there shall be a function of ensuring the integrity of user data.

6.1.1.4 Network security protection

SUPPORT two-way network access control based on IP address, port, and physical interface. DISCARD packets which do not meet the pre-defined policy.

6.1.2 Self-security requirements

6.1.2.1 Operation security protection

The operation security protection functions of SSF are as follows. […]

6.1.2.2 Resource utilization

6.1.2.2.1 Fault tolerance

Certain measures shall be taken to ensure that the SSF can maintain normal operation when certain deterministic fault conditions occur in the system.

6.1.2.4 Security policy configuration

Security policy configuration functions shall be provided for identity authentication, network security protection, resource utilization, and user login access control.

6.1.3 Security assurance requirements

6.1.3.1 Development

6.1.3.2 Guiding document

6.1.3.3 Life cycle support

6.1.3.4 Testing

6.1.3.4.1 Coverage

The developer shall provide a testing coverage document. The evidence of the testing coverage shall indicate the correspondence between the testing in the testing document and the SSOOS interface in the functional specification description.

6.1.3.4.2 Functional testing

Developers shall test SSF and self-security protection functions. The testing document shall include the following. […]

6.1.3.4.4 Cryptographic testing

Developers shall test the correctness and compliance of the symmetric, asymmetric, and hash cryptographic algorithms used, to ensure that the actual operation results are consistent with the expected correct results.

Developers shall ensure that symmetric, asymmetric, and hash cryptographic algorithms which comply with national cryptography-related regulations are used.

6.1.3.5 Vulnerability evaluation

Based on the identified potential vulnerabilities, the operating system shall resist attacks by attackers with a basic attack potential.

Note: The resisting to attacks by attackers with basic attack potential needs to be comprehensively considered based on the following 5 specific factors. attack time, attacker ability, level of understanding of the operating system, time of access to operating system or number of attack samples, attack equipment used. See GB/T 30270-2013 Appendix A, A.8.

6.2 Class 2.system audit protection class

6.2.1 Security function requirements

6.2.1.1 Identity authentication

The identity authentication functions of SSOOS are as follows. […]

6.2.2 Self-security requirements

6.2.2.1 Operation security protection

The operation security protection functions of SSF are as follows. […]

6.2.2.2 Resource utilization

6.2.2.2.1 Fault tolerance

The fault tolerance functions of SSOOS are as follows. […]

6.2.2.2.2 Service priority

The service priority functions of SSOOS are as follows.

a) The service priority policy shall be adopted to set the subject to use the priority of a subset of resources within the SSF control scope to manage and allocate operating system resources;

b) It shall be ensured that access to all operating system resources is based on the priority set by the subject.

6.2.2.2.3 Resource allocation

The resource allocation functions of SSOOS are as follows.

a) In accordance with the requirements of 5.1.4.2 a) maximum quota resource allocation in GB/T 20271-2006, it shall carry out the management and allocation of operating system resources. The quota mechanism ensures that users and subjects will not monopolize certain controlled resources.

b) It shall be ensured that, when an authorized subject makes a request, resources can be accessed and utilized.

c) It shall, based on each user or each user group, provide a mechanism, to control its consumption of disks and the use of resources such as CPU.

6.2.2.3 User login access control

The user login access control functions of SSOOS are as follows. […]

6.2.2.4 Trusted measurement

The trusted measurement functions of SSOOS are as follows. […]

6.2.2.5 Security policy configuration

Security policy configuration functions shall be provided for identity authentication, security audit, network security protection, resource utilization, and user login access control.

6.2.3 Security assurance requirements

6.2.3.1 Development

6.3 Class 3.security label protection class

6.3.2 Self-security requirements

6.3.2.1 Operation security protection

The operation security protection functions of SSF are as follows. […]

6.3.2.2 Resource utilization

6.3.2.2.1 Fault tolerance

The fault tolerance functions of SSOOS are as follows. […]

6.3.3 Security assurance requirements

6.3.3.1 Development

6.3.3.1.1 Security architecture

The developer shall provide the security architecture description document of SSOOS. The security architecture description document shall meet the following requirements. […]

6.4 Class 4.structured protection class

6.4.1 Security function requirements

6.4.1.1 Identity authentication

The identity authentication functions of SSOOS are as follows. […]

6.5 Class 5.access verification protection class

6.5.3 Security assurance requirements

6.5.3.4 Testing

6.5.3.4.1 Coverage

The developer shall provide a testing coverage document. The testing coverage document shall meet the following requirements. […]

6.5.3.4.3 Functional testing

Developers shall test SSF and self-security protection functions. The testing document shall include the following. […]

6.5.3.4.4 Independent testing

Developers shall provide a set of equivalent resources as they used in self-tests, for testing of SSOOS.

6.5.3.4.5 Cryptographic testing

Developers shall test the correctness and compliance of the symmetric, asymmetric, and hash cryptographic algorithms used, to ensure that the actual operation results are consistent with the expected correct results.

Developers shall ensure that symmetric, asymmetric, and hash cryptographic algorithms which comply with national cryptography-related regulations are used.

6.5.3.4.6 Code security testing

The developer shall perform a security testing on the SSOOS implementation representation and the operating system kernel code, to confirm that there are no security flaws or backdoors in the code.

6.5.3.5 Vulnerability evaluation

Developers shall assess the vulnerability of the operating system in the following ways. […]