T1110.001 CrowdStrike LogScale · LogScale

Detect Password Guessing in CrowdStrike LogScale

Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts. Without knowledge of the password for an account, an adversary may opt to systematically guess the password using a repetitive or iterative mechanism. An adversary may guess login credentials without prior knowledge of system or environment passwords during an operation by using a list of common passwords. Password guessing may or may not take into account the target's policies on password complexity or use policies that may lock accounts out after a number of failed attempts. Commonly targeted services include SSH, RDP, SMB, LDAP, Kerberos, FTP, MSSQL, MySQL, VNC, and web management portals. Threat actors such as APT28, APT29, Emotet, and tools like CrackMapExec have leveraged this technique extensively.

MITRE ATT&CK

Tactic
Credential Access
Technique
T1110 Brute Force
Sub-technique
T1110.001 Password Guessing
Canonical reference
https://attack.mitre.org/techniques/T1110/001/

LogScale Detection Query

CrowdStrike LogScale (LogScale)
cql
#event_simpleName = UserLogonFailed2
| RemoteAddressIP4 != "127.0.0.1"
| RemoteAddressIP4 != "::1"
| RemoteAddressIP4 != ""
| UserName != ""
| UserName != "-"
| UserName != "ANONYMOUS LOGON"
| bucket(span=10min, function=[
    count(as=FailureCount),
    count(UserName, distinct=true, as=DistinctAccounts),
    collect([UserName], max=20, as=Accounts),
    min(@timestamp, as=FirstSeen),
    max(@timestamp, as=LastSeen)
  ], by=[ComputerName, RemoteAddressIP4])
| FailureCount >= 10
| case {
    FailureCount >= 50 | Severity := "High";
    FailureCount >= 20 | Severity := "Medium";
    * | Severity := "Low"
  }
| case {
    DistinctAccounts > 3 | AttackPattern := "Password Spray Likely";
    * | AttackPattern := "Password Guessing"
  }
| sort(FailureCount, order=desc)
medium severity medium confidence

Detects password guessing using CrowdStrike Falcon's UserLogonFailed2 endpoint telemetry events in LogScale (CQL), grouping authentication failures in 10-minute buckets by source IP and host. Alerts when 10 or more failures are observed and classifies the attack pattern as targeted guessing or spray based on the number of distinct accounts targeted.

Data Sources

CrowdStrike Falcon Endpoint Agent (UserLogonFailed2 event stream)CrowdStrike Falcon Data Replicator (FDR) streaming to LogScaleCrowdStrike LogScale (Humio) ingestion pipeline

Required Tables

Falcon event stream: UserLogonFailed2

False Positives & Tuning

  • Endpoint management agents (SCCM, Microsoft Intune, Tanium) using cached service account credentials that expired, generating periodic UserLogonFailed2 bursts during scheduled compliance scans or software deployments
  • Users actively recovering from an account lockout by repeatedly attempting to authenticate while a password reset request is being processed by the helpdesk
  • Internal red team or security assessment programs running authorized credential testing tools (e.g., CrackMapExec in lab scope, Metasploit auxiliary modules) against sanctioned target systems within a defined engagement window
Download portable Sigma rule (.yml)

Other platforms for T1110.001


Testing Methodology

Validate this detection against 5 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1RDP Password Guessing with Hydra

    Expected signal: Windows Security Event ID 4625 (Logon Failure) with LogonType=10 (RemoteInteractive) on the target system, source IP matching the attacker host. Multiple failures in rapid succession. Network flow logs showing repeated TCP connections to port 3389 from attacker IP.

  2. Test 2SMB Password Guessing with CrackMapExec

    Expected signal: Windows Security Event ID 4625 (Logon Failure) with LogonType=3 (Network) and SubStatus 0xC000006A (wrong password) on the target DC/server. Event ID 4776 (NTLM validation failure) may also appear. Sysmon Event ID 3 on the attacker host showing outbound connections to port 445.

  3. Test 3SSH Password Guessing using Hydra on Linux

    Expected signal: Linux syslog/auth.log entries: 'Failed password for <user> from <attacker_ip> port <port> ssh2' and 'Invalid user <user> from <attacker_ip>'. Multiple entries in rapid succession from attacker IP. Possible PAM failure events if auditd is configured.

  4. Test 4Windows Local Account Password Guessing via Net Use

    Expected signal: Windows Security Event ID 4625 (Logon Failure) on the target host with LogonType=3 (Network), SubStatus=0xC000006A (wrong password), and source IP matching the test machine. Sysmon Event ID 1 on the attacker machine showing cmd.exe spawning with 'net use' command line. Security Event ID 4648 (logon with explicit credentials) may also appear.

  5. Test 5Azure AD / Office 365 Password Guessing via MSOLSpray

    Expected signal: Azure AD SigninLogs / AADSignInLogs in Microsoft Sentinel: ResultType = 50126 (invalid username or password) or 50053 (account locked out), with repeated entries from same IP. UserAgent reflecting PowerShell/HTTP client. Office 365 Unified Audit Log: UserLoginFailed operation with ClientInfoString showing legacy auth client.

Unlock Pro Content

Get the full detection package for T1110.001 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections