WTP Overview
Web Tamper Protection (WTP) can detect and prevent tampering of files in specified directories, including web pages, documents, and images, and quickly restore them using valid backup files.
Constraints
Ensure that the WTP edition has been enabled for the server. For details about how to purchase HSS and enable the WTP edition, see Purchasing HSS Quota and Enabling Web Tamper Protection.
How WTP Prevents Web Page Tampering
WTP supports static and dynamic web page protection. How WTP works shows the protection mechanism.
Process of Using WTP
![](https://support.huaweicloud.com/eu/usermanual-hss2.0/en-us_image_0000001716562232.png)
Procedure |
Description |
---|---|
After the WTP edition is enabled, static WTP and other protection functions are enabled automatically. |
|
Static WTP protects specified directories. You need to configure static WTP directories. |
|
By default, HSS backs up files in the protected directories to the local backup paths you specified when adding protected directories. To prevent the local backup from being damaged by attackers, you can configure remote backup to protect web page backup data. |
|
After static WTP is enabled, the content in the protected directory is read-only and cannot be modified. To modify a protected file, you can add a privileged process. |
|
Not all OS kernel versions support privileged processes and each server can add up to 10 privileged processes. For OSs that do not support privileged processes, you can set periodic static WTP and update websites when WTP is automatically disabled. |
|
HSS provides runtime application self-protection (RASP) for Tomcat applications. You can enable dynamic WTP for Tomcat applications as required. |
|
Tamper events that occur during static web tamper protection are recorded and displayed in the event list. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.