Valid

GB/T 47686-2026Cybersecurity technology — Requirements for the security configuration baseline of government clouds (English PDF)

网络安全技术 政务云安全配置基线要求

Preview PDF

This is a limited preview

Buy now to download the full PDF (35 pages)

Need quotation for your management?

Get a formal quotation for GB/T 47686-2026 in 30 minutes.

Issued by

SAMR; SAC

Level / Type

National · Recommended

Issue date

May 25, 2026

Implementation date

December 1, 2026

Scope

GB/T 47686-2026 is the English-translated version of 网络安全技术 政务云安全配置基线要求.

GB/T 47686-2026 sets the security configuration baseline for the key components of a government cloud.

Clause 1 names six of them - the cloud management platform, the host operating system, containers, virtual machines, databases and cloud security components - and the preview carries the requirements for the first three: for the cloud management platform, system, network and storage virtualization management, remote access, communication protection, session security, identity authentication, residual information protection, logging and audit, API access security, monitoring alarms, cross-cloud migration and baseline management; for the host operating system, general hardening, network services and account and password security; for containers, host and daemon configuration.

Its overview states that the configuration should in principle meet at least level 3 of the classified protection system. Issued on 25 May 2026, it applies from 1 December 2026.

Found what you need?

Document preview — GB/T 47686-2026

National Standard of the People's Republic of China

ICS
35.030
Classification
L 70

Issued by: State Administration for Market Regulation; Standardization Administration of the PRC

Contents

  • 1 Scope
  • 4 Abbreviations
  • 5 Overview
  • 6 Security Configuration Requirements for Cloud Management Platform
  • 7 Host Operating System Security Configuration Requirements
  • 8 Container security configuration requirements

1 Scope

This document specifies the key components of the government cloud, including the cloud management platform, host operating system, containers, virtual machines, databases, and cloud security components. Safety configuration baseline requirements for components.

This document is intended to guide the construction, operation, management, and testing of government cloud security capabilities.

4 Abbreviations

The following abbreviations apply to this document.

ACL. Access Control List

API. Application Programming Interface

ASLR. Address Space Layout Randomization

CPU. Central Processing Unit

CUPS. Common Unix Printing System

DHCP. Dynamic Host Configuration Protocol

DNS. Domain Name System

FTP. File Transfer Protocol

FTPS. Secure File Transfer Protocol

HTTP. Hypertext Transfer Protocol

HTTPS. Hypertext Transfer Protocol Secure

IAM. Identity and Access Management

ICMP. Internet Control Message Protocol

IOPS. Input and output per second.

IPC. Inter-process communication

LDAP. Lightweight Directory Access Protocol

NFS. Network File System

NIS. Network Information Service

OS. Operating System

PAM. Pluggable Authentication Modules

PID. Process Identifier

PKI. Public Key Infrastructure

RBAC. Role-based access control

RDP. Remote Desktop Protocol

RPM. Red Hat Package Manager

SCA. Software Composition Analysis

5 Overview

5.1 Government Cloud Network Reference Architecture

The government cloud is used to host the portal websites, government business application systems, and government data of government departments at all levels, for government office work and public services.

The government cloud provides services such as public services, data management, mobile government affairs, and regulatory enforcement. The network reference architecture for the government cloud is shown in Figure 1. Typical government services on the government cloud are illustrated in Figure 1. See Appendix A for service types.

The primary users of the government cloud are government departments at all levels. It connects to government units at various levels through government networks and utilizes the computing power on the government cloud.

It utilizes computing, networking, storage, and security resources to support various government information systems and government data, enabling government personnel to carry out various government activities. To provide government services to the public.

The large-scale construction of government clouds and the centralized deployment of government applications on the cloud have made the security risks faced by government clouds more complex, and their main security risks are... See Appendix B for full risk assessment. By proposing security configuration requirements for key components of the government cloud, the security strength of each key component is strengthened, and the risk of various groups is reduced.

This addresses the security risks arising from missing or improper configurations, thereby ensuring the secure operation of the entire government cloud and cloud-based government applications.

