Help Center/ Host Security Service/ FAQs/ Brute-force Attack Defense/ How Does HSS Intercept Brute Force Attacks?
Updated on 2024-09-25 GMT+08:00
View PDF

How Does HSS Intercept Brute Force Attacks?

Types of Detectable Brute Force Attacks

HSS can detect the following types of brute force attacks:

  • Windows: SQL Server (automatic interception is not supported currently) and RDP
  • Linux: MySQL, vfstpd, and SSH

If MySQL, vfstpd, or SSH is installed on your server, after HSS is enabled, the agent will add rules to iptables to prevent brute force attacks. If a brute-force attack is detected, its source IP address will be added to the blocking list.

  • Added MySQL rule: IN_HIDS_MYSQLD_DENY_DROP
  • Added vfstpd rule: IN_HIDS_VSFTPD_DENY_DROP
  • Added SSH rule: If SSH on the server does not support the TCP Wrapper interception mode, the SSH uses iptables for interception. Therefore, the IN_HIDS_SSHD_DENY_DROP rule will be added to iptables. If you have configured an SSH login whitelist, the IN_HIDS_SSHD_DENY_DROP and IN_HIDS_SSHD_WHITE_LIST will be added to iptables.
Take the MySQL database as an example. Figure 1 shows the new rule.
Figure 1 Added MySQL rule

Existing iptables rules are used for blocking brute-force attacks. You are advised to keep them. If they are deleted, HSS will not be able to protect MySQL, vfstpd, or SSH from brute-force attacks.

How Brute Force Attacks Are Intercepted

Brute-force attacks are a type of common intrusion attacks. Attackers submit many server passwords until eventually guessing correctly and gaining control over a server.

HSS uses brute-force detection algorithms and an IP address blacklist to effectively prevent brute-force attacks and block attacking IP addresses. The blocking duration is 12 hours. If a blocked IP address does not perform brute-force attacks in the default blocking duration, it will be automatically unblocked. HSS supports 2FA to authenticate user identity, effectively preventing attackers from hacking accounts.

You can set common login IP addresses and SSH IP address whitelist that will not be blocked.

If HSS detects account cracking attacks on servers using Kunpeng EulerOS (EulerOS with Arm), it does not block the source IP addresses and only generates alarms. The SSH login IP address whitelist does not take effect for such servers.

Alarm Policies

  • If a hacker successfully cracks the password and logs in to a server, a real-time alarm will be immediately sent to specified recipients.
  • If a brute-force attack and risks of account hacking are detected, a real-time alarm will be immediately sent to specified recipients.
  • If a brute-force attack is detected and failed, and no unsafe settings (such as weak passwords) are detected on the server, no real-time alarms will be sent. HSS will summarize all attacks in a day in its daily alarm report. You can also view blocked attacks on the Detection & Response > Alarms page of the HSS console.

Viewing Brute Force Cracking Detection Results

  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. In the navigation pane, choose Detection & Response > Alarms.
  4. View the brute force cracking detection result of the server or container.

    • View the brute force cracking detection result of the server.
      1. Click the Server Alarms tab.
      2. In the Alarm Types area, select Abnormal User Behavior > Brute-force attacks to view alarm event records on the protected server.
      3. Click the value in the Blocked IP Addresses area to view the blocked attack source IP address, attack type, blocking status, blocking times, blocking start time, and latest blocking time.
        • Blocked indicates the brute-force attack has been blocked by HSS.
        • Canceled indicates you have unblocked the source IP address of the brute force attack.

          The default blocking duration is 12 hours. If a blocked IP address does not perform brute-force attacks in the default blocking duration, it will be automatically unblocked.

    • View the brute force cracking detection result of a container.
      1. Click the Container Alarms tab.
      2. In the Alarm Types area, select Abnormal User Behavior > Brute-force attacks to view alarm event records on the protected container.

Managing Blocked IP Addresses

  • If a server is frequently attacked, you are advised to fix its vulnerabilities in a timely manner and eliminate risks.

    You are advised to enable 2FA, and configure common login IP addresses and the SSH login IP whitelist.

  • If a valid IP address is blocked by mistake (for example, after O&M personnel enter incorrect passwords for multiple times), manually unblock the IP address.

    If you manually unblocked an IP address, but incorrect password attempts from this IP address exceed the threshold again, this IP address will be blocked again.