How Do I Handle a Brute-force Attack Alarm?

Mind map for troubleshooting

The following mind map describes how to handle a brute-force attack alarm.

Figure 1 Mind map for troubleshooting

Handling the Alarm of a Successful Brute-force Attack

If you received an alarm notification indicating that your account had been cracked, you are advised to harden your servers as soon as possible.

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. Check whether the IP address that triggered the alarm is valid.
   1. In the navigation pane, choose Detection > Alarms.
   2. In the Alarm Types area, select Abnormal User Behavior > Abnormal logins to view abnormal login alarm events.
   3. Click the alarm event name. On the details page that is displayed, check the login IP address.
      • If the IP address is from a normal user (for example, who entered incorrect password for multiple times but logged in before their account is blocked), your server is not intruded. In this case, you can click Handle and ignore the event.
      • If the IP address is invalid, your server may have been intruded.

        In this case, mark this event as handled, log in to the intruded server, and change its password to a stronger one. For details, see How Do I Set a Secure Password?

      Figure 2 Abnormal logins
      

4. Check for and eliminate malicious programs.
   1. In the navigation pane, choose Detection > Alarms.
   2. In the Alarm Types area, select Malware > Unclassified malware to filter the unclassified malware.
   3. In the Alarm Type column, select Malicious program and check alarm events.
      You can click an alarm name to view alarm event details.

      • If you find malicious programs implanted in your servers, locate them based on their process paths, users running them, and startup time.

        To kill a malicious program in an alarm event, click Handle in the Operation column of an alarm and select Isolate and kill.

      • If you have confirmed that all the malicious program alarms are false, go to Step 8.

5. Check for suspicious account change records.
   1. In the navigation pane on the left, choose Asset Management > Server Fingerprints.
   2. Click the Account Information tab. Detect suspicious account change records to prevent attackers from creating accounts or escalating account permissions (for example, adding login permissions to an account). For details, see Managing Account Information.

6. Check and handle invalid accounts.
   1. In the navigation pane, choose Detection > Alarms.
   2. In the Alarm Types area, select Abnormal User Behavior > Invalid accounts. View and handle the invalid account alarms. For details, see Handling Server Alarms

7. Check for and fix unsafe settings.

   Check for and fix weak password complexity policies and unsafe software settings on your servers. For details, see Fixing Unsafe Configurations.

8. Harden your servers.

   For more information, see Hardening Security for SSH Logins to Linux ECSs.

Handling the Alarm of a Blocked Brute-force Attack

If you have enabled an edition higher than HSS basic, HSS will protect your servers against brute-force attacks.

You can configure a login security policy to specify the brute force cracking determination mode and blocking duration. For details, see Login Security Check

If you have not configured any login security detection policy, the following default login security policy is used: HSS will block an IP address if it has five or more brute-force attack attempts detected within 30 seconds, or 15 or more brute-force attack attempts detected within 3,600 seconds.

If you receive an alarm indicating that an attack source IP address is blocked, check whether the source IP address is a trusted IP address.

Procedure

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 Detection > Alarms. Choose Abnormal User Behavior > Brute-force attacks to view account brute force events.
   Brute-force attack alarms will be generated if:

   • The system uses weak passwords, is under brute-force attacks, and attacker IP addresses are blocked.
   • Users fail to log in after several incorrect password attempts, and their IP addresses are blocked.

4. Check whether the login IP address triggering the alarm is valid.
   • If the IP address is valid,
     • To handle a false alarm, click Handle in the row of the alarm event. Mark this event as Ignore or Add to Login Whitelist.

       This does not unblock the IP address.

     • To unblock the IP address, click View Details under Blocked IP Addresses, select the IP address, and unblock it. Alternatively, you can just wait for it to be automatically unblocked when its blocking duration expires. The default blocking duration is 12 hours.
   • If the source IP address is invalid or unknown,

     Mark this event as handled.

     Immediately log in to your server and change your password to a stronger one. You can also enhance the defense against brute-force attacks by following the instructions provided in How Do I Defend Against Brute-force Attacks?

Helpful Links

• How Does HSS Intercept Brute Force Attacks?
• How Do I Unblock an IP Address?