5.2 Key Component Architecture of Government Cloud

The government cloud components include cloud management-side components and cloud tenant-side components. The cloud management-side components include the cloud management platform, host operating system, and capacity... Six types of components, including servers, virtual machines, databases, and cloud security components, are key components of the government cloud, collectively constituting its core capabilities.

The architecture is shown in Figure 2. Each key component virtualizes the computing, network, and storage resources of the government cloud, and manages virtual machines through deployment and management.

Container and cloud management platforms enable cloud resource scheduling and operation and maintenance, while cloud security components provide cloud platform security capabilities.

Cloud tenant-side components mainly include virtual machines, containers, and databases, primarily hosting the cloud tenant's business applications and data. Cloud tenant-side components can be referenced... In accordance with the security configuration requirements of key components on the management side, strengthen the security configuration management of virtual machines, containers, and databases.

The security configuration of key components of the government cloud should, in principle, meet at least Level 3 of the Cybersecurity Classified Protection System and the Enhanced Level of the Cloud Computing Security Assessment. Requirements for security assessment of commercial cryptography applications.

6 Security Configuration Requirements for Cloud Management Platform

6.1 System Virtualization Management

The requirements for system virtualization management include the following.

a) Implement integrity checks for virtual machine images and snapshot files to prevent malicious tampering. If necessary, protect private virtual machine images. Configure encryption measures for the virtual machine image.

b) Perform integrity checks on important data configurations such as virtual machine template files and configuration files.

c) Virtual mirror templates should be configured correctly, and the template lineage should be clearly defined.

d) Resource isolation should be provided for the virtualization platform, and virtual machines should only be able to access the physical storage space allocated to them.

e) Resource isolation should be provided for the virtualization platform to achieve virtual central processing unit (vCPU) instruction isolation between different virtual machines.

It is isolated from memory, so that the crash of a virtual machine does not affect the virtual machine monitor and other virtual machines.

f) Virtual machine security isolation should be provided, and security isolation measures between virtual machines and physical machines should be provided at the virtual machine monitor layer to control virtual machines.

All data communication between machines and between virtual machines and physical machines is prevented from virtual escape.

g) An alarm policy should be set to issue timely alarms when resources exceed the threshold or resource isolation fails.

h) Detect and alert on unauthorized new virtual machines, unauthorized configuration changes, or re-enabling of virtual machines.

i) Policies should be set to prevent unauthorized access to virtual machine image file data.

j) A mechanism for separating the permissions of virtualization platform operation administrators should be set up to prevent situations such as unauthorized or excessive management.

k) Protection measures should be in place during the migration of virtual machines across physical machines, and access control policies should be able to be migrated along with the virtual machine during migration.

l) It should have the ability to specify or limit the range of physical machines where virtual machines reside.

m) Measures should be taken to ensure that the memory of a virtual machine is fully released before it is released or reallocated to other virtual machines.

6.2 Network Virtualization Management

Network virtualization management requirements include the following.

a) Configure logical network isolation to address access to virtual network resources between different tenants, meeting the network isolation requirements between different tenants. And provide access control measures.

b) Network isolation and access control measures should be set up for different services of the same tenant.

c) Manage the bandwidth of the virtual machine network interface.

d) Access control measures should be deployed at the boundaries of network zones of different levels, and access control rules should be set, such as using firewalls or network gateways.

Access control is implemented using security equipment. In principle, the security level of public areas is higher than that of internet areas, and the security level of managed areas is higher than... Business area.

e) A virtualized load balancing solution should be provided for tenant services.

f) High-risk ports should not be accessed via the internet, such as SSH (port 22), FTP (port 21), LDAP (port 389), and RDP (port 22).

3389), SMB (port 445), MySQL (port 3306), Redis (port 6379), Docker (port 2375), Elastic-search (port 9200), etc.

g) Network ACL rules or security groups should be configured to strictly restrict high-risk ports listed in the inbound rules. If opening is necessary for business operations... It should be set according to the principle of minimizing openness.

h) The flow of customer and other important information on the cloud platform to overseas entities should be restricted.

