Managing Protection Policies

Constraints

Only premium, WTP, and container editions support ransomware protection.

Creating a Policy

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.
3. In the navigation pane, choose Prevention > Ransomware Prevention. Click the Protected Servers tab. Click Add Server.

4. In the slide pane that is displayed, select Linux or Windows, enable protection, and select Create new. For more information, see Table 1.
   The following uses a Linux server as an example.

   Table 1 Protection policy parameters

   Parameter	Description	Example Value
   Policy	Policy name	test
   Action	Indicates how an event is handled. Report alarm and isolate Report alarm	Report alarm and isolate
   Bait File	After bait protection is enabled, the system deploys bait files in protected directories and key directories (unless otherwise specified by users). A bait file occupies only a few resources and does not affect your server performance. If ransomware prevention is enabled, this function is enabled by default. NOTE: Currently, Linux servers support dynamic generation and deployment of bait files. Windows servers support only static deployment of bait files.	Enabled
   Bait File Directories	Protected directories (excluding subdirectories). Separate multiple directories with semicolons (;). You can configure up to 20 directories. This parameter is mandatory for Linux servers and optional for Windows servers.	Linux: /etc/lesuo Windows: C:\Test
   Excluded Directory (Optional)	Directories where bait files are not deployed. Separate multiple directories with semicolons (;). You can configure up to 20 excluded directories.	Linux: /test Windows: C:\ProData
   Protected File Type	Types of files to be protected. More than 70 file formats can be protected, including databases, containers, code, certificate keys, and backups. This parameter is mandatory for Linux servers only.	Select all

5. Click Next and select servers. You can search for a server by its name or by filtering.
6. Click OK to enable ransomware protection and create the policy.
7. In the navigation pane, choose Prevention > Ransomware Prevention. Click the Policies tab and check the new policy.

Modifying a Policy

1. Log in to the management console and go to the page.
2. In the navigation pane, choose Prevention > Ransomware Prevention. Click the Policies tab.
3. Click Edit in the Operation column of a policy. Edit the policy configurations and associated servers. For more information, see Protection policy parameters.
   The following uses a Linux server as an example. On the Protected Servers tab, you can also click the name of the policy associated with the server to edit the policy.

   Table 2 Protection policy parameters

   Parameter	Description	Example Value
   Policy	Policy name	test
   Action	Indicates how an event is handled. Report alarm and isolate Report alarm	Report alarm and isolate
   Bait File	After bait protection is enabled, the system deploys bait files in protected directories and key directories (unless otherwise specified by users). A bait file occupies only a few resources and does not affect your server performance. If ransomware prevention is enabled, this function is enabled by default. NOTE: Currently, Linux servers support dynamic generation and deployment of bait files. Windows servers support only static deployment of bait files.	Enabled
   Bait File Directories	Protected directories (excluding subdirectories). Separate multiple directories with semicolons (;). You can configure up to 20 directories. This parameter is mandatory for Linux servers and optional for Windows servers.	Linux: /etc/lesuo Windows: C:\Test
   Excluded Directory (Optional)	Directories where bait files are not deployed. Separate multiple directories with semicolons (;). You can configure up to 20 excluded directories.	Linux: /test Windows: C:\ProData
   Protected File Type	Types of files to be protected. More than 70 file formats can be protected, including databases, containers, code, certificate keys, and backups. This parameter is mandatory for Linux servers only.	Select all

4. Confirm the policy information and click OK.

Deleting a Policy

1. Log in to the management console and go to the page.
2. In the navigation pane, choose Prevention > Ransomware Prevention. Click the Policies tab.
3. Click Delete in the Operation column of the target policy.
4. Confirm the policy information and click OK.