System Time Discovery T1124

Tactic: Discovery

An adversary may gather the system time and/or time zone settings from a local or remote system. The system time is set and stored by services, such as the Windows Time Service on Windows or systemsetup on macOS. These time settings may also be synchronized between systems and services in an enterprise network, typically accomplished with a network time server within a domain.

Events covered

2 catalog events are tagged with this technique by at least one rule.

Authoring guide

Patterns shared across the 6 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (8 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
CommandLine4contains 3, regex_match 1 /computer:localhost , /dataonly , /period:, (?i)net.*?time.*?\x5c\x5c, /computer:
Image2ends_with 2\w32tm.exe, \net.exe, \net1.exe
process_name2eq 2net.exe, net1.exe, tzutil.exe, w32tm.exe
EventID1eq 14688
OriginalFileName1eq 1w32time.dll
Type1eq 1
event.type1eq 1start
process.args1eq 1/g, /tz, time

Top indicator values (26 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.

FieldKindValueRules (here)Corpus reach
Imageends_with
\w32tm.exe
22
Imageends_with
\net.exe
149
Imageends_with
\net1.exe
147
process_nameeq
w32tm.exe
23
process_nameeq
net.exe
122
process_nameeq
net1.exe
135
process_nameeq
tzutil.exe
12
CommandLinecontains
/computer:localhost
1
CommandLinecontains
/dataonly
1
CommandLinecontains
/period:
1
CommandLinecontains
/samples:
1
CommandLinecontains
/stripchart
1
CommandLinecontains
/computer:
12
CommandLinecontains
/dataonly
1
CommandLinecontains
/period:
1
CommandLinecontains
/samples:
1
CommandLinecontains
/stripchart
1
CommandLinecontains
time
1
CommandLinecontains
tz
1
CommandLineregex_match
(?i)net.*?time.*?\x5c\x5c
1
EventIDeq
4688
1313
OriginalFileNameeq
w32time.dll
1
event.typeeq
start
1606
process.argseq
/g
1
process.argseq
/tz
1
process.argseq
time
12

Exclusions (3 distinct)

Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.

FieldKindValueRules excluding
user.ideq
S-1-5-18
1
user.ideq
S-1-5-19
1
user.ideq
S-1-5-20
1

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Platform (all)
Domain (all)

Sigma 3 rules

Elastic 1 rule

Splunk 2 rules