6.3 Storage Virtualization Management

Storage virtualization management requirements include.

a) Security controls for stored data should be applicable to both logical and physical storage entities, and should not be limited by the physical storage location of the information. The change resulted in the bypassing of safety control measures;

b) Logically isolate the virtual storage resources used by different cloud service tenants;

c) Virtual storage data auditing measures should be provided to audit the mounting and operation of user storage;

d) Virtual storage data access control measures should be configured to prevent or restrict direct access to physical storage entities, such as employing authentication, Authorized access, security tags, data encryption, and other measures;

e) Virtual storage redundancy backup measures should be configured to enable recovery from redundant backup data, such as cluster deployment and image recovery;

f) Storage protocol-level data access authorization policies should be set, such as implementing storage protocols like Internet Small Computer System Interface (iSCSI). Level of security control;

g) Support should be provided for the use of third-party encryption and key management measures, allowing customers to deploy data encryption products that comply with national cryptographic management requirements.

Products should be stored in encrypted form on a cloud platform.

6.4 Remote Access

Remote access requirements include.

a) Cryptographic measures that comply with national cryptographic management requirements should be used to ensure the confidentiality, integrity, and authenticity of remote access sessions;

b) Access to the cloud computing platform by local and remote terminal devices should be restricted;

c) All remote access should only be permitted through a limited number of managed access control points;

d) Secure network protocols should be used when accessing remotely, such as using SFTP/SFTP instead of FTP, and SSH instead of remote login.

(Telnet), HTTPS instead of HTTP, SMTPS instead of SMTP, WebSockets over TLS instead of WebSockets, etc.;

e) When performing remote maintenance and management on the cloud platform, it is important to prevent remote management devices from directly connecting to other network resources at the same time;

f) When remotely managing devices in a cloud platform, a two-way authentication mechanism should be established between the management terminal and the cloud computing platform;

g) Restrict privileged commands executed during remote management, such as virtual machine deletion and restart, and take protective measures. An audit will be conducted.

6.5 Communication Protection

Communication protection requirements include.

a) It should be able to uniformly manage, schedule, and allocate physical and virtual resources according to policies;

b) Cloud platform management traffic should be separated from customer business traffic, for example, by configuring independent management networks and business networks. Network isolation is implemented;

c) Management commands for the virtualization platform should be transmitted in an encrypted manner;

d) The cloud computing platform should establish an independent operation and maintenance network partition, and deploy a resource management platform, operation and maintenance management system, security operation center, etc. Implement operation and maintenance management;

e) Centralized control capabilities should be provided, including system management, audit management, and security management;

f) Log data and monitoring traffic data generated by the cloud platform should be configured for centralized storage;

g) Real-time monitoring of cloud platform computing and storage resources should be conducted, with monitoring metrics including the total number of host machines and the total number of virtual machines.

Quantity, total number of virtual CPU cores, number of allocated cores, CPU resource consumption, total storage capacity, allocated capacity, and storage consumption.

Status, total memory capacity, allocated capacity, memory usage, cloud storage read/write IOPS, cloud storage read/write utilization, physical hard disk Utilization rate, physical hard drive read/write IOPS, etc.;

h) Real-time monitoring of the cloud platform's network resources should be conducted, including monitoring items such as network bandwidth utilization, network traffic, and network latency.

Network inbound bandwidth, network outbound bandwidth, outbound network inbound rate, outbound network outbound rate, number of network connections, etc.

6.6 Session Security

Session security requirements include.

a) The session identifier should be invalidated when the user logs out or the session terminates;

b) A user session timeout policy should be set, such as the session expiring if a user remains inactive for more than 30 minutes and must log in again;

c) The account ID of the cloud management platform should be unique, and the same account should not be logged in multiple times on the platform at the same time.

6.7 Identity Authentication

Identity verification requirements include.

a) The cloud platform should manage accounts uniformly through a unified identity authentication service (such as IAM), enabling the allocation of different accounts to different roles. Permissions, such as regular administrator, audit administrator, security administrator, etc.;

