IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Suspicious PrintSpooler Service Executable File Creation Suspicious Process from Conhost »
Elastic Docs ›Elastic Security Solution [7.10] ›Detections and Alerts ›Prebuilt rule reference

Suspicious Process Execution via Renamed PsExec Executable

edit

Suspicious Process Execution via Renamed PsExec Executable

edit

Identifies suspicious psexec activity which is executing from the psexec service that has been renamed, possibly to evade detection.

Rule type: query

Rule indices:

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

Severity: medium

Risk score: 47

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

Tags:

  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Execution

Version: 1

Added (Elastic Stack release): 7.10.0

Rule authors: Elastic

Rule license: Elastic License

Rule query

edit
event.category:process and event.type:(start or process_started) and
(process.pe.original_file_name:(psexesvc.exe or PSEXESVC.exe) or
winlog.event_data.OriginalFileName:(psexesvc.exe or PSEXESVC.exe)) and
process.parent.name:services.exe and not process.name:(psexesvc.exe or
PSEXESVC.exe)

Threat mapping

edit

Framework: MITRE ATT&CKTM

« Suspicious PrintSpooler Service Executable File Creation Suspicious Process from Conhost »