Security › Module 3 › Lesson 4
Lab — SbD
Pack shift left named, requirements security, and privacy by design — security-by-design file from $ARCH_LAB only.
Visual · t41_sbd_lab
Lab: security-by-design pack. $ARCH_LAB only. Original Cyberlium.
Opening
SBD pack merges shift left to requirements to privacy — paperwork before STRIDE threat modeling module.
Lessons 3-1–3-3 named shift left, requirements security, and privacy by design. This lab merges three sections into one $ARCH_LAB SBD artifact with M1 ethics and M2 defense cross-references. No real PII, employer backlog imports, or attack cookbooks — security-by-design paperwork only. Next: Quiz — Security by Design.
1. Lab contract: security-by-design pack
Create $HOME/cyberlium-lab/t41-m03-l04-sbd-lab.txt merging shift left, requirements security, and privacy by design sections with $ARCH_LAB fictional org LAB-ARCH-001 and M1/M2 cross-references.
Optional: link requirements to layer map from M2 by system name.
Command guide
Try these commands — Lab contract: security-by-design pack
═══ LINUX / macOS (Terminal Practice) ═══
Check system state and user context
Command — copy this
id whoami uname -a
Inspect network sockets listening for connections
Command — copy this
ss -tuln 2>/dev/null || netstat -tuln
Audit active processes
Command — copy this
ps aux | grep -v "\[" | head -15
═══ WINDOWS (POWERSHELL) ═══ Query user identity and system information
Command — copy this
whoami /all Get-ComputerInfo | Select-Object CsName, OsName, OsVersion
Primary tools to practice this lesson: grep, curl. Reference sites: NIST 800-53 (https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final); OWASP ASVS (https://owasp.org/www-project-application-security-verification-standard/); Microsoft SDL (https://www.microsoft.com/en-us/securityengineering/sdl/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Cross-check ethics
Grep for real emails, live attack steps in abuse cases, employer sprint exports — remove. Confirm all data categories are $ARCH_LAB placeholders.
Abuse cases stay design-review context — not offensive cookbooks.
3. Lock the proof
chmod 600 on the pack. Quiz next — then STRIDE Named.
Security-by-design literacy feeds STRIDE lessons in M4.
4. What you ship: security-by-design pack for $ARCH_LAB
Merged shift left, requirements, privacy sections. $ARCH_LAB named. NO real PII. chmod 600.
5. What you record before the next lesson
Date. SBD pack path. $ARCH_LAB named. File t41-m03-l04-sbd-lab.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
Include real customer email in requirements. Draft live attack steps in abuse case.
Right
Write YOUR security-by-design pack for $ARCH_LAB. chmod 600. Next: Quiz — Security by Design.
Mission: freeze YOUR security-by-design pack on disk
1) Merge M3 literacy sections. 2) Confirm placeholder data only. 3) Link M1/M2 cross-refs. 4) chmod 600.
Stuck? Ask Cyberlium AI Mentor
One governed SBD pack beats ten inconsistent sprint security sticky notes.
Knowledge Check
APPLY: This lab requires:
Multiple choice
Knowledge Check
APPLY: True or False: SBD pack should include testable security acceptance criteria.
True or False
Knowledge Check
APPLY: SBD pack supports:
Multiple choice