Cloud concept · Updated

Timeline Reconstruction - Timeline reconstruction is the process of correlating evidence into a time-ordered account of an incident to establish what happened, which entities were involved, and how events relate.

In short

A reconstructed timeline connects security alerts, identity activity, configuration changes, network traffic, and workload events into an evidence-backed incident narrative. It supports root cause analysis by distinguishing the initial compromise and enabling conditions from later attacker actions, symptoms, and response activity.

Cloud Concepts Hub →

6 key aspects of Timeline Reconstruction

Reliable timeline reconstruction combines normalized time, cross-source correlation, iterative investigation, and preserved evidence while making uncertainty and coverage gaps explicit.

01
Time normalization and uncertainty

Convert timestamps to a common time basis while preserving original values and distinguishing event time from ingestion time. Account for clock skew, aggregation intervals, and delayed delivery before asserting an exact sequence.

02
Cross-source evidence correlation

Connect audit events, network records, configuration history, and workload logs using identities and resource identifiers. Validate connections with multiple attributes rather than relying only on matching timestamps or IP addresses.

03
Backward and forward investigation

Trace backward from a known event to find earlier compromise indicators and enabling conditions, then forward to establish impact and persistence. Expand the time window and account scope as new relationships emerge.

04
Causality and hypothesis testing

Distinguish observed chronology from explanations of why events occurred. Test competing explanations and document confidence rather than treating temporal proximity as proof of causation.

05
Evidence integrity and provenance

Retain references to original records, document evidence handling, and protect collected artifacts from unauthorized modification. Keep investigator actions identifiable so the timeline remains reproducible and defensible.

06
Coverage and gap awareness

Record which accounts, Regions, event types, and retention periods the available evidence covers. Explain how disabled logging, expired records, or unsupported telemetry limit the conclusions.

Cloud services for Timeline Reconstruction

GuardDuty findings can identify a suspicious entity and investigation window, while Detective helps explore related activity and relationships. CloudTrail supplies API evidence, AWS Config adds recorded resource-state history, and CloudWatch Logs contributes workload context. Athena can correlate retained datasets in Amazon S3 when the investigation requires broader searches or custom joins. These services provide complementary views, not an automatically complete incident narrative. Investigators must reconcile timestamps, verify logging coverage and retention, preserve original records, and distinguish evidence-supported conclusions from hypotheses about the initial compromise.

Amazon DetectiveAmazon Detective

Amazon Detective organizes supported security telemetry into a behavior graph and provides time-scoped views of related entities and activity. Investigators can use these relationships to explore events preceding a finding, identify associated resources, and test root cause hypotheses.

AWS CloudTrailAWS CloudTrail

AWS CloudTrail records supported account and API activity, providing identity, action, resource, and timing evidence for an incident timeline. Management-event history alone does not cover every investigative need; applicable data events and longer-term retention must be configured where required.

Amazon GuardDutyAmazon GuardDuty

Amazon GuardDuty findings provide investigation starting points, including affected entities and observed activity times. A finding is a detection result rather than a complete chronology, so investigators correlate it with underlying audit and workload evidence.

AWS ConfigAWS Config

AWS Config provides configuration history for supported resources within the configured recording scope. Investigators use this history to establish relevant state changes and correlate them with API activity, rather than treating configuration history as a complete record of actor behavior.

Amazon AthenaAmazon Athena

Amazon Athena can query retained logs in Amazon S3 to correlate events across sources, accounts, and time windows using SQL. Consistent schemas, timestamp handling, and partitioning improve both investigation accuracy and query efficiency.

Timeline Reconstruction exam questions

Real practice exam questions on Timeline Reconstruction, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SCS-C03

A company contains an incident in which an unauthorized Kubernetes RoleBinding was created in an Amazon EKS cluster, followed by the deployment of a privileged Pod. The incident occurred yesterday. EKS control plane audit logs covering the incident are retained in Amazon S3, but no investigation behavior graph existed during the incident.

The security team must immediately establish which Kubernetes identities performed these actions and their sequence. The team also wants a managed behavior graph for investigating relationships between Kubernetes identities, Pods, and API activity in future incidents, without building a custom ingestion pipeline.

Which approach meets these requirements?

Show answerCORRECT ANSWER

Enable Amazon Detective and its EKS audit logs optional data source for future investigations. Analyze the retained EKS audit logs separately to establish the identities, timestamps, and outcomes of the RoleBinding and Pod creation requests.

Amazon Detective can analyze Kubernetes activity through its optional EKS audit logs data source, but enabling it does not backfill yesterday's activity from an existing S3 archive. The retained EKS audit logs provide the evidence needed for the current incident, while enabling Detective with the optional source supports future graph-based investigations.

