ATT&CK coverage › Technique
Brute Force T1110
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained. Without knowledge of the password for an account or set of accounts, an adversary may systematically guess the password using a repetitive or iterative mechanism. Brute forcing passwords can take place via interaction with a service that will check the validity of those credentials or offline against previously acquired credential data, such as password hashes.
Events covered
13 catalog events are tagged with this technique by at least one rule.
Authoring guide
Patterns shared across the 13 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (24 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (59 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.
Common exclusions (17 distinct)
Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 4 rules
- External Remote RDP Logon from Public IP
- External Remote SMB Logon from Public IP
- HackTool - CrackMapExec Execution
- HackTool - Hydra Password Bruteforce Execution
Elastic 3 rules
- Multiple Logon Failure Followed by Logon Success
- Multiple Logon Failure from the same Source Address
- Privileged Accounts Brute Force
Kusto Query Language 6 rules
- Brute force attack against user credentials (Uses Authentication Normalization)
- Excessive Windows Logon Failures
- Failed logon attempts by valid accounts within 10 mins
- Potential Password Spray Attack (Uses Authentication Normalization)
- Remote Desktop Network Brute force (ASIM Network Session schema)
- SecurityEvent - Multiple authentication failures followed by a success