Resource guide

Evidence integrity checklist

Establish what you collected

Record the authorized scope, collector, machine, time source assumptions, tool version, command, and original filenames. Separate direct observation from interpretation. A JSON report is useful documentation, but it does not retroactively create an evidence-acquisition process.

Preserve exact bytes

Hash the original before editing or reformatting. Reading JSON through a formatter and saving it again changes whitespace and potentially encoding. Use copies for analysis. The scanner writes UTF-8 bytes with a trailing newline so its saved bytes and digest input match.

Verify independently

Use Get-FileHash on Windows or sha256sum on Linux and compare the result with the recorded baseline. Case differences in hexadecimal letters do not change the represented digest. A raw-digest sidecar must be compared manually; it is not a filename-bearing sha256sum manifest.

Preserve a baseline outside the same writable folder

An attacker who changes the report can also change its nearby checksum. Store and protect an independent baseline according to your organization's procedures. Document transfers and custody where the professional context requires them.

Treat failures as findings about the procedure

A failed sidecar write can leave a JSON file behind. Preserve the error and inspect the artifact; do not call the collection complete. Repeat into fresh output paths and document what happened.

Apply this in the complete free Project 001 lesson →

Search PythonProjects.org