Enabling Protection

1. Log in to the management console.
2. Click in the upper left corner and select a region or project.
3. In the upper left corner of the page, click and choose Security > Host Security Service.
4. In the navigation pane on the left, choose Asset Management > Servers & Quota.
5. Locate a server whose agent status is Online.
6. Click Enable in the Operation column of a server.
7. Click OK. If the Protection Status of the target server is Enabled, the enterprise or premium edition has been enabled.

   After the protection is enabled, it takes 2 to 3 minutes for HSS to send protection policies to agents. The protection is successful only after all policies are sent. To check policy statuses, choose Asset Management > Servers & Quota and click a server name. On the server details page, choose Security Operations > Policies. If all the policy statuses are Enabled, the policies have been sent.

   Note

   • A quota can be bound to a server to protect it, on condition that the agent on the server is online.
   • After HSS is enabled, it will scan your servers for security issues. Check items vary according to the edition you enabled.

8. (Optional) Configure alarm notification, protection policies, server login protection, and malicious program isolation and removal.
   • Configuring alarm notifications

     After HSS is enabled, alarms are displayed on the console by default. To learn the security risks of servers, containers, or web pages in a timely manner, you can enable alarm notification, and HSS will notify you of risks by SMS or email. For details, see Alarm Configuration.

   • Configuring protection policies

     Each HSS edition provides a group of protection policies preset with default settings. You can enable or disable policies and adjust protection rules as needed. For details, see Policy Management.

   • Configuring login protection

     You can enhance server login security by Enabling 2FA, Configuring Common Login Locations, Configuring Common Login IP Addresses, and Configuring an SSH Login IP Address Whitelist

   • Enabling malicious program isolation and removal

     If this function is enabled, HSS will automatically isolate identified malicious programs, such as backdoors, Trojans, and worms, to help you handle security risks. For details, see Isolating and Killing Malicious Programs.

WTP can be enabled for one or multiple servers at a time. When you enable it for multiple servers at a time, the same protected directory settings will be applied to all of them, and cannot be customized for each server. If these servers have different directories to be protected, you can customize the protected directories or other settings for them separately after WTP is enabled. For details, see Modifying Settings.

1. Log in to the management console.
2. Click in the upper left corner and select a region or project.
3. In the upper left corner of the page, click and choose Security > Host Security Service.
4. In the navigation pane, choose Server Protection > Web Tamper Protection.
5. On the Servers tab, click Add Server.
6. On the Add Server page, select servers and quotas, and click Next. For more information, see Table 1.
   Table 1 Parameters for selecting protected servers

   Parameter	Description	Example Value
   OS	Select the OS type of the server to be protected by WTP. Linux Windows	Linux
   Select Servers	Select servers. You can filter the servers by software type or other attributes.	-

