MITRE ATT&CK tracks Brute Force as T1110 under Credential Access. It covers repeated password attempts against a login service and attempts to recover a password from stolen hashes. The four sub-techniques differ in the credential material used and the way accounts are targeted.
How it works
MITRE says an adversary can test passwords through a service or work offline with acquired password hashes. T1110.001, Password Guessing, tries possible passwords for an account. T1110.002, Password Cracking, attempts to recover a usable password from a hash. The second method may leave no login failures on the target service while the cracking takes place.
T1110.003, Password Spraying, tests one or a small set of passwords across many accounts. T1110.004, Credential Stuffing, tests username and password pairs obtained from another breach. The password spraying explainer and credential stuffing explainer cover each method in more detail. For the broad meaning of repeated password attempts, see the brute force attack glossary entry.
MITRE places this behavior near Account Discovery (T1087), which can provide account names, and Valid Accounts (T1078), which can follow a successful guess. It also notes that brute forcing can accompany External Remote Services (T1133) during initial access. These are related behaviors, not additional T1110 sub-techniques.
A real example
MITRE lists APT28 as a group that can perform brute force attacks to obtain credentials. This is a cataloged procedure example, not evidence that every failed login from an unknown source belongs to APT28. Compare account, source, time, and success events before assigning an incident to T1110.
Who uses it
How to detect
-
Failures followed by success for one account
MITRE's DET0463 analytic AN1275 correlates many failed Windows logons with a later success from a suspicious user, host, or time window. Check the same account and source together before treating this sequence as a lead.
-
One source testing many accounts
DET0463 analytic AN1277 looks for attempts across a user pool in identity provider sign-in logs. A low number of failures per account can still matter when the same source reaches many users, as in password spraying.
-
Repeated failures across platforms
DET0463 also names Linux audit records, macOS unified logs, and SaaS sign-in logs. Correlate source, target account, and time across those records, then check for a later success. A quiet login log does not rule out offline password cracking.
-
Check the success and account context
MITRE's Windows and Linux analytics both include a success after failed attempts. Review whether the source is expected, which account was used, and whether the success led to access. Tune known monitoring sources to reduce routine noise.
How to defend
-
Limit failed attempts
NIST SP 800-63B requires a rate-limiting mechanism for failed password authentication attempts. Apply limits per subscriber account and watch the effect on legitimate users. MITRE warns that overly strict lockouts can deny users access.
-
Use multi-factor authentication
MITRE lists multi-factor authentication as a T1110 mitigation and recommends enabling it on externally facing services where possible. A guessed password alone should not complete a protected sign-in.
-
Reject common and exposed passwords
NIST says verifiers must compare new passwords with a blocklist of common, expected, or compromised values. It also advises distinct passwords across services to reduce credential stuffing.
-
Protect stored password hashes
NIST says verifiers must salt and hash stored passwords with a suitable scheme and cost factor. This raises the cost of offline guesses if an attacker obtains hashes. Online rate limits do not apply to that offline work.
Frequently Asked Questions
Does T1110 include offline password cracking?
Yes. MITRE includes Password Cracking (T1110.002), which attempts to recover passwords from acquired hashes. The cracking can take place outside the target network.
What separates password spraying from password guessing?
MITRE describes spraying as testing one or a few passwords against many accounts. Password guessing tests possible passwords for an account. This difference changes whether analysts group failures by source, account, or both.
Which log sequence deserves investigation first?
MITRE DET0463 highlights repeated authentication failures followed by a success. Also check a source that reaches many accounts within a short window, even if each account has few failures.
Sources
- Brute Force, Technique T1110MITRE ATT&CK
- Brute Force: Password Guessing, T1110.001MITRE ATT&CK
- Brute Force: Password Cracking, T1110.002MITRE ATT&CK
- Brute Force: Password Spraying, T1110.003MITRE ATT&CK
- Brute Force: Credential Stuffing, T1110.004MITRE ATT&CK
- Brute Force Authentication Failures with Multi-Platform Log Correlation, DET0463MITRE ATT&CK
- NIST Special Publication 800-63B: Authentication and Authenticator ManagementNIST
