The Sleuth Kit
Which filesystem record supports the recovered name or content?
Choose a tool by the evidence it can inspect, then validate the result on a known input.
This directory separates acquisition, source parsing, event triage, and analysis workspaces. A tool’s reputation does not validate the specific feature used in a conclusion. Profiles record original sources, applicability, maintenance observations, and integrity concerns.
Which filesystem record supports the recovered name or content?
Did a displayed result come from a native record, an ingest module, or an analyst annotation?
What was actually present in this acquisition, and what did the plugin infer from it?
What source event does this normalized timestamp describe?
Which parts of this timeline are source facts and which are analyst-created context?
What did the collection query ask the endpoint to produce?
Does this rule match identify suspicious behavior, or merely a pattern worth checking?
Can the matched fields be traced back to the original record?
Is this a current-state observation or a retained event record?
Which metadata container produced this value, and how does it relate to the file?
What was captured at this observation point, rather than what happened everywhere on the network?
Does the examined database state include the transactions relevant to this collection?
| Task | Candidate tools | Question before relying on output |
|---|---|---|
| Filesystem examination | The Sleuth Kit, Autopsy | Can the result be relocated in the source image? |
| Memory structures | Volatility 3 | Are the target build, symbols, and captured pages suitable? |
| Event extraction and triage | Plaso, Hayabusa, Chainsaw | What do the original fields mean, and what was not collected? |
| Live endpoint state | Velociraptor, osquery | What changed while collection ran, and what query scope applied? |
| Metadata and application stores | ExifTool, SQLite shell | Which container and transaction state produced the displayed value? |
| Packets and combined timelines | Wireshark, Timesketch | What did collection omit, and what did analysis add? |
All profiles are documentation reviews, not binary safety assessments or benchmarks. The NIST CFTT program provides relevant test-method resources. Use the working templates to preserve inputs, settings, and limitations.