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 [7.16] ›Detections and alerts ›Prebuilt rule reference

Potential Persistence via Time Provider Modification

edit

Potential Persistence via Time Provider Modification

edit

Windows operating systems are utilizing the time provider architecture in order 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 System32 folder. The service W32Time initiates during the startup of Windows and loads w32time.dll. Adversaries may abuse this architecture to establish persistence, specifically by registering and enabling a malicious DLL as a time provider.

Rule type: eql

Rule indices:

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

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: 1

Added (Elastic Stack release): 7.12.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

« Potential Persistence via Periodic Tasks Potential Port Monitor or Print Processor Registration Abuse »