Ransomware Prevention Overview
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.
Constraints and Limitations
- To use ransomware prevention for a server, enable the HSS premium, web tamper protection, or container edition.
- If the version of the agent installed on the Linux server is 3.2.10 or later or the version of the agent installed on the Windows server is 4.0.22 or later, ransomware prevention is automatically enabled with the premium, WTP, or container edition. For other agent versions, you need to manually enable ransomware prevention.
Process of Using Ransomware Prevention
Operation |
Description |
---|---|
Enable ransomware prevention on a server, deploy static and dynamic honeypots, detect ransomware attacks in real time, and automatically isolate suspicious processes. (There is a low probability that some normal processes are incorrectly isolated.) If the version of the agent installed on the Linux server is 3.2.10 or later or the version of the agent installed on the Windows server is 4.0.22 or later, ransomware prevention is automatically enabled with the premium, WTP, or container edition. For other agent versions, you need to manually enable ransomware prevention. |
|
Currently, no tools can protect all ransomware. Servers need to be periodically backed up, so that data can be restored using the backup in a timely manner to reduce loss if a ransomware event occurs. |
|
Once a ransomware attack is detected during ransomware protection, analyze and isolate the ransomware in a timely manner, and fix the security weaknesses of the system. |
|
If ransomware intrusion succeeds and your service data is lost, you can use the backup to restore data and reduce loss. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.