Anti-Forensics Field Manual

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Report Timeline Exhibits ======

===== Definition =====
Report Timeline Exhibits is a log or timeline concept used to organize events, test sequence, and decide how much confidence a chronology deserves.
In a forensic report, report timeline exhibits should be treated as a source of evidence and uncertainty, not as a shortcut to intent. The useful question is what the record supports, what it does not support, and what another source says when asked the same question.

===== Background =====
Timelines are useful until someone treats them like prophecy. Logs can be late, clocks can drift, and duplicate timestamps can stand in a row looking innocent.
For practitioners, the value is not drama; it is knowing which facts can survive review and which ones need to stay in the notes. Timestamps have alibis. Some are good. Some were written by clocks that should not be allowed near evidence.

===== Technical Description =====
Analysis compares event sources, record IDs, clock settings, timezone handling, collection timing, retention behavior, and independent artifact support.
A careful review starts with the source format and collection method before it argues about meaning.

===== Forensic Relevance =====
  * **Timeline reconstruction:** Report Timeline Exhibits helps test sequence, event order, and whether timestamps agree with the surrounding record.
  * **Gap analysis:** It can distinguish suspicious gaps from retention, rollover, disabled logging, or collection limits.
  * **Contradiction testing:** It is useful when logs, metadata, endpoint telemetry, and account activity tell different stories.
  * **Attribution limits:** It can support account or host context without proving who was at the keyboard.
  * **Reporting decisions:** It helps keep conclusions about report timeline exhibits proportional to the number and quality of sources.

===== Evidence Sources =====
^ Evidence source ^ What it may show ^ Reliability limits ^ What it cannot prove alone ^
| Event records | Show discrete actions, status changes, failures, or detections. | Provider behavior and configuration define what gets logged. | Do not prove the whole event sequence. |
| Clock and timezone settings | Help normalize times across systems. | Manual changes, drift, and daylight saving rules can distort comparison. | Do not make all timestamps equally reliable. |
| Retention and rotation settings | Explain missing or truncated logs. | Can look suspicious even when policy caused the gap. | Do not prove tampering by themselves. |
| Cross-source timelines | Show whether independent systems agree. | Different systems record different parts of the event. | Do not remove interpretation limits. |

===== Interpretation Limits =====
The most common error is treating report timeline exhibits as proof of motive. It may support a technical event, a sequence, or a contradiction, but motive needs stronger ground.
Another bad leap is treating absence as intent. Missing data can come from retention, configuration, collection scope, sync behavior, overwriting, media behavior, or ordinary use.
A tool result should be described as a parsed or recovered record, not as the tool's opinion about what happened. Tools surface evidence; they do not understand it.
Duplicate timestamps standing in formation are still not proof of conspiracy.

===== Common Misinterpretations =====
  * Mixing local time, UTC, and normalized time without labeling the mess.
  * Ignoring cross-host clock differences because the chart looked neat.
  * Treating report timeline exhibits as proof that a specific user acted, when the artifact only supports system or account context.
  * Treating a timestamp as exact truth without checking timezone, clock drift, and source semantics.
  * Ignoring benign explanations because the suspicious explanation is easier to write.

===== Example Scenario =====
During follow-up analysis, event records becomes the strongest visible record tied to report timeline exhibits.
The finding may support activity in the relevant time window, but it does not prove who caused it or why.
The careful next step is to normalize the time source, compare independent artifacts, and write the finding as support rather than proof.

===== Analysis Workflow =====
  - Define the question before opening another parser: what should Report Timeline Exhibits help answer?
  - Preserve the source evidence and document how the event records were collected.
  - Record tool versions, input paths, output paths, time settings, and errors.
  - Identify observed facts before writing any interpretation.
  - Normalize time sources and document timezone, clock drift, and collection-time effects.
  - Compare at least two independent artifact families before raising confidence.
  - Consider benign explanations, automated behavior, retention, sync, and storage-device behavior.
  - Write conclusions proportionally: observed fact first, inference second, uncertainty always visible.

===== Reporting Guidance =====
Reporting on report timeline exhibits should be precise enough that another analyst can retrace the claim without inheriting the original examiner's confidence.
Avoid wording that converts possibility into intent. The report should not say a user deliberately deleted, hid, wiped, or tampered with evidence unless the evidence actually supports that conclusion.
Report-ready wording:
  * The available event records are consistent with activity related to report timeline exhibits, but they do not independently establish motive or user intent.
  * Recovery was limited under the examined conditions; additional corroboration would be required before concluding deliberate destruction.
  * The finding should be read with the collection scope, time-source limits, and alternate explanations described in this report.

===== Confidence and Reliability =====
^ Confidence level ^ What it looks like for this topic ^ How to report it ^
| Low | Event records exist, but collection scope, time source, or surrounding context is limited. | State the observation and keep interpretation narrow. |
| Moderate | Event records align with Clock and timezone settings, but attribution or intent remains unresolved. | Say the artifacts support the finding, not that they prove it. |
| High | Multiple independent sources agree on sequence, source system, account context, and collection conditions. | Use stronger language, but still separate observed facts from inference. |