7. On the Add Server page, configure policies. For more information, see Table 2.
   Table 2 Parameters for configuring rules

   Parameter	Description	Example Value
   Protected Directory	WTP supports static and dynamic web page protection. Static WTP can lock protected directories, or restore their data from backups in real time once it detects changes made by attackers. Therefore, when configuring a protection policy, you need to specify the directories to be protected. After a directory is protected, the files and folders in the directory will become read-only. The requirements for adding a protected directory are as follows: For Linux, It cannot start with a space, end with a slash (/), or contain semicolons (;). Up to 256 characters are allowed. A server can have up to 50 protected directories. The folder levels of a protected directory cannot exceed 100. The total folders in protected directories cannot exceed 900,000. For Windows, Up to 256 characters are allowed. The directory name cannot start with a space or end with a backslash (\). It cannot contain the following characters: ;/*?"<>| A server can have up to 50 protected directories. Do not add network directories as protected directories. The reasons are as follows: Inefficient detection A network directory usually contains a large number of files and may reach hundreds of terabytes, severely slowing down a scan. Network bandwidth consumption Accessing a network directory consumes network bandwidth. A large-scale scan may fully occupy the network bandwidth and affect your workloads. For example, the access speed may slow down and the network latency may increase.	Linux: /etc/lesuo Windows: d:\web
   Excluded Subdirectory (Optional)	If a protected directory contains subdirectories that do not need to be protected, you can exclude the subdirectories. The requirements for adding a subdirectory are as follows: Enter a subdirectory name or the relative subdirectory path under a protected directory. If you enter a subdirectory name, all subdirectories that match the name will be excluded, regardless of their levels. A subdirectory name or path cannot start or end with a slash (/) and can contain up to 256 characters. Up to 10 subdirectories can be added. Use semicolons (;) to separate multiple subdirectories.	Linux: data/cache or cache Windows: web\test or test
   Excluded File Path (Optional)	This item is available only for Linux servers. If a protected directory contains files that do not need to be protected, exclude the files. The requirements for adding excluded file paths are as follows: Enter a file name or the relative file path under a protected directory. If you enter a file name, all files that match the name will be excluded, regardless of their levels. A file name or path cannot start or end with a slash (/), and can contain up to 256 characters. Up to 50 files can be added. Use semicolons (;) to separate multiple files.	data/ma.txt or ma.txt
   Local Backup Path	This item is available only for Linux servers. Set a local backup path for a protected directory. After WTP is enabled, files in the protected directory are automatically backed up to the local backup path. Once the system detects that a file in the protected directory is tampered with, it immediately uses the local backup to restore the tampered file. The requirements for adding local backup paths are as follows: A local backup path cannot contain semicolons (;), start with a space, or end with a slash (/). Up to 256 characters are allowed. Key system directories are a main attack target and cannot be used as backup paths, including but not limited to /etc/, /bin/, /usr/bin/, /var/spool/, /usr/sbin/, /sbin/, /usr/lib/, /lib/, /lib64/, /usr/lib64/, and their subdirectories. Local backup rule description: The local backup path must be valid and cannot overlap with the protected directory path. Excluded subdirectories and types of files are not backed up. Generally, the backup completes within 10 minutes. The actual duration depends on the size of files in the protected directory.	/backup
   Excluded File Type	If a protected directory contains files of certain types that do not need to be protected, exclude these file types, for example, logs. You can exclude any type of files. To record the running status of servers in real time, exclude the log files in the protected directory. You can set high permission requirements for log read and write, so that attackers cannot view or tamper with log files.	log
   Type	Action taken when file tampering is detected. Alarm: Only alarms are reported. Block: An alarm is reported, and the file is restored to the status before being tampered with.	Block
   Scheduled Protection (Optional)	You can schedule when to disable static WTP. In the unprotected period, you can modify, update, or release web pages. Click to enable scheduled protection and configure the following parameters: Unprotected Time Range A time range when WTP is disabled within a day, for example, 10:05 to 15:35. Requirements: A time range must be at least 5 minutes. Time ranges (except for those starting at 00:00 or ending at 23:59) cannot overlap and must have at least a 5-minute interval. All time ranges are subject to the system time of the server. Unprotected Days of a Week Static WTP is automatically disabled on specified days of a week, for example, Wednesday and Thursday.	, 10:05-15:35, Wednesday
   Dynamic WTP (Optional)	Dynamic WTP is mainly used to protect Tomcat applications on Linux. It can detect and prevent tampering with dynamic data, such as database data, in real time during application running. Currently, dynamic WTP can protect Tomcat applications using JDK 8, JDK 11, and JDK 17. To enable dynamic WTP, click and enter a complete Tomcat bin directory path, for example, /usr/workspace/apache-tomcat-8.5.15/bin. The system presets the setenv.sh script in the bin directory to configure the startup parameters of the anti-tamper program.	, /usr/workspace/apache-tomcat-8.5.15/bin
   Configure Privileged Processes (Optional)	A privileged process is a process authorized to modify a protected directory. If WTP is enabled, all files in protected directories are set to read-only and cannot be modified. You can add privileged processes and use them to modify the files in protected directories or update websites. Ensure the specified privileged processes, which are authorized to access protected directories, are secure and reliable. This feature is compatible with Linux and Windows. For Linux, only the distributions using kernel versions 5.10 or later are supported. Click to enable the privileged processes and configure the following parameters: Process File Path Set one or multiple complete file paths of privileged processes. Put each privileged process file path on a separate line. Up to 10 privileged processes are allowed. Trust Subprocess If Trust Subprocess is enabled, HSS will trust all the subprocesses up to five levels deep in the subdirectories of specified directories, and allow the subprocesses to modify protected directories, and allow the subprocesses to modify protected directories.	Linux: /Path/Software.type Windows: C:\Path\Software.type

8. After the policy is configured, click OK.
9. On the Servers tab, check the static and dynamic WTP status of the server.

   The Protected status indicates protection has been enabled. After dynamic WTP is enabled, restart Tomcat to apply the settings.

   After the protection is enabled, it takes 2 to 3 minutes for HSS to send protection policies to agents. The protection is successful only after all policies are sent. To check policy statuses, choose Asset Management > Servers & Quota and click a server name. On the server details page, choose Security Operations > Policies. If all the policy statuses are Enabled, the policies have been sent.

10. (Optional) Configure alarm notification, protection policies, server login protection, and malicious program isolation and removal.

    In addition to web tamper protection, the HSS WTP edition also offers server protection, vulnerability scan, and baseline check functions. For details about the functions, see Features. You can configure them as needed. Below are the ways to configure basic features:

    • Configuring alarm notifications

      After HSS is enabled, alarms are displayed on the console by default. To learn the security risks of servers, containers, or web pages in a timely manner, you can enable alarm notification, and HSS will notify you of risks by SMS or email. For details, see Alarm Configuration.

    • Configuring protection policies

      Each HSS edition provides a group of protection policies preset with default settings. You can enable or disable policies and adjust protection rules as needed. For details, see Policy Management.

    • Configuring login protection

      You can enhance server login security by Enabling 2FA, Configuring Common Login Locations, Configuring Common Login IP Addresses, and Configuring an SSH Login IP Address Whitelist

    • Enabling malicious program isolation and removal

      If this function is enabled, HSS will automatically isolate identified malicious programs, such as backdoors, Trojans, and worms, to help you handle security risks. For details, see Isolating and Killing Malicious Programs.

1. Log in to the management console.
2. Click in the upper left corner and select a region or project.
3. In the upper left corner of the page, click and choose Security > Host Security Service.
4. In the navigation pane, choose Asset Management > Containers & Quota.
5. In the row of a server, click Enable Protection in the Operation column. The confirmation dialog box is displayed.

   Ensure there is an active container on the node. If there is none, start one.

6. Confirm the node information and select a billing mode.
   Caution

   A container security quota protects one cluster node.

7. Read the Host Security Service Disclaimer and select I have read and agree to the Container Guard Service Disclaimer.
8. Click OK. If the Protection Status of the node changes to Protected, protection has been enabled.

   After the protection is enabled, it takes 2 to 3 minutes for HSS to send protection policies to agents. The protection is successful only after all policies are sent. To check policy statuses, choose Asset Management > Servers & Quota and click a server name. On the server details page, choose Security Operations > Policies. If all the policy statuses are Enabled, the policies have been sent.

9. (Optional) Configure alarm notification, protection policies, server login protection, and malicious program isolation and removal.
   • Configuring alarm notifications

     After HSS is enabled, alarms are displayed on the console by default. To learn the security risks of servers, containers, or web pages in a timely manner, you can enable alarm notification, and HSS will notify you of risks by SMS or email. For details, see Alarm Configuration.

   • Configuring protection policies

     Each HSS edition provides a group of protection policies preset with default settings. You can enable or disable policies and adjust protection rules as needed. For details, see Policy Management.

   • Configuring login protection

     You can enhance server login security by Enabling 2FA, Configuring Common Login Locations, Configuring Common Login IP Addresses, and Configuring an SSH Login IP Address Whitelist

   • Enabling malicious program isolation and removal

     If this function is enabled, HSS will automatically isolate identified malicious programs, such as backdoors, Trojans, and worms, to help you handle security risks. For details, see Isolating and Killing Malicious Programs.