Credential Access

Brute-Force

Brute-Force

Detection overview

The "Brute-Force" detection focuses on identifying attempts to gain unauthorized access to user accounts through repetitive guessing of passwords. Brute-force attacks involve trying numerous combinations of usernames and passwords until the correct one is found. This detection is crucial as successful brute-force attacks can lead to unauthorized access, data breaches, and further exploitation within the network.

Triggers

  • An internal host is making many login attempts on an internal system, behavior which is consistent with a brute-force password attack
  • Such attacks can be performed via different protocols (e.g. RDP, VNC, SSH) and may also be a Heartbleed attack (e.g. memory scraping)

Possible Root Causes

  • An infected host or a malicious insider in control of the host is trying to guess passwords on another internal system
  • A misconfigured host is constantly trying to connect to one or more other internal systems

Business Impact

  • Successful harvesting of account credentials (usernames and password) of other accounts, particularly more privileged accounts, is a classic progression of a targeted attack
  • Even if triggered due to a misconfiguration, the identified misconfiguration is creating significant stress on the target system and should be cleaned up

Steps to Verify

  • Determine whether the internal host in question should be connecting to the target host; if not, this is likely malicious behavior
  • Determine which process on the internal host is sending traffic to the internal IP address(es) and ports; in Windows systems, this can be done using a combination of netstat and tasklist commands
  • Verify that the process should be running on the infected host and whether the process is configured correctly
Brute-Force

Possible root causes

Malicious Detection

  • An attacker is attempting to brute-force user accounts to gain unauthorized access.
  • Use of automated tools or scripts to perform brute-force attacks on login portals.
  • Insider threat where an employee is attempting to access restricted accounts.

Benign Detection

  • Users forgetting their passwords and repeatedly attempting to log in.
  • Misconfigured applications or systems causing repeated login attempts.
  • Penetration testing or security assessments involving brute-force attack simulations.
Brute-Force

Example scenarios

Scenario 1: An attacker uses a tool to perform a brute-force attack on a company's VPN login portal. The tool tries various combinations of usernames and passwords until it successfully gains access to an account. This detection is triggered by the high number of failed login attempts from a single IP address.

Scenario 2: During a penetration test, the security team simulates a brute-force attack on several user accounts to test the organization's defenses. The detection is triggered, and the activity is verified as part of the scheduled assessment.

Brute-Force

Business impact

If this detection indicates a genuine threat, the organization faces significant risks:

Account Compromise

Unauthorized access to user accounts can lead to further exploitation and data breaches.

Privilege Escalation

Compromised accounts with elevated privileges can be used to gain further access within the network.

Operational Disruption

Repeated login attempts can overwhelm authentication systems, causing delays or outages.

Brute-Force

Steps to investigate

Brute-Force

MITRE ATT&CK techniques covered

FAQs

What is a brute-force attack?

Can a brute force attack be detected?

What are the common signs of a brute-force attack?

Why is a brute-force attack a significant threat?

Can legitimate activities trigger the detection of brute-force attacks?

What steps should I take if I detect a brute-force attack?

How does Vectra AI detect brute-force attacks?

What is the business impact of a brute-force attack?

How can I prevent brute-force attacks?

What tools can help verify the presence of brute-force attacks?