Creating a Protection Policy for a Dynamic Honeypot Port

Scenario

The dynamic port honeypot function uses a real port as a honeypot port to induce attackers to access the network. Therefore, when enabling dynamic port honeypot protection, you need to create a protection policy to add a server port as a honeypot port and bind it to the server for protection.

This chapter describes how to create a dynamic port honeypot protection policy.

Constraints and Limitations

• A maximum of 10 honeypot ports can be added to a server.
• A honeypot port can be bound to only one protocol. Both TCP and TCP6 are supported.

Creating a Protection Policy for a Dynamic Honeypot Port

1. Log in to the management console.
2. In the upper left corner of the page, select a region, click , and choose Security & Compliance > HSS.
3. Choose Server Protection > Dynamic Port Honeypot.
4. (Optional) If you have enabled the enterprise project, select the enterprise project where the target server resides from the drop-down list.
5. On the Servers tab, click Create a Protection Policy. The dialog box is displayed.
6. Create a protection policy as prompted.
   1. Configure the policy and click Next. For details about related parameters, see Table 1

      Table 1 Parameters for creating a protection policy

      Parameter	Description
      Policy Name	You can retain the default name or enter a name that is easy to identify.
      OS Type	Select an OS type of a server to which you want to add the dynamic port honeypot function.
      Protected Port	Select a server port that implements the dynamic port honeypot function. Recommended Port: For Linux, common Windows ports are recommended. For Windows, common Linux ports are recommended. Custom Port: You can add custom ports or delete some recommended ports as required. NOTE: Ensure that the port to be added is not occupied by other services. If the port is occupied, the dynamic port honeypot function fails to be enabled.
      (Optional) Source IP address whitelist	By default, the servers that proactively connect to the dynamic honeypot port are compromised intranet servers. Once a suspicious connection behavior is detected, an alarm is reported. Therefore, if a trusted server may connect to the port, you are advised to add the IP address to the source IP address whitelist.

   2. Select the target server and click Save and Enable.
      Note that the dynamic port honeypot can be selected only for the servers that meet all the following conditions:

      • The HSS premium edition or higher has been enabled on the server.
      • The server agent is online. The Windows agent version is 4.0.22 or later, and the Linux agent version is 3.2.10 or later.
      • No dynamic port honeypot policies have been bound to the server.
      • The OS type of the server is the same as that specified in 6.a.
      • No EIPs have been bound to the server.

7. In the Associated Servers column of the created target policy, click the value. The dialog box is displayed.
   Figure 1 Associate servers
   

8. In the Port Status column of the associated server, check the port status.

   To enable the port again, click the Edit Policy to select server, and then bind the server. For details about how to edit a policy, see Editing a Policy.

FAQs

What can I do if the port fails to be enabled?

• Possible cause 1: The port is occupied by other services.

  Solution: Add other idle ports by editing the policy.

• Possible cause 2: System resources are insufficient.

  Solution: Free up some system resources, click the Edit Policy to select server, and then bind the server. For details about how to edit a policy, see Editing a Policy.