Purchasing and Enabling WTP
Scenario
HSS provides static and dynamic (Tomcat) Web Tamper Protection (WTP) functions. WTP monitors website directories in real time, backs up files, and restores tampered files. In addition, multiple server security protection functions are provided. For details, see Product Functions.
This document uses an ECS running EulerOS 2.9 as an example to describe how to purchase and enable WTP.
Step 1: Purchase HSS Quota
- Log in to the management console.
- Click in the upper left corner and select the region and project.
- Click in the upper left corner of the page and choose Security & Compliance > HSS.
- In the upper right corner of the Dashboard page, click Buy HSS.
- Set the parameters for buying HSS as prompted.
- Billing Mode: Select Yearly/Monthly. Only the yearly/monthly billing mode is supported.
- Region: Select the region where the server is located. In this example, select CN-Hong Kong.
- Edition: Select Web Tamper Protection.
- Quantity: Set this parameter based on the number of servers. In this example, set the quantity to 1.
- Specify other parameters as needed.
- In the lower right corner of the page, click Next.
- After confirming that the order, select I have read and agree to the Host Security Service Disclaimer.
- Click Pay Now and complete the payment.
- Click Back to Host Security Service Console.
Step 2: Install an Agent
- In the navigation pane, choose .
- Choose .
- In the Operation column of the target server, click Install Agent. The Install Agent dialog box is displayed.
Figure 1 Installing an agent
- Select and set the server verification information.
- Server authentication mode: Select a mode. In this example, select Account and password mode.
- Allow direct connection with root permissions: Whether to allow root direct connection. In this example, select this option.
- Server Root Password: Set this parameter based on the server information.
- Server Login Port: Set this parameter based on the actual server login port. In this example, set 22 port.
Figure 2 Enter the server verification information.
- Click OK to start installation.
- Choose Servers With Agents page and view the agent status of the target server.
If the Agent Status is Online, the agent is successfully installed.
Step 3: Enable Protection
- In the navigation pane, choose Server Protection > Web Tamper Protection.
- On the Servers tab, click Add Server.
- On the Add Server page, select the target server and click Add and Enable Protection.
Figure 3 Adding a protected server
- Read the message for adding a protected directory and click .
Figure 4 Prompt information
- Locate the row containing the target server and click Configure Protection in the Operation column.
Figure 5 Protection settings
- Add a protected directory.
- In the Protected Directory Settings area, click Settings.
- In the Protected Directory Settings dialog box, click Add Protected Directory.
Figure 6 Adding a protected directory
- Add protected directories based on service requirements. For details about the parameters, see Table 1.
Table 1 Parameters for adding a protected directory Parameter
Description
Example Value
Protected Directory
Add directories to be protected.
- Do not add an OS directory as a protected directory.
- After a directory is added, the files and folders in the protected directory are read-only and cannot be modified directly.
/etc/lesuo
Excluded Subdirectory
Subdirectories that do not need to be protected in the protected directory, such as temporary file directories.
Separate subdirectories with semicolons (;). A maximum of 10 subdirectories can be added.
lesuo/test
Excluded File Types
Types of files that do not need to be protected in the protected directory, such as log files.
To record the running status of the server in real time, exclude the log files in the protected directory. You can grant high read and write permissions for log files to prevent attackers from viewing or tampering with the log files.
Separate file types with semicolons (;).
log;pid;text
Local Backup Path
Set this parameter if your server runs the Linux OS.
Set a local backup path for files in protected directories. After WTP is enabled, files in the protected directory are automatically backed up to the local backup path.
The backup rules are described as follows:
- 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.
- If WTP detects that a file in a protected directory is tampered with, it immediately uses the backup file on the local server to restore the file.
/etc/backup
Excluded File Path
Exclude files that do not need to be protected from the protected directory.
Separate multiple paths with semicolons (;). A maximum of 50 paths can be added. The maximum length of a path is 256 characters. A single path cannot start with a space or end with a slash (/).
lesuo/data;lesuo/list
- Click OK.
- In the protected directory list, if Protection Status is Protected, the directory is added successfully.
- (Optional) Enable remote backup.
Only Linux servers support the remote backup function. Skip this item for Windows servers.
- In the Protected Directory Settings dialog box, click Manage Remote Backup Servers.
Figure 7 Managing remote backup servers
- Click Add Backup Server.
- Enter the information and click OK. For details about the parameters, see Table 2.
- In the Protected Directory Settings area, click Settings.
- In the Protected Directory Settings dialog box, click Enable Remote Backup.
- Select the added remote backup server and click OK.
- If Enabled is displayed, remote backup is started.
- In the Protected Directory Settings dialog box, click Manage Remote Backup Servers.
- (Optional) Enable dynamic WTP.
Runtime application self-protection (RASP) is provided for Tomcat applications of JDK 8 on a Linux server. If you do not require RASP of the Tomcat application or the server runs the Windows OS, skip this item.
- In the Dynamic WTP area, click .
Figure 8 Enable dynamic WTP
- In the dialog box that is displayed, enter the Tomcat bin directory and click OK.
Tomcat bin directory example: /usr/workspace/apache-tomcat-8.5.15/bin
- If is displayed, dynamic WTP is enabled.
- Restart Tomcat to make the dynamic WTP function take effect.
- In the Dynamic WTP area, click .
Follow-Up Procedure
- Modify a file or folder in a protected directory.
If WTP is enabled, files or folders in the protected directory are read-only and cannot be modified. To modify files or folders in the protected directory, perform the following steps:
- Adding a privileged process: A maximum of 10 privileged processes can be added. For details, see Adding a Privileged Process.
- Enabling/Disabling scheduled static WTP: In addition to adding a privileged process, you can set periodic static WTP and modify files or folders when WTP is disabled, for details, see Enabling/Disabling Scheduled Static WTP.
- Enable active protection for servers.
WTP provides some proactive functions for servers. These functions are not enabled or not completely enabled when WTP is enabled. You can determine whether to use these functions based on your requirements, the following table Table 3 describes the functions.
Table 3 Proactive server protection functions Function
Description
Ransomware is one of the biggest cybersecurity threats today. Ransomware can intrude a server, encrypt data, and ask for ransom, causing service interruption, data leakage, or data loss. Attackers may not unlock the data even after receiving the ransom. HSS provides static and dynamic ransomware prevention. You can periodically back up server data to reduce potential losses.
Ransomware prevention is automatically enabled with the WTP edition. Honeypot files are deployed on your server and suspicious encryption programs are automatically isolated. You can modify the ransomware protection policy. You are also advised to enable backup so that you can restore data.
To protect your applications with RASP, you simply need to add probes to them, without having to modify application files.
HSS can learn the characteristics of application processes on servers and manage their running. Suspicious and trusted processes are allowed to run, and alarms are generated for malicious processes.
The function uses the virus detection engine to scan virus files on the server. The scanned file types include executable files, compressed files, script files, documents, images, and audio and video files. You can perform quick scan and full-disk scan on the server as required. You can also customize scan tasks and handle detected virus files in a timely manner to enhance the virus defense capability of the service system.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot