splunk-security_content/detections/endpoint/windows_nirsoft_advancedrun.yml

name: Windows NirSoft AdvancedRun
id: bb4f3090-7ae4-11ec-897f-acde48001122
version: 2
date: '2024-05-14'
author: Michael Haag, Splunk
status: production
type: TTP
description: The following analytic detects the execution of AdvancedRun.exe, a tool
  with capabilities similar to remote administration programs like PsExec. It identifies
  the process by its name or original file name and flags common command-line arguments.
  This detection leverages data from Endpoint Detection and Response (EDR) agents,
  focusing on process and command-line telemetry. Monitoring this activity is crucial
  as AdvancedRun can be used for remote code execution and configuration-based automation.
  If malicious, this could allow attackers to execute arbitrary commands, escalate
  privileges, or maintain persistence within the environment.
data_source:
- Sysmon EventID 1
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time)
  as lastTime from datamodel=Endpoint.Processes where (Processes.process_name=advancedrun.exe
  OR Processes.original_file_name=advancedrun.exe) Processes.process IN ("*EXEFilename*","*/cfg*","*RunAs*",
  "*WindowState*") by Processes.dest Processes.user Processes.parent_process_name
  Processes.process_name Processes.process Processes.original_file_name Processes.process_id
  Processes.parent_process_id | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)`|
  `security_content_ctime(lastTime)` | `windows_nirsoft_advancedrun_filter`'
how_to_implement: The detection is based on data that originates from Endpoint Detection
  and Response (EDR) agents. These agents are designed to provide security-related
  telemetry from the endpoints where the agent is installed. To implement this search,
  you must ingest logs that contain the process GUID, process name, and parent process.
  Additionally, you must ingest complete command-line executions. These logs must
  be processed using the appropriate Splunk Technology Add-ons that are specific to
  the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint`
  data model. Use the Splunk Common Information Model (CIM) to normalize the field
  names and speed up the data modeling process.
known_false_positives: False positives should be limited as it is specific to AdvancedRun.
  Filter as needed based on legitimate usage.
references:
- http://www.nirsoft.net/utils/advanced_run.html
- https://www.microsoft.com/security/blog/2022/01/15/destructive-malware-targeting-ukrainian-organizations/
tags:
  analytic_story:
  - Ransomware
  - Unusual Processes
  - Data Destruction
  - WhisperGate
  asset_type: Endpoint
  confidence: 100
  impact: 60
  message: An instance of advancedrun.exe, $process_name$, was spawned by $parent_process_name$
    on $dest$ by $user$.
  mitre_attack_id:
  - T1588.002
  observable:
  - name: user
    type: User
    role:
    - Victim
  - name: dest
    type: Hostname
    role:
    - Victim
  - name: parent_process_name
    type: Process
    role:
    - Parent Process
  - name: process_name
    type: Process
    role:
    - Child Process
  product:
  - Splunk Enterprise
  - Splunk Enterprise Security
  - Splunk Cloud
  required_fields:
  - _time
  - Processes.dest
  - Processes.user
  - Processes.parent_process_name
  - Processes.parent_process
  - Processes.original_file_name
  - Processes.process_name
  - Processes.process
  - Processes.process_id
  - Processes.parent_process_path
  - Processes.process_path
  - Processes.parent_process_id
  risk_score: 60
  security_domain: endpoint
tests:
- name: True Positive Test
  attack_data:
  - data: 
      https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1588.002/atomic_red_team/windows-sysmon.log
    source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
    sourcetype: xmlwineventlog