RoE Lab
Pack MSF RoE + lab topology note — literacy file only, dest $LAB.
Visual · msf_roe_lab
Lab: write MSF RoE pack. $LAB host-only. Original Cyberlium.
If the host is not $LAB in the pack, msfconsole does not get it.
Lessons 1–3 defined MSF, wrote RoE, and locked the lab network. This lab ships the artifact later modules reuse: an MSF RoE file naming $LAB, host-only networking, module literacy boundaries (search/info before run), and NEVER lines for strangers, ransomware, and phishing. No exploit run required — this is paperwork discipline defenders expect before any tool launch. Next: Quiz — MSF Mindset and RoE.
1. Lab contract: write the pack first
Create $HOME/cyberlium-lab/t14-m01-l04-roe-lab.txt with date, operator, $LAB, network mode, allowed actions (search/info/configure on lab), and NEVER list.
Optional: one-line proof you can reach $LAB (ping or TCP) — still no module runs 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)
MITRE ATT&CK matrix — https://attack.mitre.org/matrices/enterprise/ MSF overview — https://docs.rapid7.com/metasploit/msf-overview/
═══ INSTALL ═══
Linux (Debian/Ubuntu): Kali: preinstalled, or: sudo apt install metasploit-framework
macOS: Prefer Kali/Linux VM — brew install metasploit (heavy)
Windows: Use Kali VM or WSL with metasploit-framework — not raw Windows host
═══ LINUX / macOS ═══
Command — copy this
grep LAB_HOST "$HOME/cyberlium-lab/t14-msf/roe.txt" 2>/dev/null || echo 'Write roe.txt with YOUR lab IP' msfconsole -q -x 'version; help search; exit' 2>/dev/null || echo 'msfconsole required in lab VM'
Primary tools to practice this lesson: msfconsole, grep. Reference sites: MITRE ATT&CK matrix (https://attack.mitre.org/matrices/enterprise/); MSF overview (https://docs.rapid7.com/metasploit/msf-overview/). 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 public IP examples and redact them to $LAB. If a tutorial screenshot shows RHOSTS=8.8.8.8, rewrite mentally to $LAB before you copy habits.
Classmates run their own lab; do not 'share targets' by bridging VMs.
3. Lock the proof
chmod 600 on the pack. Quiz is next — then Install and msfconsole.
Defenders archive RoE with test evidence; you are practicing that archive habit early.
4. What you ship: MSF RoE pack for $LAB
RoE pack names $LAB and host-only net. NEVER lines present. chmod 600. No stranger RHOSTS.
5. What you record before the next lesson
Date. RoE pack path. $LAB reachability note. File t14-m01-l04-roe-lab.txt chmod 600.
6. Wrong vs right: stranger hosts vs YOUR lab VM
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
- Wrong: Add a friend's IP 'as a second target.' Skip the file and open msfconsole anyway.
- Right: Write YOUR pack for $LAB. chmod 600. Next: Quiz — MSF Mindset and RoE.
Mission: freeze YOUR MSF RoE on disk
1) Write RoE pack with who/what/where/stop. 2) Name $LAB and host-only networking. 3) Optional reachability note to $LAB only. 4) chmod 600. Never list stranger hosts.
Stuck? Ask Cyberlium AI Mentor
RoE is boring on purpose — boring saves careers.
APPLY: This lab requires:
APPLY: True or False: You should chmod 600 on RoE notes.
APPLY: A tutorial uses RHOSTS 203.0.113.50. You: