{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
6.11.3
Sangfor Cloud Platform (SCP) {{ breadTitle }} Security Service Core System Hardening (Hypervisor & OS Level)
{{sendMatomoQuery("Sangfor Cloud Platform (SCP)","Core System Hardening (Hypervisor & OS Level)")}}

Core System Hardening (Hypervisor & OS Level)

{{ $t('productDocDetail.updateTime') }}: 2025-12-22

The Sangfor HCI platform is built on a security-hardened Linux-based hypervisor. While these settings are managed by the platform, understanding them is crucial as they form the foundation of the environment's security.

Minimal Service Installation: The attack surface is significantly reduced by disabling all non-essential system services and processes. This includes components like mail agents, graphical desktops, Telnet, and compilation tools, ensuring that only the processes necessary for HCI functionality are running.

Core Service Hardening: Essential services, such as the SSH management interface, are configured with strict security settings to protect against common attack vectors. This includes protocol-level security and secure default configurations.

Kernel Parameter Tuning: The hypervisor kernel is tuned to enhance security. Key parameters, such as disabling IP forwarding, are configured to prevent the host from acting as a router, thereby containing network traffic and reducing risk.

File System Permissions: Following the principle of least privilege, file and directory permissions are set to the minimum required for system operation. This prevents unauthorized access to or modification of critical system files.

System Authentication & Authorization: Direct root user access to the hypervisor is restricted. Privileged access requires a dual-authorization mechanism, combining the platform's admin account with a vendor-issued authorization code. This ensures that no single entity (neither the user nor the vendor) can access the system's backend unilaterally.

Comprehensive Logging & Auditing: All critical system and kernel-level activities are logged and recorded in a "black box" audit trail. This provides full traceability, allowing administrators and support personnel to reconstruct system events for forensic analysis and troubleshooting.