Help Center/ Host Security Service/ User Guide (Paris)/ Asset Management/ Server Management/ Enabling Protection/ WTP Edition
Updated on 2024-08-14 GMT+08:00
View PDF
Share

WTP Edition

The WTP edition provides web tamper protection capabilities for your servers.

Web Tamper Protection Principles

Table 1 How WTP works

Type

Mechanism

Static web page protection
  1. Local directory lock

    WTP locks files in a web file directory in a drive to prevent attackers from modifying them. Website administrators can update the website content by using privileged processes.

  2. Proactive backup and restoration

    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.

  3. Remote backup and restoration

    If a file directory or backup directory on the local server is invalid, you can use the remote backup service to restore the tampered web page.

Dynamic web page protection

Dynamic web page protection for Tomcat.

  1. Malicious behavior filtering based on RASP

    The unique runtime application self-protection (RASP) detects application program behaviors, preventing attackers from tampering with web pages through application programs.

  2. Network disk file access control

    WTP implements fine-grained management to control permissions for adding, modifying, and querying file content in network disks, preventing tampering without affecting website content release.

Prerequisite

  • The agent has been installed on the servers to be protected, the agent status is Online, and the protection status is Unprotected.

Configuring Protected Directories

You can add up to 50 directories to be protected. For details, see Adding a Protected Directory.

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.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner of the page, select a region, and choose Security > Host Security Service.
  1. In the navigation pane, choose Protection > Web Tamper Protection. On the Web Tamper Protection page, click the Servers tab.
  2. Click Add Server. In the displayed dialog box, select servers.

    Selected servers must be equal to or fewer than the available quotas.

  3. Click Add and Enable Protection and check the protection status. Choose Protection > Web Tamper Protection. On the Web Tamper Protection page, click the Servers tab. If the Protection Status of the server is Protected, WTP has been enabled.

    • After WTP is enabled, configure protected directories for WTP to take effect. For details, see Adding a Protected Directory.
    • Dynamic WTP can only be enabled for Linux servers, and can only be used after Tomcat is restarted.
    • You can check the server protection status on the Web Tamper Protection page.
      The premium edition will be enabled when you enable WTP. You can perform the following operations to check the protection status:
      • Choose Prevention > Web Tamper Protection. If the Protection Status of the server is Protected, WTP has been enabled.
      • Choose Asset Management > Servers & Quota and click the Servers tab. If the Edition of the target server is WTP edition, the premium edition provided by the WTP edition is enabled free of charge.

Parent topic: Enabling Protection