Techniques › T1070.006 › AN1626
AN1626 Analytic 1626
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Detects attempts to modify file timestamps via API usage (e.g.,
SetFileTime), CLI tools (e.g., w32tm, PowerShell), or double-timestomp behavior where $SI and $FN timestamps are mismatched or reverted.</p>- Detects
- T1070.006 Timestomp
- Part of
- DET0591 Cross-Platform Behavioral Detection of File Timestomping via Metadata Tampering
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 |
|---|---|---|
| WinEventLog:Sysmon | EventCode=15 | DC0059 File Metadata |
| WinEventLog:Security | EventCode=4663, 4670, 4656 | DC0055 File Access |
| EDR:file | SetFileTime | DC0021 OS API Execution |
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 |
|---|---|
TimeWindow | Correlate timestamp change with preceding file creation or suspicious access |
APINamePattern | Include SetFileTime, NtSetInformationFile, or other timestamp APIs |
TimestampDeltaThreshold | Trigger on excessive backdating (e.g., >90 days) |