Security Software Discovery using WMIC

Elastic Stack Serverless Security

Identifies the use of Windows Management Instrumentation Command (WMIC) to discover certain System Security Settings such as AntiVirus or Host Firewall details.

Rule type: eql

Rule indices:

• logs-endpoint.events.*
• winlogbeat-*
• logs-windows.*

Severity: medium

Risk score: 47

Runs every: 5m

Searches indices from: now-9m (https://www.elastic.co/guide/en/elasticsearch/reference/current/common-options.html#date-math[Date Math format], see also Additional look-back time)

Maximum alerts per execution: 100

References: None

Tags:

• Elastic
• Host
• Windows
• Threat Detection
• Discovery

Version: 5

Rule authors:

• Elastic

Rule license: Elastic License v2

If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2, events will not define event.ingested and default fallback for EQL rules was not added until 8.2, so you will need to add a custom pipeline to populate event.ingested to @timestamp for this rule to work.

process where event.type in ("start", "process_started") and
   (process.name:"wmic.exe" or process.pe.original_file_name:"wmic.exe") and
    process.args:"/namespace:\\\\root\\SecurityCenter2" and process.args:"Get"

Framework: MITRE ATT&CKTM

• Tactic:

  • Name: Discovery
  • ID: TA0007
  • Reference URL: https://attack.mitre.org/tactics/TA0007/

• Technique:

  • Name: Software Discovery
  • ID: T1518
  • Reference URL: https://attack.mitre.org/techniques/T1518/

• Sub-technique:

  • Name: Security Software Discovery
  • ID: T1518.001
  • Reference URL: https://attack.mitre.org/techniques/T1518/001/