Skip to content
Tutorials Center
My learning

Topics

Lesson 9 of 38 ยท Scoping, Rules and Methodology

Note-Taking and Evidence Handling

Learn how professional penetration testers keep timestamped logs, capture reproducible evidence, hash files, redact secrets and organize notes for reports.

Penetration testers forget things. Over a two-week test you might send thousands of requests, try dozens of ideas and find a handful of real problems. Without good notes, you cannot reproduce a finding, you cannot prove you stayed within scope, and writing the report becomes archaeology. Note-taking is not paperwork you do after the real work; it is part of the work. This lesson covers what to record, how to store evidence safely, and how to build habits that make the final report almost write itself.

What to record

Think of two kinds of notes.

The activity log answers: what did I do, when, against what, and what happened? Each entry has a timestamp, the target, the action (including the exact command), and the outcome. This log protects you: if a service fails at 14:07 and you scanned it at 14:05, you can say so and respond properly. It also proves that every action stayed inside the rules of engagement.

The findings notes answer: what did I discover and how can someone else see it too? Each finding gets its own page with a title, affected assets, steps to reproduce, evidence, impact and a first idea for the fix.

A good log entry

Timestamp In UTC, to the second.
Target Exact host, port or URL.
Action The command or request.
Result What happened, briefly.

Write it as you go, not at the end of the day.

1 / 2

Choosing tools

Any tool works if you use it consistently. Popular choices:

  • Plain text or Markdown files in a folder per client, with one file per day.
  • Note applications with templates and search (check where they store data; avoid cloud sync of client material unless the contract allows it).
  • Terminal session recorders, such as script on Linux, which save everything typed and printed.
  • Tool outputs saved with flags: most scanners can write a file so you do not rely on scrolling back.

Read-only example of saving a terminal session and scan output (the output below is an example, not a real run):

Terminal
script -a -f ~/client-acme/2026-05-12-session.log
nmap -sV -oA ~/client-acme/scans/web01-tcp 192.0.2.10
TEXT
Script started, output log file is '/home/tester/client-acme/2026-05-12-session.log'.
Starting Nmap 7.x ( https://nmap.org ) at 2026-05-12 09:14 UTC
Nmap done: 1 IP address (1 host up) scanned in 11.82 seconds

The -oA option writes three formats at once (normal, grepable, XML), which makes later parsing easy.

Capturing evidence

Evidence should let a reader reproduce your result and should show impact with minimal harm.

  • Screenshots with the URL bar and a visible clock if possible, cropped to what matters.
  • Request and response pairs, copied exactly, with secrets redacted in the copy you share.
  • Command output in text, not only images, so it can be searched.
  • Hashes of files you collect (SHA-256), so you can show they were not altered afterwards.
  • Minimal data samples: one redacted row instead of a table dump.

Name files consistently: 2026-05-12_web01_login-sqli_request.txt. Predictable names make report writing fast.

Protecting what you collect

Your notes may contain credentials, personal data and vulnerabilities that are dangerous if leaked. Treat them as such:

  • Store them on an encrypted disk or container.
  • Keep each client's material separate.
  • Do not paste real secrets into public tools (online formatters, translators, paste sites, chatbots).
  • Follow the retention rule in the RoE: delete when the period ends.
  • Redact before sharing: show ab****gh instead of a full password, and mask card numbers and personal identifiers.

Chain of custody in short

For ordinary tests you do not need formal forensic custody, but the idea helps: record who collected an item, when, where it is stored and its hash. If a dispute or legal action follows, that record shows the evidence was not tampered with.

Stand-in: a structured log and hash helper

The first example builds a tiny activity log in memory, with UTC timestamps, and prints it in a clean format. Notice that every entry names the target and the exact action.

Python Build an activity log

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The second example hashes evidence and redacts a secret. hashlib is part of Python's standard library, so it runs in the browser; the evidence text is invented.

Python Hash and redact evidence

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Keep the hash of the original, store the original securely, and put only the redacted version in the report. The different hashes show the two files are different on purpose.

Daily habits

  1. Start each day with a new log file and the date.
  2. Write the command before you run it, then paste the result.
  3. Take a screenshot whenever something surprising appears, even if it seems minor.
  4. At the end of the day, review the log and promote anything real into a finding page.
  5. Back up notes to an approved, encrypted location.

Later lessons assume you have these notes: the reporting chapter of this course draws on them directly, and the practice work in the projects chapter asks you to produce a log of your own. Your first real use for them starts in Reconnaissance.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why record every action with a timestamp and target?

    A precise log protects you if something breaks and supports the report.
  2. 2. What is the purpose of hashing a collected file?

    A SHA-256 hash is a fingerprint. If the file changes, the hash changes.
  3. 3. Which is the best way to show that you could read customer data?

    Prove access with minimal data and redact personal information.
  4. 4. Where should you store client evidence?

    Evidence contains secrets and vulnerabilities. Encrypt it, separate it and follow the retention rules.

Summary

  • Keep an activity log (what, when, where, result) and findings notes (reproducible detail).
  • Save tool output to files, record terminal sessions, and use consistent file names.
  • Collect evidence with minimal data, hash important files and redact secrets before sharing.
  • Store everything encrypted and per client, and delete it when the retention period ends.
  • Good habits during the test make the report fast and accurate.

Next: Reconnaissance: Passive and Active