Penetration › Module 1 › Lesson 4
Lab — RoE Draft
Pack pentest RoE + lab VM note — literacy file only, dest $LAB_HOST.
Visual · pentest_roe_lab
Lab: write pentest RoE pack. $LAB_HOST only. Original Cyberlium.
Opening
If the host is not $LAB_HOST in the pack, offensive tools do not get it.
Lessons 1–3 defined pentest, wrote RoE, and locked the lab VM. This lab ships the artifact later modules reuse: a pentest RoE file naming $LAB_HOST, allowed actions (recon, enumeration, lab-only exploit validation per brief on lab only), and NEVER lines for stranger LANs, café Wi-Fi, internet ranges, and weaponized PoCs on strangers. No production exploit required — this is paperwork discipline pentesters expect before any engagement runs. Next: Quiz — Pentest Mindset and RoE.
1. Lab contract: write the pack first
Create $HOME/cyberlium-lab/t19-m01-l04-roe-lab.txt with date, operator, $LAB_HOST, allowed actions, and NEVER list.
Optional: one-line proof you can ping or SSH to $LAB_HOST — still no offensive run required in this lab.
Command guide
Try these commands — Lab contract: write the pack first
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Scope document — in_scope / out_of_scope for YOUR lab Nmap — https://nmap.org/ (authorized targets only)
═══ 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
cat > "$HOME/cyberlium-lab/t19-scope.txt" <<'EOF' in_scope: intentional lab VMs listed here out_of_scope: ISP gear, neighbors, cloud not named stop_conditions: DoS, phishing, ransomware EOF
Command — copy this
source "$HOME/cyberlium-lab/t19-lab.env"; nmap -sn "$LAB_HOST"
Primary tools to practice this lesson: nmap, grep. Reference sites: Scope document; 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 against misuse patterns
Grep your notes for stranger IP examples and redact them to $LAB_HOST. If a tutorial screenshot shows a public cloud range, rewrite mentally to $LAB_HOST before you copy habits.
Classmates run their own lab VMs; do not 'share targets' by exploiting each other's home PCs.
3. Lock the proof
chmod 600 on the pack. Quiz is next — then Engagement Types and Scope.
Pentest teams archive RoE with engagement evidence; you are practicing that archive habit early.
4. What you ship: pentest RoE pack for $LAB_HOST
RoE pack names $LAB_HOST. NEVER lines present. chmod 600. No stranger exploitation.
5. What you record before the next lesson
Date. RoE pack path. $LAB_HOST reachability note. File t19-m01-l04-roe-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 a classmate's IP 'as a second target.' Skip the file and nmap anyway.
Right
Write YOUR pack for $LAB_HOST. chmod 600. Next: Quiz — Pentest Mindset and RoE.
Mission: freeze YOUR pentest RoE on disk
1) Write RoE pack with who/what/where/stop. 2) Name $LAB_HOST. 3) Optional reachability note to $LAB_HOST only. 4) chmod 600. Never list stranger IPs.
Stuck? Ask Cyberlium AI Mentor
RoE is boring on purpose — boring saves careers and keeps strangers' networks alone.
Knowledge Check
APPLY: This lab requires:
Multiple choice
Knowledge Check
APPLY: True or False: You should chmod 600 on RoE notes.
True or False
Knowledge Check
APPLY: A tutorial exploits a stranger cloud range. You:
Multiple choice