Overview

If policies such as asset collection, baseline check, and intrusion detection do not meet your server protection requirements, you can manage these policies.

Table 1 lists the policies that can be managed by each HSS edition. For details about how to configure policies, see Configuring Policies.

If you have different protection requirements, you can create a custom policy group to deploy different protection policies for different servers. For details, see Creating a Policy Group.

**Table 1** Policies
Function Type	Policy	Action	Supported OS	Professional Edition	Enterprise Edition	Premium Edition	WTP Edition	Container Edition
Assets	Asset discovery	Scan and display all software in one place, including software name, path, and major applications, helping you identify abnormal assets.	Linux and Windows	×	×	√	√	√
Baseline Inspection	Weak password detection	Change weak passwords to stronger ones based on HSS scan results and suggestions.	Linux	√	√	√	√	√
	Container information collection	Collect information about all containers on a server, including ports and directories, and report alarms for risky information.	Linux	×	×	×	×	√
	Configuration Check	Check the unsafe Tomcat, Nginx, and SSH login configurations found by HSS.	Linux and Windows	×	×	√	√	√
Intrusions	AV detection	Check server assets and report, isolate, and kill the detected viruses. The generated alarms are displayed under Detection > Alarms > Server Alarms > Event Types > Malware. After AV detection is enabled, the resource usage is as follows: The CPU usage does not exceed 40% of a single vCPU. The actual CPU usage depends on the server status. For details, see How Many CPU and Memory Resources Are Occupied by the Agent When It Performs Scans?	Windows	√	√	√	√	×
	Cluster intrusion detection	Detect container high-privilege changes, creation in key information, and virus intrusion.	Linux	×	×	×	×	√
	Container escape	Check for and generate alarms on container escapes.	Linux	×	×	×	×	√
	Container information module	This function is used to mask intrusion detection alarms of trusted containers. You can configure a trusted container whitelist based on the container name, organization name to which the image belongs, and namespace so that intrusion detection does not detect these trusted containers.	Linux	×	×	×	×	√
	Web Shell Detection	Scan web directories on servers for web shells.	Linux and Windows	√	√	√	√	√
	Container File Monitoring	Detect file access that violates security policies. Security O&M personnel can check whether hackers are intruding and tampering with sensitive files.	Linux	×	×	×	×	√
	Container Process Whitelist	Check for process startups that violate security policies.	Linux	×	×	×	×	√
	Suspicious Image Behaviors	Configure the blacklist and whitelist and customize permissions to ignore abnormal behaviors or report alarms.	Linux	×	×	×	×	√
	HIPS Detection	Check registries, files, and processes, and report alarms for operations such as abnormal changes.	Linux and Windows	×	√	√	√	√
	File Protection	Check the files in the Linux OS, applications, and other components to detect tampering.	Linux	√	√	√	√	√
	Login Security Check	Detect brute-force attacks on SSH, FTP, and MySQL accounts. If the number of brute-force attacks (consecutive incorrect password attempts) from an IP address reaches 5 within 30 seconds, the IP address will be blocked. By default, suspicious SSH attackers are blocked for 12 hours. Other types of suspicious attackers are blocked for 24 hours. You can check whether the IP address is trustworthy based on its attack type and how many times it has been blocked. You can manually unblock the IP addresses you trust.	Linux and Windows	√	√	√	√	√
	Malicious File Detection	Reverse shell: Monitor user process behaviors in real time to detect reverse shells caused by invalid connections. Detect actions on abnormal shells, including moving, copying, and deleting shell files, and modifying the access permissions and hard links of the files.	Linux	√	√	√	√	√
	Port Scan Detection	Detect scanning or sniffing on specified ports and report alarms.	Linux	×	×	√	√	√
	Abnormal process behaviors	All the running processes on all your servers are monitored for you. You can create a process whitelist to ignore alarms on trusted processes, and can receive alarms on unauthorized process behavior and intrusions.	Linux	√	√	√	√	√
	Root privilege escalation	Detect the root privilege escalation for files in the current system.	Linux	√	√	√	√	√
	Real-time process	Monitor the executed commands in real time and generate alarms if high-risk commands are detected.	Linux and Windows	√	√	√	√	√
	Rootkit Detection	Detect server assets and report alarms for suspicious kernel modules, files, and folders.	Linux	√	√	√	√	√
Self-protection	Self-protection	Protect HSS files, processes, and software from malicious programs, which may uninstall HSS agents, tamper with HSS files, or stop HSS processes. Self-protection depends on antivirus detection, HIPS detection, and ransomware protection. It takes effect only when more than one of the three functions are enabled. Enabling the self-protection policy has the following impacts: The HSS agent cannot be uninstalled on the control panel of a server, but can be uninstalled on the HSS console. HSS process cannot be terminated. In the agent installation path C:\Program Files\HostGuard, you can only access the log and data directories (and the upgrade directory, if your agent has been upgraded).	Windows	×	×	√	√	×