- How do I enable protection against brute-force attacks?
- How do I handle a successful brute-force attack?
- Why do I still receive brute-force attack alerts after I change the default port of the SSH service?
- Why are RDP brute-force attacks detected after RDP requests on port 3389 have already been blocked by security group rules or firewall rules?
- Does Security Center detect weak passwords of RDP and SSH services only?
- How do I handle an SSH or RDP remote logon failure?
How do I enable protection against brute-force attacks?
- On the Security Risk page, click Process Now on the right side to go to the tab.
- On the Anti-brute Force Cracking tab, place the pointer over the dimmed button Add. A message appears indicating that authorization is required. Follow the instructions to complete the authorization.
- After the authorization is complete, click Add to add a defense rule.
- The following table shows how to set the parameters.
Parameter Description Defense Rule Name Specify a name for the defense rule. Defense Rule Set the defense rule parameters. If the number of times that an IP address fails to log on to the specified servers exceeds the upper limit (2,3, 4, 5, or 10 times) within the specified time period (1, 2, 5, 10, or 15 minutes), the IP address is blocked for a specified time period (5, 15, or 30 minutes, or 1, 2, 6, or 12 hours).
For example, if the number of logon failures exceeds 3 times within 1 minute, the IP address is blocked for 30 minutes.
Select Server Select the servers where you want to apply the defense rule. You can directly select servers that are added to Security Center, or search servers by name or IP address. Set As Default Policy Specify the defense rule as the default rule.
- Click OK.
How do I handle a successful brute-force attack?
- Change the server password
Change the cracked password as soon as possible. We recommend that you use a complex password.
- Run baseline checks to detect risks
Use the baseline check feature of Security Center to detect risks on your servers, and handle the detected risks based on the suggestions.Note Baseline check is only supported by the Enterprise Edition.
- Reset your server, and enhance server security
For more information about how to enhance server security, see Secure ECS deployment.
Why do I still receive brute-force attack alerts after I change the default port of the SSH service?
After you change the default port of the SSH service on a Linux server from 22 to another port, you may still receive brute-force attack alerts from Security Center.
Security Center identifies brute-force attacks based on the frequency of SSH logon attempts rather than the SSH port. Therefore, even if you have changed the default port of the SSH service, Security Center still sends you alerts triggered by brute-force attacks on the SSH service.
If your server has been cracked by brute-force attacks, we recommend that you reinforce protection for your server. For more information, see How do I handle a successful brute-force attack?.
Why are RDP brute-force attacks detected after RDP requests on port 3389 have already been blocked by security group rules or firewall rules?
Due to the special logon audit mechanism in Windows operating systems, the audit activities of logons based on IPC, RDP, and Samba are recorded in the same log without specifying the logon methods. If records of RDP brute-force attacks are found after the requests to the RDP service port have been blocked, check whether IPC or Samba is enabled.
Check whether the ECS instance has enabled port 135, port 139, or port 445 and whether these ports can be accessed by public IP addresses. Check whether the Window security logs contain logon records within the attack time period.
Does Security Center detect weak passwords of RDP and SSH services only?
Security Center detects weak passwords of RDP and SSH services and weak passwords that are used by administrators to log on to content management systems (CMS).
How do I handle an SSH or RDP remote logon failure?
If the current IP address cannot remotely log on to a cloud server through SSH or RDP, log on to the Alibaba Cloud Security Control console to add this IP address to the whitelist.
- Log on to the Security Center console.
- In the left-side navigation pane, choose General tab, find the Security Control section, and then click Configuration to go to the Security Control console.
Note Alternatively, place the pointer over the avatar in the upper-right corner of the Alibaba Cloud console, and select Security Console to go to the Alibaba Cloud Security Control console.
. On the
- In the Alibaba Cloud Security Control console, choose Add. in the left-side navigation pane, and then click
- Enter the IP address in the Source IP field, and select the servers to which logons from the IP address are allowed. Select one or more servers from the box on the left, and click the right arrow to add the selected servers to the Selected box on the right.
- Click OK after you complete the configurations.