IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Potential Persistence via Periodic Tasks Potential Port Monitor or Print Processor Registration Abuse »
Elastic Docs ›Elastic Security Solution [8.4] ›Detections and alerts ›Prebuilt rule reference

Potential Persistence via Time Provider Modification

edit

Potential Persistence via Time Provider Modification

edit

Identifies modification of the Time Provider. Adversaries may establish persistence by registering and enabling a malicious DLL as a time provider. Windows uses the time provider architecture to obtain accurate time stamps from other network devices or clients in the network. Time providers are implemented in the form of a DLL file which resides in the System32 folder. The service W32Time initiates during the startup of Windows and loads w32time.dll.

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

References:

Tags:

  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Persistence

Version: 4 (version history)

Added (Elastic Stack release): 7.12.0

Last modified (Elastic Stack release): 8.4.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule query

edit
registry where event.type:"change" and registry.path:"HKLM\\SYSTEM\\
*ControlSet*\\Services\\W32Time\\TimeProviders\\*" and
registry.data.strings:"*.dll"

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 4 (8.4.0 release)
  • Formatting only
Version 3 (8.2.0 release)
  • Formatting only
Version 2 (8.1.0 release)
  • Formatting only
« Potential Persistence via Periodic Tasks Potential Port Monitor or Print Processor Registration Abuse »