Documentation Hygiene¶

Good security research notes should survive handoff, retest, and later review.

Rules¶

• Record exact commands, requests, and timestamps.
• Keep raw evidence alongside the summary.
• Separate observation from interpretation.
• Normalize target names, paths, and versions early.
• Strip unrelated secrets before sharing notes.

Why this matters¶

Bad notes turn real findings into unverifiable claims. Good notes let another reviewer reproduce the path without guessing.