b) The cloud management platform should perform credential authentication based on passwords, hardware tokens, or PKI, and the relevant cryptographic measures should comply with national cryptographic management regulations. Require;

c) The password must be at least 8 characters long and must include at least numbers, uppercase and lowercase letters, and special symbols;

d) Users cannot change their passwords to old passwords that have been used more than 5 times in the past when updating their passwords;

e) Encryption algorithms that comply with national cryptographic management requirements should be used to encrypt stored passwords, and HTTPS, SSH, or other similar methods should be used. Transmit password;

f) The password should not be used for more than 90 days.

g) The use of default super administrator accounts, such as Admin and root, should be restricted;

h) An account lockout policy should be set, such as locking the user for 10 minutes if they fail to log in more than five times within 5 minutes;

i) An account session timeout policy should be set so that if a user is inactive within a specified session threshold, the session will expire and the user should log in again.

6.8 Protection of Residual Information

Residual information protection requirements include.

a) After a cloud tenant releases a storage resource, all data on the released storage resource should be completely erased from the physical storage.

Image files and snapshot files can be completely deleted after migrating or deleting a virtual machine;

b) When a cloud tenant deletes business application data, all copies stored in the cloud platform should be deleted, including local backups and off-site backups. Copy;

c) Before a faulty physical storage medium leaves the cloud platform (e.g., is returned to the factory), effective technical means such as data erasure and physical demagnetization should be used to remove the data. According to reports, to avoid data leaks;

d) To prevent accidental deletion of backup data, a secondary confirmation policy can be configured.

6.9 Logs and Audits

Log and audit requirements include.

a) A unified system clock should be configured within the cloud platform to generate timestamps for audit records;

b) Audit logs generated by the cloud platform should include the event type, the time and location of the event, the source of the event, the outcome of the event, and related information.

The identity of the user or subject involved in the event, as well as the session, connection, transaction, activity duration, number of bytes received and sent, and usage.

Additional information messages for diagnosing or identifying events, and information used to describe and identify the characteristics of objects or resources involved in the action;

c) Audit logs generated by the cloud platform should be stored for no less than 6 months; logs related to internet-based government applications should be retained. The time frame should be no less than one year;

d) The audit process should be protected from interruption by unauthorized accounts.

e) It should be possible to configure log transfer for log data generated by the cloud platform to facilitate long-term storage and big data analysis of log data;

f) Database auditing policies should be enabled for the cloud platform's databases;

g) Configure integrity checks for critical audit data to prevent tampering with critical audit data;

h) An audit failure alarm policy and an audit log storage capacity threshold (e.g., exceeding 80%) alarm policy should be set.

6.10 API Access Security

API access security requirements include.

a) User authentication and authorization should be configured before making service API calls;

b) A secure transmission policy should be configured for the service API;

c) Security policies such as protection against replay attacks, code injection, and DoS/DDoS attacks should be configured for the service API;

d) Service API overload protection policies should be set up to ensure fairness in business operations among users of different service levels and optimal utilization of system resources. Taika;

e) A call logging policy for the service API should be configured, and the API call frequency and abnormal behavior should be monitored;

f) A time threshold should be set to disable API keys that have not been used for more than 180 days.

6.11 Monitoring Alarm

Monitoring and alarm requirements include.

a) Rules should be configured to trigger alarms to identify unauthorized activities and anomalous events;

b) Alarm trigger thresholds should be set for both physical and virtual resources;

c) When creating alert rules, an input validation policy based on the prompt should be set to prevent malicious attacks or input errors. question.

6.12 Cross-cloud migration requirements

Cross-cloud migration requirements include.

a) All or critical business data from the source cloud platform should be backed up, including virtual machines, databases, service lists, and accounts;

b) The computing resources, storage resources, network resources, security resources, and operational status of the target cloud platform should be verified, including but not limited to... Regarding hardware and software resource specifications, resource configuration, network allocation, and connectivity;

c) Verify the network connection (such as a physical leased line or VPN) between the source cloud platform and the target cloud platform, including but not limited to migration.

Access points, dedicated line gateways, dedicated line ports, and capacities of the outgoing and incoming computer rooms;

d) A suitable time window should be selected for service switching based on factors such as business traffic models and load conditions, such as traffic troughs, etc. Off-peak periods, etc.;

e) The migration of business applications should be carried out by choosing between stopping or not stopping service, depending on the factors affecting business operations;

f) A business transition strategy and implementation plan should be developed, including but not limited to the business transition method (e.g., switching applications first and then data).

(Switching data and data simultaneously), data migration methods (such as full migration, incremental migration), switchover duration, rollback plan, etc.;

g) After cross-cloud migration is completed, verify whether the application is running normally and whether the data is consistent on the target cloud platform, and conduct continuous and uninterrupted monitoring. Control system operation status.

6.13 Security Configuration Baseline Management

The requirements for security configuration baseline management include the following.

a) A configuration management plan for the cloud management platform should be developed and implemented, including the roles and responsibilities of configuration administrators and the configuration change management workflow.

The process includes the management of configuration parameters and baseline configuration, as well as the management process of information system component lists.

b) The cloud management platform and its hardware, software, firmware, and other configuration files and records should be backed up regularly (e.g., monthly/before changes are implemented/updates).

After the component is installed, the relevant configuration can be restored if necessary.

c) Security configuration baselines should be approved before they take effect.

d) Security configuration baseline suitability assessments should be conducted regularly, and updated promptly based on changes in business architecture, threat landscape, regulatory requirements, etc. New baseline content.

e) A baseline review should be triggered after a major security incident.

f) The validity period of the baseline version should be monitored, and a timely warning should be issued before the expiration date. Systems affected by the expired baseline should complete adaptation or maintenance within the transition period. Migrants.

g) When a security configuration baseline is deprecated, the scope of impact should be assessed. If the baseline is completely replaced by a new version and has no historical system dependencies, deprecation can be initiated.

The application was terminated and, after approval, was announced as invalid.

h) Baseline documents should include a version number, effective date, revision history, and a summary of changes. Older versions of baseline documents should be retained for at least 3 years.

i) The controlled configuration list of the cloud management platform should be clearly defined and changed regularly, such as updating it monthly or starting a new scan.

Before the description, after the new rule base is released, etc.

j) Before implementing baseline configuration changes, considerations should be given to change success rate, change complexity, security policy, rollback plan, business impact, and timeliness.

Controlled configuration changes should be analyzed and reviewed, including aspects such as time windows. If necessary, controlled configuration changes should be tested in advance. And verification.

k) When implementing changes, the change process and change plan should be strictly followed. If necessary, privileged command operations may be subject to secondary approval.

l) An audit of the change operation should be conducted promptly after the change is implemented.

7 Host Operating System Security Configuration Requirements

7.1 General Reinforcement

General reinforcement requirements include.

a) Common processes should be hardened, such as by enabling ASLR and linker protection, in accordance with C.1 requirements;

b) Access control policies should be configured to restrict the storage of critical system files such as user account information, password information, user group information, and log auditing information. Access permissions for the file;

c) Privilege escalation should be configured so that regular users can only escalate privileges by providing a password, preventing privilege escalation without password verification;

d) The latest operating system patches should be updated and installed promptly to fix known operating system vulnerabilities;

e) The system firewall content should be optimized;

f) It should comply with the malicious code protection requirements in section 7.9 of GB/T 31168-2023;

g) Critical directories of the system should be partitioned and mounted, and operating system data should be partitioned from business data according to the characteristics of the business.

Manage your data carefully and avoid storing all data on a single disk or partition.

h) File system configuration, software service configuration, software upgrade configuration, process hardening configuration, system file configuration, privileged command configuration, and time... The configuration of clock synchronization service and scheduled task service should comply with the requirements of C.1.

7.2 Network Services

Network service requirements include.

a) Harden the configuration of SSH and RDP services, such as by not using Secure Shell version 1 (SSHv1), root access, or blank passwords.

Configure maximum login attempts, idle timeout, and anonymous remote connection limits, and disable SSH port forwarding.

