Practical cybersecurity guides, labs & compliance
Preserve Nmap XML and its scan conditions alongside each Obsidian host note. Use the comparison record to distinguish genuine retest differences from changed port scope, target identity, import behavior or missing coverage.
Build an initial-access practice record with the objective, observed access, reproducible steps and submission state. Use the handoff to review evidence against current official requirements without treating checklist completion as awarded points.
Compare TUN, SOCKS and transparent forwarding through one required application flow. Record transport, resolution and each hop, then test a permitted representative connection without assuming one working browser covers every protocol.
Build an Obsidian service card with the command, observed result, hypothesis and evidence link kept distinct. Use the retrieval review to check attachment links after moving or exporting notes and retain provenance and handling context.
Use an enumeration timebox to review evidence and choose whether to continue, park or revisit a lead. Preserve the next discriminating question and stop condition, and keep study timing separate from actual exam rules.
Review a Kioptrix practice screenshot through target identity, source evidence and report context. Use the practice-proof record to check what the image establishes and compare exam submissions with the current official proof requirements.
Plan Kali logging from the event you need to retrieve, the effective collection setup and a bounded retention budget. Use a benign event and retrieval record to check coverage while preserving exclusions and sensitive-data limits.
Review the actual exported lab report, not just a successful build. Use the acceptance record to check image paths, PDF engine context, captions, page breaks and redactions, then identify the final artifact reviewed.
Build a Kali tool workflow that preserves commands, original output and coverage beyond the terminal session. Use the handoff record to distinguish session persistence, authentication, permissions and independently retained evidence.
Describe shell access, executed actions, process identity and privilege boundaries with separate evidence. Use the claim record to distinguish an interaction channel from confirmed execution or control of a wider system.