A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
A repeatable reconnaissance script behaves more like a lab procedure than a one-liner. Define the target list, create an output directory, record the start time, run the same collection steps, and emit a compact summary. The goal is not maximum discovery; it is comparable discovery you can explain to another analyst.
| Question to ask | Why it matters |
|---|---|
| Build reconnaissance scripts with explicit inputs and repeatable outputs | Keeps the lesson tied to an observable security outcome. |
| Failure signal | Use exit status and raw evidence to separate “no finding” from “check failed”. |
Use a directory per run or a stable artifact naming scheme. Keep raw tool output alongside parsed summaries. That gives you two benefits: a reviewer can audit what the scanner actually returned, and your parser can be improved later without repeating network activity.
Creates a unique run directory derived from the execution time. The useful habit here is to treat the command output as evidence about one system fact, not as a magical diagnosis.
One subtle source of drift is ambient state. DNS answers, route tables, and package versions change. Record enough metadata to understand the environment in which the script ran, but avoid dumping secrets or unrelated personal information into the output archive.
Captures the route decision as raw evidence. Read the result in context: the same command can be correct yet insufficient if a permission boundary, alternate configuration, or different backend changes what it reports.
Captures local listening sockets without changing system state. In a production workflow, save the raw result when the observation contributes to a finding. That keeps later analysis honest and makes troubleshooting reproducible.
A practitioner’s checkpoint: compare the observed behavior with the assumption your script is about to make. If the assumption is broader than the evidence, narrow the rule. If the evidence is incomplete, report the uncertainty instead of converting it into a confident finding.
Lab discipline: stay inside the declared course environment, prefer read-only checks for learning exercises, and preserve the original output of security tools before transforming it.
Finish the lesson once you have worked through the material. This awards ★ 35 XP.