T1110.001 Sumo Logic CSE · Sumo

Detect Password Guessing in Sumo Logic CSE

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/

Sumo Detection Query

Sumo Logic CSE (Sumo)
sql
(_sourceCategory=Windows/Security OR _sourceCategory=OS/Windows/Security OR _sourceName=Security)
| where EventCode in ("4625", "4771", "4776")
| parse regex "(?:Target|Caller) User Name:\s+(?<TargetAccount>\S+)" nodrop
| parse regex "Source Network Address:\s+(?<SourceIP>[\d.:a-fA-F]+)" nodrop
| parse regex "Workstation Name:\s+(?<SourceWorkstation>\S+)" nodrop
| where !isNull(TargetAccount) and TargetAccount != "" and TargetAccount != "-"
| where toLowerCase(TargetAccount) != "anonymous logon"
| where !isNull(SourceIP) and SourceIP != "" and SourceIP != "-"
| where SourceIP != "127.0.0.1" and SourceIP != "::1"
| timeslice 10m
| eval DetectionType = if(EventCode=="4625", "Windows Logon Failure", if(EventCode=="4771", "Kerberos Pre-Auth Failure", "NTLM Auth Failure"))
| count as FailureCount, dcount(TargetAccount) as DistinctAccounts by _timeslice, _sourceHost, SourceIP, DetectionType
| where FailureCount >= 10
| eval Severity = if(FailureCount >= 50, "High", if(FailureCount >= 20, "Medium", "Low"))
| eval AttackPattern = if(DistinctAccounts > 3, "Password Spray Likely", "Password Guessing")
| fields _timeslice, _sourceHost, SourceIP, DetectionType, FailureCount, DistinctAccounts, Severity, AttackPattern
| sort by FailureCount
medium severity high confidence

Detects password guessing in Sumo Logic by parsing Windows Security Event Log records for authentication failures (EventCode 4625, 4771, 4776), grouping by source IP and host in 10-minute timeslices, and alerting when 10 or more failures are observed. Classifies whether behavior resembles targeted password guessing or broader password spraying based on distinct account count.

Data Sources

Windows Security Event Log via Sumo Logic Installed Collector (Source Category Windows/Security)Sumo Logic Cloud SIEM Windows event sensorWindows Event Collector forwarding to Sumo Logic HTTP source

Required Tables

Windows Security Event Log

False Positives & Tuning

  • Backup or endpoint management software (e.g., SCCM, Tanium) using service accounts with expired passwords that generate authentication failure bursts during scheduled scans or deployments
  • Users accessing multiple internal services simultaneously with cached browser credentials that became invalid after a password change, triggering failures across multiple systems at once
  • Network device discovery or inventory tools (e.g., SolarWinds, Nmap with NSE scripts) performing authenticated connectivity checks using default or test credentials against Windows hosts
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