PH_Rule_SIGMA_2615
Enabled
Detects the use of the WMI command-line (WMIC) utility to identify and display various system information, including OS, CPU, GPU, and disk drive names; memory capacity; display resolution; and baseboard, BIOS, and GPU driver products/versions. Some of these commands were used by Aurora Stealer in late 2022/early 2023. . This rule is adapted from https://github.com/SigmaHQ/sigma/blob/master/rules/windows/process_creation/proc_creation_win_wmic_recon_system_info_discovery.yml
5
Security
Discovery
Discovery consists of techniques an adversary may use to gain knowledge about the system and internal network. These techniques help adversaries observe the environment and orient themselves before deciding how to act. They also allow adversaries to explore what they can control and what’s around their entry point in order to discover how it could benefit their current objective. Native operating system tools are often used toward this post-compromise information-gathering objective.
https://attack.mitre.org/tactics/TA0007T1082
System Information Discovery
An adversary may attempt to get detailed information about the operating system and hardware, including version, patches, hotfixes, service packs, and architecture. Adversaries may use the information from during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions. Tools such as Systeminfo can be used to gather detailed system information. A breakdown of system data can also be gathered through the macOS "systemsetup" command, but it requires administrative privileges. Infrastructure as a Service (IaaS) cloud providers such as AWS, GCP, and Azure allow access to instance and virtual machine information via APIs. Successful authenticated API calls can return data such as the operating system platform and status of a particular instance or the model view of a virtual machine.
https://attack.mitre.org/techniques/T1082Server
Windows Sysmon via FortiSIEM Agent
Correlation
No remediation guidance specified
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
300 seconds
If the following defined pattern/s occur within a 300 second time window.
Filter
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
eventType="Win-Sysmon-1-Create-Process" AND (description="WMI Commandline Utility" OR srcFileName="wmic.exe" OR procName REGEXP "\\WMIC\.exe$") AND command REGEXP ".*DISKDRIVE get Caption.*|.*LOGICALDISK get Name,Size,FreeSpace.*|.*MEMPHYSICAL get MaxCapacity.*|.*OS get Caption,OSArchitecture,Version.*|.*baseboard get product.*|.*baseboard get version.*|.*bios get SMBIOSBIOSVersion.*|.*cpu get name.*|.*path win32_VideoController get DriverVersion.*|.*path win32_VideoController get VideoModeDescription.*|.*path win32_VideoController get name.*"
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
command,description,hostName,procName,srcFileName
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT(*) >= 1
This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.
The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern
command = Filter.command,
description = Filter.description,
hostName = Filter.hostName,
procName = Filter.procName,
srcFileName = Filter.srcFileName