Security › Module 1 › Lesson 4
Lab — Setup
Pack architecture scope, fictional org inventory, and ethics disclaimer — lab setup file only, dest $ARCH_LAB.
Visual · t41_lab_setup
Lab: write architecture setup pack. $ARCH_LAB only. Original Cyberlium.
Opening
Lab setup before architecture exercises — scope paperwork mentors expect before defense-in-depth and STRIDE modules.
Lessons 1–3 defined why security architecture matters, lab fictional only, and no offensive architecture. This lab ships the combined artifact: topic scope paragraph, fictional org inventory row for LAB-ARCH-001, and ethics card for $ARCH_LAB under $HOME/cyberlium-lab/t41-arch/. No attack cookbooks or real employer diagram imports required — scope and org paperwork first. Next: Quiz — Arch Mindset and Lab.
1. Lab contract: write the setup pack
Create $HOME/cyberlium-lab/t41-m01-l04-lab-setup.txt with date, operator, $ARCH_LAB placeholder, literacy vs offensive architecture paragraph, fictional org inventory row for LAB-ARCH-001, and ethics card with defensive disclaimer.
Optional: one-line proof your t41-arch folder exists — still no attack cookbooks or employer diagram imports required in this lab.
Command guide
Try these commands — Lab contract: write the setup pack
═══ 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/ SABSA — https://sabsa.org/
═══ 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
export ARCH_LAB=${ARCH_LAB:-$HOME/cyberlium-lab/t41-arch}
cat > "$ARCH_LAB/roe.txt" <<'EOF'
ARCH_LAB=$HOME/cyberlium-lab/t41-arch
org: fictional LAB-ARCH-001 — multi-tier SaaS platform literacy stub (not a real company)
targets: YOUR defense/, security-design/, stride/, patterns/, sabsa/, enterprise/, controls/, review/ folders
never: offensive attack cookbooks; exploit chains against strangers; unauthorized bypass how-tos
never: present LAB SAMPLE diagrams as production security sign-off
allowed: STRIDE worksheets; DFD markdown; defense-in-depth diagrams; SABSA stubs; control tables
allowed: review checklists; curl OWASP, Microsoft SDL, NIST, SABSA/TOGAF literacy pages
output: markdown stubs in lab folder — educational defensive design only
EOFCommand — copy this
chmod 600 "$ARCH_LAB/roe.txt" grep -E 'ARCH_LAB|never|allowed|LAB-ARCH-001|LAB SAMPLE' "$ARCH_LAB/roe.txt" cat > "$ARCH_ORG/org-profile.md" <<'EOF' # LAB-ARCH-001 — Fictional Org Profile (literacy only) - **Type:** Multi-tier SaaS platform literacy stub - **Scope:** web app + API gateway + microservices + managed DB (fictional) - **Users:** fictional customers, admins, partner integrations (educational trust-boundary exercise) - **Frameworks:** OWASP ASVS literacy + Microsoft SDL + NIST 800-160 + SABSA/TOGAF stubs - **Disclaimer:** NOT a real organization — templates for YOUR lab only EOF
Command — copy this
grep -E 'Fictional|Disclaimer|LAB-ARCH-001' "$ARCH_ORG/org-profile.md" ls -la "$ARCH_ORG/"
═══ WINDOWS ═══
Run on YOUR lab Windows VM only
Command — copy this
Get-Content $HOME/cyberlium-lab/t41-arch/roe.txt | Select-String never Get-ChildItem $HOME/cyberlium-lab/t41-arch/LAB-ARCH-001
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/); SABSA (https://sabsa.org/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Cross-check against misuse patterns
Grep notes for 'attack cookbook,' unauthorized target blueprint steps, real customer PII — redact or delete. Rewrite forum habits to $ARCH_LAB fictional placeholders before you copy templates.
Classmates build their own setup packs for their $ARCH_LAB — not yours.
3. Lock the proof
chmod 600 on the pack. Quiz is next — then Layers Named.
Architecture mentors archive lab setup before first trust boundary exercise; you are practicing that habit early.
4. What you ship: architecture lab setup pack for $ARCH_LAB
Setup pack: scope, org row LAB-ARCH-001, ethics card. $ARCH_LAB named. NEVER offensive architecture. chmod 600.
5. What you record before the next lesson
Date. Setup pack path. $ARCH_LAB scope note. File t41-m01-l04-lab-setup.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
Skip the file and import employer network PDF. Add attack cookbook template to approved list.
Right
Write YOUR lab setup pack for $ARCH_LAB. chmod 600. Next: Quiz — Arch Mindset and Lab.
Mission: freeze YOUR architecture lab setup pack on disk
1) Merge scope, org inventory, ethics sections. 2) Name $ARCH_LAB and LAB-ARCH-001. 3) chmod 600. Never list offensive architecture as approved practice.
Stuck? Ask Cyberlium AI Mentor
Setup packs are boring on purpose — boring keeps architecture work defensible.
Knowledge Check
APPLY: This lab requires:
Multiple choice
Knowledge Check
APPLY: True or False: You should chmod 600 on architecture lab notes.
True or False
Knowledge Check
APPLY: A tutorial drafts attack paths against live targets. You:
Multiple choice