b) Network services should be configured to filter packets that may pose security risks, such as security groups and network ACLs, to filter potential security threats. All-risk network traffic;

c) Unencrypted Telnet should not be used for remote management;

d) Unnecessary ports, such as 135, 445, and 23, should be closed or blocked;

e) SYN attack protection should be enabled to prevent SYN attacks;

f) Unnecessary network interface cards should not be used or should be removed;

g) The system should use a firewall to implement access control and enhance its ability to resist network attacks;

h) The maximum number of sessions allowed per user should be limited;

i) The kernel network service configuration should comply with the requirements of C.2.1, and the network service application configuration should comply with the requirements of C.2.2.

7.3 Account and Password Security

Account and password security requirements include.

a) User accounts with minimum privileges should be created, default accounts such as root and guest should be disabled, and accounts with blank passwords should not exist;

b) An account login failure function should be configured to lock the account after a certain number of consecutive failed login attempts;

c) An automatic logout mechanism should be configured for login connection timeouts. The session timeout should not be 0, not configured, or too long.

d) Operating system account passwords should be set, and the same password should not be used repeatedly. Default passwords should be changed, and the account and password should be different.

e) The password must be at least 8 characters long and contain at least numbers, uppercase and lowercase letters, and special characters, and must be encrypted with high strength. Storage method;

f) The validity period of passwords should be reasonably configured according to business needs, and the longest validity period should not exceed 3 months;

g) Appropriate permissions should be assigned to operating system accounts;

h) Account management configuration, password management configuration, and alarm notification information configuration should comply with the requirements of C.3.

8 Container security configuration requirements

8.1 Overview

The document proposes security configuration baseline requirements for management-side containers, which can be used as a reference for tenant-side cloud containers.

8.2 Host Configuration

Host configuration requirements include.

a) A separate storage space should be created for the container;

b) The container should be updated to the latest stable version;

c) Ordinary users should not have permissions to create, execute, or manipulate containers;

d) Unused images should be deleted periodically;

e) The number of containers on the host machine should be limited;

f) The network access range of the host machine should be restricted, allowing only necessary port communication;

g) Privileged accounts should not be used to log in to the host machine.

8.3 Daemon Process Configuration

Daemon configuration requirements include.

a) Inter-container communication on the bridge should not be enabled by default, and encryption protection should be enabled;

b) Mirror repositories without mirror repository certificates or that do not use TLS should not be used;

c) Existing storage drivers should not be used;

d) Security configurations for the daemon should be enabled, such as two-way authentication, resource limiting, and resource isolation;

e) A default space size for the container should be set;

f) An authentication and authorization mechanism for container client commands should be enabled;

g) Containers should not elevate privilege levels via executable files;

h) Interactions from older repository versions should not be used;

i) A real-time recovery mechanism should be enabled;

j) User-space network proxies should not be used;

k) Containers should not be started in privileged mode;

l) Daemons should not be run with a non-privileged account; they should be run using a non-privileged user and security group.

m) The ownership and permissions of files and directories related to the daemon process should be configured in accordance with the requirements of D.1.

......
This preview omits tables, figures, formulas and parts of the technical clauses. The complete document — 35 pages — is available in the English PDF.

How to Download GB/T 47686-2026

  1. 1

    Add to cart

    Click "Download PDF" on this page and choose "Buy this standard". You can add more standards before checkout.

  2. 2

    Checkout

    Enter your email and billing details. Payment is processed securely by Stripe (cards or bank transfer). Prefer bank details? Request a quotation (min. order $300).

  3. 3

    Fast delivery

    After payment you'll receive an email confirmation. The English PDF is sent to the same address, usually within minutes and at the latest within 1 business day.

  4. 4

    Invoice included

    A tax invoice is attached to the confirmation email. Need a custom invoice? Contact us.

Related Standards

English PDF
35 pages
Fast delivery
Invoice included
View Cart

Secure payment via Stripe

Payments accepted

VisaMastercardAmerican ExpressApple PayGoogle PayStripe

GB/T 47686-2026

$545.00