Lab — Scope Sheet
Pack scope summary + in/out + limits — literacy file only, dest $SCOPE_HOST.
Visual · bounty_scope_lab
Lab: write scope pack. $SCOPE_HOST only. Original Cyberlium.
Scope pack before probes — same discipline triage teams expect.
Lessons 3-1 through 3-3 defined scope reading, in/out classification, and rate limits. This lab ships the combined artifact: scope summary, in/out table, rate limits, forbidden actions — all for $SCOPE_HOST. No recon run required — paperwork first. Next: Quiz — Scope Literacy.
1. Lab contract: write the scope pack
Create $HOME/cyberlium-lab/t20-m03-l04-scope-lab.txt with scope date, in-scope list, out-of-scope list, in/out table, rate limits, and forbidden actions for $SCOPE_HOST.
Optional: wildcard rule note if your program uses *.domain patterns.
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)
t20-scope.env — SCOPE_HOST=lab.example.invalid or joined program root httpbin.org — safe demo when program not joined
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install curl
macOS: Built-in
Windows: Built-in (PowerShell: Invoke-WebRequest)
═══ LINUX / macOS ═══
Command — copy this
cat > "$HOME/cyberlium-lab/t20-scope.env" <<'EOF' SCOPE_HOST=httpbin.org IN_SCOPE=*.lab.example.invalid OUT_OF_SCOPE=third-party CDN, employee emails, DoS RATE_LIMIT_NOTE=respect program rate limits EOF
Command — copy this
chmod 600 "$HOME/cyberlium-lab/t20-scope.env" source "$HOME/cyberlium-lab/t20-scope.env"; curl -sS "https://$SCOPE_HOST/robots.txt" | head -10
Primary tools to practice this lesson: grep, curl. Reference sites: t20-scope.env; httpbin.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 random URL examples — redact to $SCOPE_HOST. If a tutorial scopes a public shop, rewrite to YOUR program before copying.
Classmates scope their own $SCOPE_HOST — not yours, not the dorm gateway.
3. Lock the proof
chmod 600 on the pack. Quiz next — then Recon for Bounty.
Clean scope packs make recon and reports defensible later.
4. What you ship: scope pack for $SCOPE_HOST
Summary + in/out + limits + forbidden. $SCOPE_HOST named. chmod 600. No random targets.
5. What you record before the next lesson
Date. Scope pack path. $SCOPE_HOST scope date. File t20-m03-l04-scope-lab.txt chmod 600.
6. Wrong vs right: random sites vs in-scope program
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
- Wrong: Add classmate URL as 'bonus in-scope.' Skip file and start subdomain brute force.
- Right: Write YOUR scope pack for $SCOPE_HOST. chmod 600. Next: Quiz — Scope Literacy.
Mission: freeze YOUR scope pack on disk
1) Merge summary, in/out, limits, forbidden. 2) Name $SCOPE_HOST. 3) chmod 600. Never list stranger URLs as in-scope.
Stuck? Ask Cyberlium AI Mentor
Scope packs are boring — boring keeps accounts and strangers safe.
APPLY: This lab requires:
APPLY: True or False: Scope pack should include rate limits.
APPLY: A tutorial scopes a random domain. You: