CS0-003 practice question 14 of 35

Which of the following explains the importance of a timeline when providing an incident response report?

Full set: 462 questions
Answer options
A: The timeline contains a real-time record of an incident and provides information that helps to simplify a postmortem analysis.
B: An incident timeline provides the necessary information to understand the actions taken to mitigate the threat or risk.
C: The timeline provides all the information, in the form of a timetable, of the whole incident response process including actions taken. Correct answer
D: An incident timeline presents the list of commands executed by an attacker when the system was compromised, in the form of a timetable.
Correct Answer:
C. The timeline provides all the information, in the form of a timetable, of the whole incident response process including actions taken.
Explanation

An incident timeline is a fundamental component of an incident response report that provides a comprehensive, chronological narrative of the entire event. It documents every phase of the incident response process, from the initial detection and reporting to the final resolution and recovery. This includes not only the actions taken by the response team (containment, eradication) but also the observed activities of the threat actor and relevant system events. This complete, time-sequenced record is crucial for understanding the incident's full scope, conducting effective post-incident analysis, identifying gaps in response, and fulfilling reporting requirements.

Why Incorrect

A. A timeline is a chronological reconstruction, not necessarily a "real-time record," and its purpose is broader than only simplifying postmortem analysis.
B. This is too narrow; a timeline includes the entire incident lifecycle (e.g., detection, analysis, attacker activity), not just mitigation actions.
D. This is incomplete. A timeline documents all relevant events, including the response team's actions, not just the attacker's commands.

References

1. National Institute of Standards and Technology (NIST). (2012). Computer Security Incident Handling Guide (Special Publication 800-61 Rev. 2).

Section 3.4.1

"Lessons Learned

" states that a key part of this meeting is to "review the timeline and accuracy of the actions taken at each stage of the incident response process." This confirms the timeline covers the whole process and all actions taken.

Section 2.3.3

"Incident Documentation

" outlines that documentation should include a summary

indicators

and "actions taken by all handlers

" reinforcing that the timeline is a comprehensive record of the entire response.

2. West-Brown

M.

Stikvoort

D.

& Kossakowski

K. P. (2003). Handbook for Computer Security Incident Response Teams (CSIRTs) (2nd ed.

CMU/SEI-2003-HB-002). Carnegie Mellon University

Software Engineering Institute.

Section 5.3

"Incident Reporting

" describes the final report

which should contain "a chronological description of the incident as it occurred

" including "what happened

when it happened

and how it was handled." This supports the idea of a complete timetable for the whole process.

3. Kent

K.

& Grance

T. (2006). Guide to Integrating Forensic Techniques into Incident Response (Special Publication 800-86). National Institute of Standards and Technology (NIST).

Section 3.2.2

"Creating a Drive Image

" notes the importance of documenting the time actions are taken. Section 4.2

"Conducting the Investigation

" emphasizes creating a "timeline of the events that occurred during the incident" as a core part of the analysis

which synthesizes data from multiple sources into a single chronological view.

Scroll to Top