Techniques › T1124 › AN0432
AN0432 Analytic 0432
macOS · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Process/script execution of systemsetup -gettimezone, date, ioreg, or API usage (timeIntervalSinceNow, gettimeofday) followed by time-based scheduling (launchd plist modification) or sleep-based execution.</p>
- Detects
- T1124 System Time Discovery
- Part of
- DET0151 Behavior-chain, platform-aware detection strategy for T1124 System Time Discovery
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| macos:unifiedlog | process exec events of systemsetup, date, ioreg with command_line parameters indicating time discovery | DC0032 Process Creation |
| macos:unifiedlog | New/modified launchd plist (persistence/scheduling) within TimeWindow after time query | DC0005 Scheduled Job Metadata |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
LaunchdPaths | Organization-specific list of allowed launchd write locations to filter benign agents. |
TimeWindow | Correlation window to link time discovery to launchd persistence/scheduling. |
AllowedCallers | Known management agents (e.g., JAMF) that legitimately call systemsetup/date. |