IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Potential LSA Authentication Package Abuse Potential LSASS Memory Dump via PssCaptureSnapShot »
Elastic Docs ›Elastic Security Solution [8.1] ›Detections and alerts ›Prebuilt rule reference

Potential LSASS Clone Creation via PssCaptureSnapShot

edit

Potential LSASS Clone Creation via PssCaptureSnapShot

edit

Identifies the creation of an LSASS process clone via PssCaptureSnapShot where the parent process is the initial LSASS process instance. This may indicate an attempt to evade detection and dump LSASS memory for credential access.

Rule type: eql

Rule indices:

  • winlogbeat-*
  • logs-windows.*

Severity: high

Risk score: 73

Runs every: 5 minutes

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

Maximum alerts per execution: 100

References:

Tags:

  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Credential Access

Version: 1

Added (Elastic Stack release): 8.0.0

Rule authors: Elastic

Rule license: Elastic License v2

Investigation guide

edit
## Config

This is meant to run only on datasources using Windows security event 4688 that captures the process clone creation.

Rule query

edit
process where event.code:"4688" and process.executable :
"?:\\Windows\\System32\\lsass.exe" and process.parent.executable :
"?:\\Windows\\System32\\lsass.exe"

Threat mapping

edit

Framework: MITRE ATT&CKTM

« Potential LSA Authentication Package Abuse Potential LSASS Memory Dump via PssCaptureSnapShot »