Penetration › Module 2 › Lesson 4
Lab — Scope Sheet
Pack scope + box-type + out-of-scope note — literacy file only, dest $LAB_HOST.
Visual · pentest_scope_lab
Lab: write scope pack. $LAB_HOST only. Original Cyberlium.
Opening
Scope pack before packets — same discipline enterprise kickoffs use.
Lessons 2-1 through 2-3 defined box types, scoping elements, and out-of-scope stops. This lab ships the combined artifact: box type for YOUR lab, in-scope $LAB_HOST targets, allowed methods, and NEVER lines for stranger networks. No recon run required — paperwork first. Next: Quiz — Engagement Types and Scope.
1. Lab contract: write the scope pack
Create $HOME/cyberlium-lab/t19-m02-l04-scope-lab.txt with date, box type, $LAB_HOST targets, methods, window, and out-of-scope NEVER list.
Optional: one-line note on which box type your vulnerable VM simulates.
Command guide
Try these commands — Lab contract: write the scope pack
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Scope lab — document stop conditions before scanning Nmap — https://nmap.org/
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install nmap
macOS:
Command — copy this
brew install nmap
Windows:
Command — copy this
choco install nmap # or download https://nmap.org/download.html
═══ LINUX / macOS ═══
Command — copy this
grep -E 'in_scope|stop' "$HOME/cyberlium-lab/t19-scope.txt" source "$HOME/cyberlium-lab/t19-lab.env"; nmap --top-ports 20 "$LAB_HOST"
Primary tools to practice this lesson: grep, nmap. Reference sites: Scope lab; Nmap (https://nmap.org/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Cross-check scope creep habits
Grep notes for stranger IP examples — redact to $LAB_HOST. If a tutorial scopes a public range, rewrite to YOUR lab before copying workflow.
Classmates scope their own $LAB_HOST — not yours, not the dorm gateway.
3. Lock the proof
chmod 600 on the pack. Quiz next — then Recon Literacy.
Pentest teams archive scope with RoE; you are building that habit early.
4. What you ship: scope pack for $LAB_HOST
Box type + in-scope + out-of-scope + methods. $LAB_HOST named. chmod 600. No stranger targets.
5. What you record before the next lesson
Date. Scope pack path. Box type noted. File t19-m02-l04-scope-lab.txt chmod 600.
6. Wrong vs right: stranger nets vs YOUR lab VMs
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Add classmate IP as 'bonus target.' Skip file and start nmap on LAN.
Right
Write YOUR scope pack for $LAB_HOST. chmod 600. Next: Quiz — Engagement Types and Scope.
Mission: freeze YOUR scope pack on disk
1) Write box type, targets, methods, out-of-scope. 2) Name $LAB_HOST. 3) chmod 600. Never list stranger IPs as in-scope.
Stuck? Ask Cyberlium AI Mentor
Scope packs are boring — boring keeps strangers' networks untouched.
Knowledge Check
APPLY: This lab requires:
Multiple choice
Knowledge Check
APPLY: True or False: Scope pack should include out-of-scope NEVER lines.
True or False
Knowledge Check
APPLY: A tutorial scopes a stranger cloud range. You:
Multiple choice