DOP-C02

A company queries archived AWS CloudTrail events, EC2 operating system logs, and VPC Flow Logs in Amazon S3 by using Amazon Athena. During an incident investigation, an engineer finds the following evidence for one EC2 instance:

• A CloudTrail event records an unauthorized security group ingress change at 10:01:30 UTC.
• An operating system audit record shows execution of a malicious program at a host timestamp of 10:03:00.
• Independent clock-monitoring records establish that the instance clock was 120 seconds ahead of UTC throughout the incident, with an uncertainty of ±10 seconds.
• An ACCEPT flow record for the instance covers 10:00:40–10:02:20 UTC. The record contains aggregate connection metadata, not individual packet timestamps.

All relevant original records are retained. A draft incident report states that the security group change enabled the malicious execution because the execution occurred afterward.

Which investigation approach produces an evidence-supported timeline?

Show answerCORRECT ANSWER

Use Athena to subtract 120 seconds from the host timestamp and retain its uncertainty range. Place the execution at approximately 10:00:50–10:01:10 UTC, preserve the flow record as an interval, and revise the report because the observed execution preceded the security group change. Search earlier evidence to investigate how access was obtained.

A clock that is ahead requires subtracting the measured offset. The resulting execution interval ends before the security group change, so that change cannot have enabled this already-observed execution. The aggregate flow record does not establish an exact connection or execution time. Searching backward can identify earlier enabling conditions without claiming that the earliest observed event proves the initial compromise time.

Practice Timeline Reconstruction in a full exam

Questions on Timeline Reconstruction in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Timeline Reconstruction

3 min read

Timeline reconstruction turns scattered observations into an evidence-backed account of a security incident. Investigators identify relevant events, normalize their timestamps, connect identities and resources, and explain the sequence from the earliest supported activity through containment and recovery. The objective is not simply to sort logs: it is to determine what the evidence establishes, what remains uncertain, and which conditions allowed the incident to occur.

In cloud environments, evidence usually spans multiple accounts, Regions, services, and operating systems. Control-plane audit logs show API activity, workload logs show application and operating-system behavior, network flow records describe communications, and configuration histories show resource state changes. A useful timeline preserves each event's source, original timestamp, normalized time, principal, resource identifier, action, result, and reference to the original evidence. Investigators should also record their own containment actions so that response activity is not mistaken for attacker behavior.

Begin with a known event, such as an unexpected access-policy change or a suspicious credential-use finding. Search backward to identify preceding authentication, role assumption, resource discovery, and permission changes, then search forward to determine impact and persistence. Expand the investigation window when earlier evidence suggests that the initial alert occurred well after compromise. Correlate stable identifiers such as access key IDs, role session identifiers, resource IDs, and request IDs where available; a shared source IP address alone does not establish that two actions came from the same actor.

For example, an investigator might connect an AWS Security Token Service AssumeRole event to subsequent API calls made with the resulting temporary credentials, followed by a bucket policy change and object reads. AWS CloudTrail can provide the relevant API evidence, but object-level reads require applicable data-event logging to have been enabled. AWS Config can help establish how the recorded bucket configuration changed, while workload and network evidence may clarify how the credentials were exposed. If evidence begins with use of a stolen credential, that proves credential use, not necessarily how the theft occurred.

Time handling requires particular care. Normalize timestamps to UTC while retaining original values, distinguish event time from ingestion time, and account for clock skew on workloads. Logs can arrive late, contain duplicates, or represent activity over an interval rather than a precise instant. Network flow records, for example, aggregate traffic and do not reveal packet contents. Treat events with overlapping uncertainty windows as potentially concurrent rather than forcing an unsupported exact order.

Amazon Detective supports this process by presenting relationships and activity across entities such as principals, IP addresses, and resources. These views help investigators explore hypotheses and scope an incident, but they do not independently prove causation or replace underlying evidence. A configuration change immediately before an alert might explain the alert, or both might result from an earlier compromise.

Completeness depends on preparation. Enable appropriate logging, centralize evidence across account and Region boundaries, establish retention, and protect access to original records. Preserve provenance and use integrity controls where available; CloudTrail log file integrity validation can help detect changes to delivered log files when configured. More detailed collection improves investigative coverage but increases storage costs, query costs, and sensitive-data handling requirements. Missing events are not proof that an action never occurred. A defensible root cause analysis explicitly separates confirmed observations, supported inferences, evidence gaps, and corrective actions addressing the underlying control failure.

Learn Timeline Reconstruction in lessons

4 short lessons on Timeline Reconstruction in 2 certification courses.

Open the lessons