===== Related Concepts =====
  * [[wiki:digital_forensics:logs_timelines:super_timeline|Super Timeline]] - Helps keep the finding grounded in a wider evidence pattern.
  * [[wiki:digital_forensics:logs_timelines:timeline_analysis|Timeline Analysis]] - Helps keep the finding grounded in a wider evidence pattern.
  * [[wiki:digital_forensics:logs_timelines:timeline_contradictions|Timeline Contradictions]] - Useful when checking whether another artifact supports the same interpretation.
  * [[wiki:digital_forensics:logs_timelines:account_logon_events|Account Logon Events]] - Helps keep the finding grounded in a wider evidence pattern.
  * [[wiki:digital_forensics:logs_timelines:authentication_logs|Authentication Logs]] - Useful when checking whether another artifact supports the same interpretation.
  * [[wiki:digital_forensics:logs_timelines:boot_time_artifacts|Boot Time Artifacts]] - Useful when checking whether another artifact supports the same interpretation.

===== Tools =====
  * [[https://github.com/log2timeline/plaso|Plaso]] - Timeline extraction and normalization across many artifact types.
  * [[https://github.com/google/timesketch|Timesketch]] - Collaborative timeline analysis and event tagging.
  * [[https://github.com/log2timeline/dfdatetime|dfDateTime]] - Timestamp conversion and interpretation support.
  * [[https://gchq.github.io/CyberChef/|CyberChef]] - Timestamp conversion, decoding, and quick data transformations.
  * [[https://jqlang.org/|jq]] - JSON parsing for logs, exports, and cloud evidence.
  * [[https://github.com/Yamato-Security/hayabusa|Hayabusa]] - Windows event log hunting and timeline support.
  * [[https://github.com/mikefarah/yq|yq]] - YAML, JSON, XML, and properties parsing during evidence review.
  * [[https://learn.microsoft.com/en-us/sysinternals/downloads/tcpview|TCPView]] - Windows network connection visibility.
  * [[https://github.com/Invoke-IR/PowerForensics|PowerForensics]] - PowerShell forensic artifact access and parsing.
  * [[https://github.com/davehull/Kansa|Kansa]] - PowerShell-based incident response collection framework.
  * [[wiki:tools:start|Forensic Tools]] - Full tool directory for the wiki.

===== Limitations of Tools =====
Tools parse, surface, and organize evidence. They do not create conclusions.
Parser output can be affected by version differences, unsupported formats, corrupted records, timezone handling, partial collection, and storage behavior outside the tool's view.
When a tool produces a strong-looking result, validate it against another tool or source where the stakes justify it. A parser can recover a fragment; it cannot tell you whether the fragment deserves a paragraph in the report.

===== References and Further Reading =====
  * [[https://plaso.readthedocs.io/|Plaso documentation]] - Timeline generation documentation.
  * [[https://learn.microsoft.com/en-us/windows/win32/eventlog/event-logging|Microsoft Windows Event Log]] - Event logging reference.
  * [[https://csrc.nist.gov/publications/detail/sp/800-92/final|NIST SP 800-92]] - Guide to computer security log management.
  * [[https://csrc.nist.gov/publications/detail/sp/800-86/final|NIST SP 800-86]] - Guide to integrating forensic techniques into incident response.
  * [[https://www.nist.gov/itl/ssd/software-quality-group/computer-forensics-tool-testing-program-cftt|NIST CFTT]] - Computer Forensics Tool Testing program.

===== See Also =====
  * [[wiki:digital_forensics:logs_timelines:start|Logs Timelines]]
  * [[wiki:digital_forensics:logs_timelines:super_timeline|Super Timeline]]
  * [[wiki:digital_forensics:logs_timelines:timeline_analysis|Timeline Analysis]]
  * [[wiki:digital_forensics:logs_timelines:timeline_contradictions|Timeline Contradictions]]
  * [[wiki:digital_forensics:logs_timelines:account_logon_events|Account Logon Events]]
  * [[wiki:digital_forensics:logs_timelines:authentication_logs|Authentication Logs]]
  * [[wiki:digital_forensics:logs_timelines:boot_time_artifacts|Boot Time Artifacts]]
  * [[wiki:digital_forensics:logs_timelines:clock_drift|Clock Drift]]
  * [[wiki:digital_forensics:logs_timelines:cloud_audit_timelines|Cloud Audit Timelines]]
  * [[wiki:digital_forensics:logs_timelines:collection_time_effects|Collection Time Effects]]
  * [[wiki:digital_forensics:logs_timelines:cross_host_correlation|Cross-Host Correlation]]
  * [[wiki:tools:start|Forensic Tools]]
  * [[wiki:resources:start|Project Resources]]

===== Reader Takeaway =====
Report Timeline Exhibits is useful when it helps explain what the evidence can support and where the limits begin. Treat report timeline exhibits as one part of a corroborated record, not a shortcut to intent. Duplicate timestamps standing in formation are still not proof of conspiracy.

===== Use Notes =====
This article is for defensive education and technical reference. It should not be treated as legal, forensic, investigative, compliance, or operational advice without qualified professional judgment.