Defensive › Module 1 › Lesson 4
RoE Lab
Pack defensive RoE + lab host note — literacy file only, dest $LAB_HOST.
Visual · defense_roe_lab
Lab: write defensive RoE pack. $LAB_HOST only. Original Cyberlium.
Opening
If the hostname is not $LAB_HOST in the pack, hardening commands do not get it.
Lessons 1–3 defined defense, wrote RoE, and locked the lab host. This lab ships the artifact later modules reuse: a defensive RoE file naming $LAB_HOST, allowed actions (read config, apply baseline, enable logging per brief), and NEVER lines for stranger hosts, LAN sweeps, and café routers. No production hardening run required — this is paperwork discipline defenders expect before any change window. Next: Quiz — Defense Mindset and RoE.
1. Lab contract: write the pack first
Create $HOME/cyberlium-lab/t16-m01-l04-roe-lab.txt with date, operator, $LAB_HOST, allowed actions, and NEVER list.
Optional: one-line proof you can log into $LAB_HOST — still no hardening changes 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)
CIS Controls — https://www.cisecurity.org/controls MITRE D3FEND — https://d3fend.mitre.org/ (defensive countermeasures map)
═══ INSTALL ═══
Linux (Debian/Ubuntu):
Command — copy this
sudo apt install curl
Built-in (iproute2)
macOS: Use: netstat
Windows: Built-in (PowerShell: Invoke-WebRequest) Use: netstat
═══ LINUX / macOS ═══
Command — copy this
grep -i never "$HOME/cyberlium-lab/t16-defense/roe.txt" 2>/dev/null || echo 'Write roe.txt first'
ss -tulpn 2>/dev/null | head -10
curl -sS http://127.0.0.1/ -o /dev/null -w "loopback HTTP %{http_code}
" 2>/dev/null || curl -sS http://127.0.0.1:8080/ -o /dev/null -w "alt port %{http_code}
"Primary tools to practice this lesson: grep, curl, ss. Reference sites: CIS Controls (https://www.cisecurity.org/controls); MITRE D3FEND (https://d3fend.mitre.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 console you do not own, rewrite mentally to $LAB_HOST before you copy habits.
Classmates run their own lab VMs; do not 'share targets' by hardening each other's home PCs.
3. Lock the proof
chmod 600 on the pack. Quiz is next — then Windows Hardening Literacy.
Defenders archive RoE with change evidence; you are practicing that archive habit early.
4. What you ship: defensive RoE pack for $LAB_HOST
RoE pack names $LAB_HOST. NEVER lines present. chmod 600. No stranger hosts.
5. What you record before the next lesson
Date. RoE pack path. $LAB_HOST login note. File t16-m01-l04-roe-lab.txt chmod 600.
6. Wrong vs right: stranger hosts vs YOUR lab hosts
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 run hardening scripts anyway.
Right
Write YOUR pack for $LAB_HOST. chmod 600. Next: Quiz — Defense Mindset and RoE.
Mission: freeze YOUR defensive RoE on disk
1) Write RoE pack with who/what/where/stop. 2) Name $LAB_HOST. 3) Optional login note to $LAB_HOST only. 4) chmod 600. Never list stranger hosts.
Stuck? Ask Cyberlium AI Mentor
RoE is boring on purpose — boring saves careers and keeps strangers' systems 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 hardens a stranger's VPS. You:
Multiple choice