Cyberlium

Zero › Module 1 › Lesson 2

BeginnerModule 1Lesson 2/5

Lab Designs Only

Lab org only means YOUR fictional organization templates under $ZT_LAB — labeled courseware org profiles, self-authored architecture diagrams — document org scope in notes before any ZT exercise.

25 min+40 XP3 quiz
Module progress2 of 5

Visual · t40_lab_org_only

Org scope. $ZT_LAB only. Original Cyberlium.

Opening

The org label is part of scope — Cyberlium refuses ZT exercises that paste real employer network diagrams or production IdP exports into lab templates without fictional labeling.

Your ZT lab org is a fictional company YOU define — Cyberlium ZT Fictional Corp, LabHybrid Co, example.zt.local service catalog — with made-up users, apps, segments, and trust gaps for learning. Templates live on $ZT_LAB only — never copied from live breach reports, real customer network maps, or employer confidential architecture files. Cyberlium maps allowed org inventory on YOUR $ZT_LAB — org name, hybrid workforce label, app list, fictional segment map — never borrowed employer production diagrams or scraped real company ZT assessments. Next: No Attack Tools.

1. Allowed org surfaces (named)

Self-authored fictional org profiles with explicit training labels. Courseware ZT packs with example.zt.local assets. Architecture diagrams using placeholder system names and synthetic trust zones. Gap checklists on templates you created — not employer confidential files.

On $ZT_LAB, list org inventory row — org name, workforce model, app count, fictional segment label — never paste real employee directories or employer VPN topology PDFs into lab notes.

Command guide

Try these commands — Allowed org surfaces (named)

═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)

NIST SP 800-207 — https://csrc.nist.gov/publications/detail/sp/800-207/final CISA ZTMM — https://www.cisa.gov/zero-trust-maturity-model

═══ INSTALL ═══

Linux (Debian/Ubuntu):

Command — copy this

sudo apt install curl

macOS: Built-in

Windows: Built-in (PowerShell: Invoke-WebRequest)

═══ LINUX / macOS ═══

Command — copy this

mkdir -p "$HOME/cyberlium-lab/t40-zt/notes" "$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/identity" "$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/devices" "$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/network" "$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/data" "$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/policy" "$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/roadmap"
cat > "$HOME/cyberlium-lab/t40-zt/lab.env" <<'EOF'
export ZT_LAB=$HOME/cyberlium-lab/t40-zt
export ZT_ORG=$HOME/cyberlium-lab/t40-zt/LAB-ZT-001
export ZT_IDENTITY=$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/identity
export ZT_DEVICES=$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/devices
export ZT_NETWORK=$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/network
export ZT_DATA=$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/data
export ZT_POLICY=$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/policy
export ZT_ROADMAP=$HOME/cyberlium-lab/t40-zt/LAB-ZT-001/roadmap
EOF

Command — copy this

chmod 600 "$HOME/cyberlium-lab/t40-zt/lab.env"
grep -E 'ZT_' "$HOME/cyberlium-lab/t40-zt/lab.env"
curl -sS https://csrc.nist.gov/publications/detail/sp/800-207/final | head -5

Primary tools to practice this lesson: grep, curl. Reference sites: NIST SP 800-207 (https://csrc.nist.gov/publications/detail/sp/800-207/final); CISA ZTMM (https://www.cisa.gov/zero-trust-maturity-model). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.

2. Why org scope matters before ZT work

ZT roadmaps and policy matrices reference users, devices, apps, and data classes. Scope is what keeps practice ethical and legally safe. Employer production network diagrams, real IdP tenant exports, and live vendor assessment files copied into lab work are out of scope.

If you cannot answer 'is this org fictional and labeled lab-only?', pause and fix scope notes before building architecture artifacts.

3. Org inventory habit

Forbidden: importing employer architecture packs because lab orgs look too simple. Allowed: org inventory row — name, hybrid/remote model, apps, source = $ZT_LAB self-authored fictional template.

Ship: org inventory row for one fictional lab org. Next: No Attack Tools.

4. What you ship: org inventory row for $ZT_LAB

One fictional org with app list and segment labels. $ZT_LAB named. NEVER real employer diagram imports. chmod 600.

5. What you record before the next lesson

Date. Org inventory row. $ZT_LAB named. File t40-m01-l02-lab-org-only.txt chmod 600.

6. Wrong vs right: bypass cookbooks vs YOUR ZT design

Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.

  • Wrong

    Paste employer ZT assessment into lab because realism helps. Skip fictional label because it is just notes.

  • Right

    Write org inventory row for YOUR $ZT_LAB fictional org. Next: No Attack Tools.

Mission: document YOUR fictional org inventory

1) Write one fictional org name and workforce model. 2) List three lab apps with segment labels. 3) Confirm zero real employer diagram imports. 4) chmod 600.

Stuck? Ask Cyberlium AI Mentor

Org inventory exists for scope — use fictional templates instead of employer confidential files.

Knowledge Check

1

APPLY: Lab org only on Cyberlium means:

Multiple choice

Knowledge Check

2

APPLY: True or False: ZT lab orgs on $ZT_LAB use explicit fictional labels.

True or False

Knowledge Check

3

APPLY: Before building a ZT diagram you should:

Multiple choice

← Previous

Answer all 3 knowledge checks to continue. (0/3 answered)