Bug › Module 10 › Lesson 1
Checklist
One-page Topic 20 capstone checklist — scope, classes, validation, report, triage on enrolled $PROGRAM or $LAB_BOUNTY.
Visual · t20_capstone_checklist
Checklist consolidates bounty pillars. Original Cyberlium.
Opening
Capstone proves disciplined hunting on assets you joined — not a montage of unauthorized scans.
Assemble checklist covering Modules 1–9: bounty mindset and $PROGRAM enrollment, scope literacy, recon and asset map, bug class literacy (XSS, IDOR, SSRF/redirect/logic), validation hygiene (minimal proof, no harm, dup/noise), report writing, triage communication literacy. Use on capstone walk of YOUR enrolled program work or $LAB_BOUNTY path only — never mass scan stranger assets, never weaponized cookbooks export, never DoS/phishing. Notes chmod 600 under $HOME/cyberlium-lab. Each row links artifact or honest N/A with reason.
1. Scope and enrollment
$PROGRAM enrolled or $LAB_BOUNTY named. NEVER OOS mass scan, stranger sites, unenrolled production.
Rate limits and program rules acknowledged in checklist header.
Command guide
Try these commands — Scope and enrollment
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Capstone checklist — rules + scope + recon + report Scope env — $SCOPE_HOST
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
go install -v github.com/projectdiscovery/subfinder/v2/cmd/subfinder@latest
macOS:
Command — copy this
brew install subfinder
Windows:
Command — copy this
go install -v github.com/projectdiscovery/subfinder/v2/cmd/subfinder@latest
═══ LINUX / macOS ═══
Command — copy this
ls -la "$HOME/cyberlium-lab"/t20-*.txt "$HOME/cyberlium-lab"/t20-*.env 2>/dev/null source "$HOME/cyberlium-lab/t20-scope.env"; subfinder -d "$(cat "$HOME/cyberlium-lab/t20-root-domain.txt" 2>/dev/null || echo httpbin.org)" -silent 2>/dev/null | head -5 || true
Primary tools to practice this lesson: grep, subfinder. Reference sites: Capstone checklist; Scope env. Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Bounty pillars
Asset map, class cards, validation pack, report draft, triage lab threads — each row linked.
Minimal proof and no-data-harm lines signed on checklist.
3. Integrity lines
No exploit cookbooks for strangers, no real PII exfil, no harassment in triage comms.
Teardown: secure notes, revoke test tokens, delete disposable accounts if program allows.
4. What you ship: Topic 20 capstone checklist
One-page bounty checklist for $PROGRAM or $LAB_BOUNTY path.
5. What you record before the next lesson
Checklist file path.
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
Use checklist to justify scanning entire internet for nuclei hits.
Right
Checklist written. Next: Lab Path.
Mission: write bounty capstone checklist
1) Scope/enrollment section. 2) Classes through triage pillars. 3) Integrity and teardown section.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “Top five capstone artifacts?”
Knowledge Check
APPLY: Checklist includes:
Multiple choice
Knowledge Check
APPLY: True or False: Checklist authorizes unenrolled OOS hunting.
True or False
Knowledge Check
APPLY: Teardown includes:
Multiple choice