During a response, a log excerpt can help explain what happened. Preserve the original source or the approved export, together with the details a second reviewer needs to understand it.
Incident Response · Lesson 2
Evidence Preservation
Learn to keep a practice record, copy, and checksum usable for later review.
Recording Context
Write down the host, source, time zone, and time window. Note who collected the records and what filter they used. A copied line without this context may have the same text as a line from a different machine.
A colleague receives a line with time 09:22 and no other context. What should you add?
Comparing a Copy
In a new practice folder, save a harmless sample line, copy it, and calculate SHA-256 values for both files. Use only the example file. The writes replace files of the same names in this folder.
$ printf '%s\n' '09:22 UTC public homepage returned 503' > sample.log
$ cp sample.log review-copy.log
$ sha256sum sample.log review-copy.log
The first column gives a content hash. The two values should match. This verifies the bytes of this copy against the original when checked. It cannot tell you whether the original event was logged accurately.
What does the matching hash support?

Preparing a Safe Review Copy
Keep the original record intact and restrict access. If another team needs only a few fields, prepare a separate excerpt and remove sensitive information from that excerpt. Document that it was reduced, and keep the link to its protected source.
Which file should you redact for sharing?
Lesson complete
You finished Evidence Preservation
You can now prepare evidence that another reviewer can interpret.
Record where and when the material was collected.
Check that a copy matches its source bytes.
Redact a separate excerpt when sharing.
Keep your learning progress
Create a free account to save this lesson and continue learning on any device.
Create a free account