This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
« Potential Kerberos Attack via Bifrost Potential LSASS Clone Creation via PssCaptureSnapShot »
Elastic Docs ›Elastic Security Solution [master] ›Detections and alerts ›Prebuilt rule reference

Potential LSA Authentication Package Abuse

edit

Potential LSA Authentication Package Abuse

edit

Adversaries can use the autostart mechanism provided by the Local Security Authority (LSA) authentication packages for privilege escalation or persistence by placing a reference to a binary in the Windows registry. The binary will then be executed by SYSTEM when the authentication packages are loaded.

Rule type: eql

Rule indices:

  • 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
  • Privilege Escalation

Version: 100 (version history)

Added (Elastic Stack release): 7.12.0

Last modified (Elastic Stack release): 8.5.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule query

edit
registry where event.type == "change" and registry.path :
"HKLM\\SYSTEM\\*ControlSet*\\Control\\Lsa\\Authentication Packages"
and /* exclude SYSTEM SID - look for changes by non-SYSTEM user */
not user.id : "S-1-5-18"

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 100 (8.5.0 release)
  • Formatting only
Version 3 (8.4.0 release)
  • Formatting only
Version 2 (8.1.0 release)
  • Formatting only
« Potential Kerberos Attack via Bifrost Potential LSASS Clone Creation via PssCaptureSnapShot »