Security O&M

Change Operation Process

Use scripts to change the live network on the platform to avoid network faults caused by direct operations on the server console. In addition, operations on the platform must comply with the 1+1 check process. One person performs the operations, and the other monitors and checks the operations to ensure process, security, and quality compliance.

Control of Privilege Escalation Operations

Control the rights and authorization process based on the hierarchical risk classification and SOD principle. When a common service alarm is generated, the system must comply with the high-risk and blacklist command control. When a change operation is performed, the system can monitor commands in real time and classify command risk levels based on configured rules. If a high-risk or blacklist command is detected, the system provides a real-time alarm notification, this prevents service interruption caused by unauthorized operations. When an emergency service alarm is generated, privilege escalation must comply with regulations to balance security and efficiency.

Review of Change Operations

Before implementing a change, you need to apply for a change, review risks, and evaluate the change by the related expert team.

During change implementation, you must check, verify, and monitor services in each step. The check scope includes changed services, peripheral services, global monitoring alarms, dialing tests, and traffic changes to prevent live network faults caused by manual changes.