Metasploit › Module 2 › Lesson 3
Workspaces
Separate lab projects with workspace — keep Module 1 RoE notes distinct from later labs.
Visual · msf_workspaces
workspace add/list. Original Cyberlium.
Opening
One console, many labs — workspaces stop Tuesday's notes from becoming Wednesday's disaster.
`workspace -a topic14_m1` creates a DB partition for hosts, services, and creds you will log later on $LAB. `workspace` lists; `workspace topic14_m1` switches. Workspaces do not replace RoE — they organize authorized lab work. Next: Console Lab.
1. Why partition
Mixing capstone lab hosts with Module 2 drills causes wrong RHOSTS mistakes. Named workspaces mirror how teams split engagements.
Default workspace exists; still name cyberlium labs explicitly.
Command guide
Try these commands — Why partition
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Workspaces — https://docs.rapid7.com/metasploit/msf-overview/ Database — https://docs.rapid7.com/metasploit/manage-the-database/
═══ INSTALL ═══
Linux (Debian/Ubuntu): Kali: preinstalled, or: sudo apt install metasploit-framework Kali: sudo msfdb init
macOS: Prefer Kali/Linux VM — brew install metasploit (heavy) Inside Kali/Linux lab VM
Windows: Use Kali VM or WSL with metasploit-framework — not raw Windows host Inside Kali/WSL lab VM
═══ LINUX / macOS ═══
Command — copy this
msfdb status 2>/dev/null || echo 'msfdb init in YOUR lab VM if needed' msfconsole -q -x 'workspace -a cyberlium_lab; workspace; exit' 2>/dev/null || echo 'Workspace literacy only'
Primary tools to practice this lesson: msfconsole, msfdb. Reference sites: Workspaces (https://docs.rapid7.com/metasploit/msf-overview/); Database (https://docs.rapid7.com/metasploit/manage-the-database/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Commands
`workspace -a name`, `workspace name`, `workspace -d name` (delete only your test names). `workspace -h` for help.
Hosts added later must still be $LAB per RoE — workspace is not permission.
3. Defender parallel
SIEM cases use IDs like workspaces — separate incidents, shared tooling. Building the habit early prevents cross-contamination in notes.
4. What you ship: workspace name for Topic 14
Created workspace topic14_m1 (or similar). Listed workspaces. No hosts added outside $LAB. chmod 600.
5. What you record before the next lesson
Date. workspace name. workspace list output. File t14-m02-l03-workspaces.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
Use default workspace for every ad-hoc public scan. Delete workspace -D all on a shared machine.
Right
Named workspace for Cyberlium T14. Next: Console Lab.
Mission: create a Topic 14 workspace
1) msfconsole -q 2) workspace -a topic14_m1 3) workspace (list) 4) exit 5) Save output chmod 600.
Stuck? Ask Cyberlium AI Mentor
Workspace name is a label — RoE still governs targets.
Knowledge Check
APPLY: Workspaces mainly:
Multiple choice
Knowledge Check
APPLY: True or False: Adding a host in workspace means any IP is in scope.
True or False
Knowledge Check
APPLY: Create workspace with:
Multiple choice