Dark › Module 3 › Lesson 2
Identity Separation
Identity compartment literacy names work vs lab personas, device boundaries, and MFA habits — map compartment rows on YOUR $DW_LAB before metadata hygiene lesson.
Visual · t39_identity_compartment
Identity compartment literacy. $DW_LAB only. Original Cyberlium.
Opening
One identity for everything deanonymizes everything — literacy teaches compartment rows so $DW_LAB notes separate work, lab, and refused criminal personas.
Identity compartmentation separates work persona — employer SSO, managed device, ticketed monitoring tools — from lab persona — $DW_LAB notes, fictional alert stubs — and explicitly refuses blending criminal persona research with employer credentials. Password reuse across compartments and missing MFA on work identity are common failure modes. Cyberlium writes identity compartment row on YOUR $DW_LAB — work persona, lab persona, refused blend rule, MFA note. Next: Metadata Hygiene.
1. Compartment components (named)
Work persona: employer SSO, managed device, authorized monitoring tools with ticket scope. Lab persona: $DW_LAB notes only — fictional FAKE-CORP alert stubs and literacy cards. Refused blend: never mix criminal persona research with employer credentials or production networks.
On $DW_LAB, write compartment row — persona name, device type, account type, allowed activity for work and lab.
Command guide
Try these commands — Compartment components (named)
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
EFF SSD — https://ssd.eff.org/module/creating-strong-passwords Tor Manual — https://tb-manual.torproject.org/ CISA — https://www.cisa.gov/secure-our-world/use-strong-passwords
═══ INSTALL ═══
Linux (Debian/Ubuntu):
macOS:
Windows:
═══ LINUX / macOS ═══
Command — copy this
export DW_LAB=${DW_LAB:-$HOME/cyberlium-lab/t39-dw}
cat > "$DW_OPSEC/identity-compartment-card.txt" <<'EOF'
Identity compartment literacy (defensive):
Work persona: employer SSO, managed device, ticketed monitoring tools
Lab persona: $DW_LAB notes only — fictional alert stubs
Never: blend criminal persona research with employer credentials
Never: reuse passwords across compartments — MFA on work identity
Row: compartment | device | account type | allowed activity
EOFCommand — copy this
grep -E 'Work persona|Never|compartment' "$DW_OPSEC/identity-compartment-card.txt"
Primary tools to practice this lesson: grep. Reference sites: EFF SSD (https://ssd.eff.org/module/creating-strong-passwords); Tor Manual (https://tb-manual.torproject.org/); CISA (https://www.cisa.gov/secure-our-world/use-strong-passwords). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Why compartmentation protects defenders and learners
Analysts browsing unauthorized dark-web content on employer credentials create incident and legal exposure. Lab work on personal VM with fictional data keeps training separated from production identity.
Students document compartment rows on notes — production identity management follows employer IAM policy.
3. Lab boundary
Forbidden: reusing employer passwords in lab, conducting criminal forum research logged into work SSO, storing employer credentials in $DW_LAB notes. Allowed: identity compartment card — work vs lab rows with $DW_LAB fictional labels.
Ship: identity compartment row for YOUR lab notes. Next: Metadata Hygiene.
4. What you ship: identity compartment row for $DW_LAB
Work persona, lab persona, refused blend, MFA note. $DW_LAB named. chmod 600.
5. What you record before the next lesson
Date. Identity compartment row. $DW_LAB named. File t39-m03-l02-identity-compartment.txt chmod 600.
6. Wrong vs right: criminal markets vs YOUR OPSEC lab
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Use work laptop for unauthorized Tor browsing 'because lab VM is slow.' Reuse work password on personal lab account.
Right
Write identity compartment row for YOUR $DW_LAB. Next: Metadata Hygiene.
Mission: document identity compartments on YOUR lab notes
1) Define work persona boundaries. 2) Define lab persona for $DW_LAB. 3) Write refused blend rule. 4) Note MFA on work identity. chmod 600.
Stuck? Ask Cyberlium AI Mentor
Compartment rows prevent employer credential contamination in lab work.
Knowledge Check
APPLY: Identity compartment literacy on Cyberlium covers:
Multiple choice
Knowledge Check
APPLY: True or False: Lab persona on $DW_LAB is limited to fictional notes and alert stubs.
True or False
Knowledge Check
APPLY: Identity compartment on Cyberlium uses:
Multiple choice