Policy Lab
Draft $LAB mini-policy + one patch verify + one change note — files chmod 600.
Visual · t16_policy_lab
Lab: policy pack on $LAB. Original Cyberlium.
Ship a policy page and a patch receipt — not an unauthorized change on shared infra.
Create $HOME/cyberlium-lab/t16-m08-policy-lab.txt: (1) five-line $LAB Logging & Patch mini-policy with review date, (2) output proving one pending update applied or scheduled on $LAB with verify command, (3) one change note for a config edit you performed (forwarder, firewall, or user account) with rollback line. chmod 600. No deploying policy to employer systems without scope.
1. Mini-policy
Scope: $LAB VMs. Requirements: patch within N days, forward logs, password length.
Owner: you. Review: quarterly lab date.
Command guide
Try these commands — Mini-policy
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Policy lab — https://www.cisecurity.org/controls CIS benchmarks — https://www.cisecurity.org/cis-benchmarks
═══ INSTALL ═══
Linux (Debian/Ubuntu): Built-in (iproute2)
macOS: Use: netstat
Windows: Use: netstat
═══ LINUX / macOS ═══
Command — copy this
ss -tulpn 2>/dev/null | wc -l; journalctl -n 15 --no-pager 2>/dev/null | head -10 sudo ufw status 2>/dev/null || sudo iptables -L -n 2>/dev/null | head -10 || ss -tuln | head -10
Primary tools to practice this lesson: sudo, journalctl, ss. Reference sites: Policy lab (https://www.cisecurity.org/controls); CIS benchmarks (https://www.cisecurity.org/cis-benchmarks). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Patch evidence
Screenshot or text: update applied / fully updated message.
Note reboot if required.
3. Change note
One sentence what/why/rollback for lab edit you made this module.
Teardown if change was temporary for exercise.
4. What you ship: policy lab pack
Mini-policy + patch verify + change note — chmod 600.
5. What you record before the next lesson
Policy lab file path.
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: Push GPO test policy to school domain without IT approval.
- Right: Policy lab on $LAB. Next: quiz.
Mission: policy lab
1) Write mini-policy for $LAB. 2) Verify one patch state. 3) Document one change with rollback.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “Policy review cadence for solo lab?”
APPLY: Policy lab includes:
APPLY: True or False: Unauthorized domain policy push is homework.
APPLY: Change note needs: