Security › Module 1 › Lesson 2
Lab Models Only
Lab fictional only means YOUR fictional organization LAB-ARCH-001 under $ARCH_LAB — labeled courseware org profiles, self-authored diagram scenarios — document org scope in notes before any architecture exercise.
Visual · t41_lab_fictional_only
Org scope. $ARCH_LAB only. Original Cyberlium.
Opening
The org label is part of scope — Cyberlium refuses architecture exercises that paste real employer network diagrams or customer environment data into lab templates without fictional labeling.
Your architecture lab org is a fictional company YOU define — LAB-ARCH-001, Cyberlium Fictional Corp, example.local service catalog — with made-up systems, trust boundaries, and design gaps for learning. Templates live on $ARCH_LAB only — never copied from live breach reports, real customer contracts, or employer confidential architecture files. Cyberlium maps allowed org inventory on YOUR $ARCH_LAB — org name LAB-ARCH-001, industry label, system list, fictional data classification — never 'borrowed' employer production diagrams or scraped real company infrastructure maps. Next: No Offensive Architecture.
1. Allowed org surfaces (named)
Self-authored fictional org profiles with explicit training labels. Courseware architecture packs with example.local assets. Diagram scenarios using placeholder system names and synthetic data classes. Design gap exercises on templates you created — not employer confidential files.
On $ARCH_LAB, list org inventory row — org name LAB-ARCH-001, industry, system count, fictional data label — never paste real customer PII or employer architecture 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)
OWASP ASVS — https://owasp.org/www-project-application-security-verification-standard/ Microsoft SDL — https://www.microsoft.com/en-us/securityengineering/sdl/ TOGAF — https://www.opengroup.org/togaf
═══ 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/t41-arch/notes" "$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/defense" "$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/security-design" "$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/stride" "$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/patterns" "$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/sabsa" "$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/enterprise" "$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/controls" "$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/review" cat > "$HOME/cyberlium-lab/t41-arch/lab.env" <<'EOF' export ARCH_LAB=$HOME/cyberlium-lab/t41-arch export ARCH_ORG=$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001 export ARCH_DEFENSE=$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/defense export ARCH_DESIGN=$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/security-design export ARCH_STRIDE=$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/stride export ARCH_PATTERNS=$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/patterns export ARCH_SABSA=$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/sabsa export ARCH_ENTERPRISE=$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/enterprise export ARCH_CONTROLS=$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/controls export ARCH_REVIEW=$HOME/cyberlium-lab/t41-arch/LAB-ARCH-001/review EOF
Command — copy this
chmod 600 "$HOME/cyberlium-lab/t41-arch/lab.env" grep -E 'ARCH_' "$HOME/cyberlium-lab/t41-arch/lab.env" curl -sS https://csrc.nist.gov/publications/detail/sp/800-160/vol-1/rev-1/final | head -5
Primary tools to practice this lesson: grep, curl. Reference sites: OWASP ASVS (https://owasp.org/www-project-application-security-verification-standard/); Microsoft SDL (https://www.microsoft.com/en-us/securityengineering/sdl/); TOGAF (https://www.opengroup.org/togaf). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Why org scope matters before architecture work
Trust boundaries and data flow diagrams reference systems and data classes. Scope is what keeps practice ethical and legally safe. Employer production network diagrams, real customer environment exports, and live infrastructure maps 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 diagram or threat model artifacts.
3. Org inventory habit
Forbidden: importing employer architecture packs because lab orgs 'look too simple.' Allowed: org inventory row — name LAB-ARCH-001, industry, systems, source = $ARCH_LAB self-authored fictional template.
Ship: org inventory row for one fictional lab org. Next: No Offensive Architecture.
4. What you ship: org inventory row for $ARCH_LAB
One fictional org LAB-ARCH-001 with system list and data labels. $ARCH_LAB named. NEVER real employer diagram imports. chmod 600.
5. What you record before the next lesson
Date. Org inventory row. $ARCH_LAB named. File t41-m01-l02-lab-fictional-only.txt chmod 600.
6. Wrong vs right: offensive playbooks vs YOUR threat models
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Paste employer network diagram into lab because 'realism helps.' Skip fictional label because 'it's just notes.'
Right
Write org inventory row for YOUR $ARCH_LAB fictional org LAB-ARCH-001. Next: No Offensive Architecture.
Mission: document YOUR fictional org inventory
1) Write org name LAB-ARCH-001 and industry. 2) List three lab systems with data classification 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
APPLY: Lab fictional only on Cyberlium means:
Multiple choice
Knowledge Check
APPLY: True or False: Architecture lab orgs on $ARCH_LAB use explicit fictional labels.
True or False
Knowledge Check
APPLY: Before building a trust boundary diagram you should:
Multiple choice