Lab — RoE Draft
Pack RoE + objectives + lab infra note — literacy file only, dest $LAB_RT.
Visual · rt_roe_lab
Lab: write RoE pack. $LAB_RT only. Original Cyberlium.
If the host is not $LAB_RT in your written RoE, offensive tools do not get it.
Lessons 1–3 defined RT vs pentest, RoE/objectives, and lab-only infra. This lab ships the artifact later modules reuse: RoE summary, objectives, forbidden list, and lab infra note for $LAB_RT. No live exploit required — paperwork discipline red teams expect before any campaign. Next: Quiz — RT Mindset and RoE.
1. Lab contract: write the RoE pack first
Create $HOME/cyberlium-lab/t21-m01-l04-roe-lab.txt with date, operator, $LAB_RT scope, allowed methods, forbidden actions, two objectives, and lab infra snapshot note.
Optional: one-line proof you control $LAB_RT — still no offensive run required in this lab.
Command guide
Try these commands — Lab contract: write the RoE pack first
═══ LINUX / macOS (Terminal Practice) ═══
Check system state and user context
Command — copy this
id whoami uname -a
Inspect network sockets listening for connections
Command — copy this
ss -tuln 2>/dev/null || netstat -tuln
Audit active processes
Command — copy this
ps aux | grep -v "\[" | head -15
═══ WINDOWS (POWERSHELL) ═══ Query user identity and system information
Command — copy this
whoami /all Get-ComputerInfo | Select-Object CsName, OsName, OsVersion
Primary tools to practice this lesson: nmap, curl, grep. Reference sites: MITRE ATT&CK Enterprise (https://attack.mitre.org/matrices/enterprise/); RoE lab checklist (https://www.cisa.gov/resources-tools/resources/red-team-exercises); Atomic Red Team (https://redcanary.com/atomic-red-team/). 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 URL examples and redact them to $LAB_RT. If a tutorial screenshots production C2, rewrite mentally to lab placeholders before you copy habits.
Classmates run their own labs; do not 'share targets' by testing each other's VMs without written RoE.
3. Lock the proof
chmod 600 on the pack. Quiz is next — then ATT&CK Literacy.
Red teams archive RoE with campaign evidence; you are practicing that archive habit early.
4. What you ship: RoE pack for $LAB_RT
RoE pack names $LAB_RT scope, forbidden list, objectives, infra note. NEVER stranger targets. chmod 600.
5. What you record before the next lesson
Date. RoE pack path. $LAB_RT scope note. File t21-m01-l04-roe-lab.txt chmod 600.
6. Wrong vs right: stranger phishing vs authorized RT lab
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
- Wrong: Add a classmate VM 'as a second target.' Skip the file and emulate anyway.
- Right: Write YOUR RoE pack for $LAB_RT. chmod 600. Next: Quiz — RT Mindset and RoE.
Mission: freeze YOUR RoE pack on disk
1) Write RoE pack with scope, forbidden, objectives, infra note. 2) Name $LAB_RT. 3) chmod 600. Never list stranger URLs.
Stuck? Ask Cyberlium AI Mentor
RoE packs are boring on purpose — boring saves careers and keeps strangers safe.
APPLY: This lab requires:
APPLY: True or False: You should chmod 600 on red team notes.
APPLY: A tutorial runs C2 on a public range. You: