T1588.005 Sumo Logic CSE · Sumo

Detect Exploits in Sumo Logic CSE

Adversaries may buy, steal, or download exploits that can be used during targeting. An exploit takes advantage of a bug or vulnerability in order to cause unintended or unanticipated behavior to occur on computer hardware or software. Rather than developing their own exploits, an adversary may find, modify, or purchase exploits from online sources, exploit vendors, criminal marketplaces (including exploit kits), or from other threat actors. Adversaries such as Ember Bear have obtained exploitation scripts against publicly-disclosed vulnerabilities from public repositories, while Kimsuky has obtained exploit code for various CVEs. Acquired exploits may be used across multiple phases of the adversary lifecycle including initial access, privilege escalation, defense evasion, credential access, and lateral movement. Because the acquisition of exploits occurs entirely on adversary-controlled infrastructure, direct detection is not possible from victim telemetry — detection must focus on observable indicators when those acquired exploits are deployed.

MITRE ATT&CK

Tactic
Resource Development
Technique
T1588 Obtain Capabilities
Sub-technique
T1588.005 Exploits
Canonical reference
https://attack.mitre.org/techniques/T1588/005/

Sumo Detection Query

Sumo Logic CSE (Sumo)
sql
_sourceCategory=*windows*sysmon* OR _sourceCategory=*winevent*sysmon*
| where EventCode = "1" OR EventID = "1"
| parse field=ParentImage "*\\*" as _parent_dir, parent_process nodrop
| parse field=Image "*\\*" as _child_dir, child_process nodrop
| where parent_process in (
    "winword.exe", "excel.exe", "powerpnt.exe", "outlook.exe",
    "mspub.exe", "onenote.exe", "msaccess.exe",
    "acrord32.exe", "acrobat.exe",
    "chrome.exe", "firefox.exe", "msedge.exe", "iexplore.exe",
    "java.exe", "javaw.exe", "javaws.exe"
  )
| where child_process in (
    "cmd.exe", "powershell.exe", "pwsh.exe",
    "wscript.exe", "cscript.exe", "mshta.exe",
    "rundll32.exe", "regsvr32.exe", "certutil.exe",
    "bitsadmin.exe", "msiexec.exe", "wmic.exe",
    "msbuild.exe", "installutil.exe", "regasm.exe",
    "regsvcs.exe", "schtasks.exe"
  )
| eval cmdline = toLowerCase(CommandLine)
| eval NetworkIndicator = if (
    cmdline matches ".*?(http://|https://|ftp://|invoke-webrequest|net\.webclient|downloadstring|downloadfile|start-bitstransfer|curl |wget ).*",
    1, 0
  )
| eval CredentialAccess = if (
    cmdline matches ".*?(mimikatz|lsass|sekurlsa|ntds|procdump|comsvcs|minidump|vaultcmd).*",
    1, 0
  )
| eval PersistenceIndicator = if (
    cmdline matches ".*?(schtasks|reg add|currentversion.run|startup|userinit|sc create|sc config).*",
    1, 0
  )
| eval LateralMovement = if (
    cmdline matches ".*?(psexec|wmiexec|winrm|net use|enter-pssession|invoke-command|ssh ).*",
    1, 0
  )
| eval ExploitScore = NetworkIndicator + CredentialAccess + PersistenceIndicator + LateralMovement + 1
| fields _time, Computer, User, parent_process, ParentCommandLine, child_process, CommandLine,
    NetworkIndicator, CredentialAccess, PersistenceIndicator, LateralMovement, ExploitScore
| sort by ExploitScore desc, _time desc
high severity medium confidence

Detects potential exploit deployment (T1588.005) in Sumo Logic by parsing Sysmon Process Create (EventID 1) events. Extracts process names from ParentImage and Image path fields, filters for known exploitable application parents spawning suspicious LOLBin children, and evaluates post-exploitation command-line indicators to produce a composite ExploitScore. Higher scores indicate stronger exploit deployment confidence across network callback, credential access, persistence, and lateral movement dimensions.

Data Sources

Sumo Logic Installed Collector with Windows Event Log Source (Sysmon channel)Sumo Logic Cloud Syslog (Sysmon forwarded via NXLog or Winlogbeat)

Required Tables

_sourceCategory matching *windows*sysmon* or *winevent*sysmon*

False Positives & Tuning

  • Legitimate Office automation macros used in finance or HR departments for Excel-to-PowerShell report generation, SharePoint uploads, or mail-merge workflows
  • Acrobat Reader spawning cmd.exe when invoking system-registered print handlers or opening linked file attachments from PDF documents
  • Chrome or Firefox launching wscript.exe or cscript.exe as part of enterprise intranet web application legacy ActiveX fallback shims or Kerberos SSO helper scripts
  • Java-based middleware platforms (WebLogic, JBoss, Tomcat catalina.sh equivalents on Windows) that use javaw.exe to spawn cmd.exe or PowerShell for service lifecycle management
  • Penetration testing or red team exercises on endpoints where Office-based macro payload delivery is used for authorized attack simulation
Download portable Sigma rule (.yml)

Other platforms for T1588.005


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 1Simulate Document Exploit Process Chain (cmd Reconnaissance)

    Expected signal: Sysmon Event ID 1: Process Create with Image=cmd.exe. CommandLine contains 'whoami', 'hostname', 'ipconfig', 'net user'. Security Event ID 4688 (with command line auditing enabled) records the same. When run from a Word macro, InitiatingProcessFileName=winword.exe triggers the detection's parent-child matching logic.

  2. Test 2Simulate Browser Exploit Network Callback (Stage-2 Download Cradle)

    Expected signal: Sysmon Event ID 1: Process Create for powershell.exe with CommandLine containing 'Net.WebClient', 'DownloadString', and the target URL. Sysmon Event ID 3: Network Connection attempt to 192.0.2.1:4444 (TEST-NET-1 per RFC 5737 — safe non-routable address that generates telemetry without reaching any real host). PowerShell ScriptBlock Log Event ID 4104 captures the full script content.

  3. Test 3VBScript-Based Exploit Payload Simulation

    Expected signal: Sysmon Event ID 1 (x2): First for powershell.exe creating the VBS file, second for wscript.exe executing it. The char()-based obfuscation in the VBS content mimics obfuscation patterns used in real exploit-delivered payloads. Sysmon Event ID 11: File Create event for the VBS file dropped to TEMP. PowerShell ScriptBlock Log Event ID 4104 for the PowerShell wrapper.

  4. Test 4Exploit Guard ASR Rule Configuration Audit

    Expected signal: PowerShell ScriptBlock Log Event ID 4104 for the MpPreference query. Informational output to file showing which ASR rules are active. When ASR rules are in block mode and a real Office application attempts to spawn a child process (e.g., via a macro), Windows Defender Operational log generates Event ID 1121 (Blocked) or Event ID 1122 (Audit) with the rule GUID and process details.

  5. Test 5Simulate Post-Exploit Process Access (Sysmon Event ID 10)

    Expected signal: Sysmon Event ID 10 (ProcessAccess): SourceImage=powershell.exe, TargetImage=notepad.exe, GrantedAccess=0x0410 (PROCESS_QUERY_INFORMATION | PROCESS_VM_READ). Sysmon Event ID 1: powershell.exe process create. The 0x0410 access mask is characteristic of credential dumping tools and shellcode injection staging — many SIEM rules alert on this mask from non-system processes targeting sensitive processes.

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections