Security › Module 9 › Lesson 2
Decision Records
Threat model review literacy — STRIDE coverage check, trust boundary verification, mitigation trace, open threat stub, review cadence — named TM review rows on YOUR `$ARCH_LAB` LAB-ARCH-001.
Visual · t41_threat_model_reviews
Threat model review = named STRIDE rows. $ARCH_LAB LAB-ARCH-001. Original Cyberlium.
Opening
Threat model reviews verify STRIDE coverage — name verification rows on YOUR lab org before adding offensive exploit steps as 'threat awareness.'
Threat model review literacy names: STRIDE coverage check category, trust boundary verification category, mitigation trace category, open threat stub category, and review cadence category. Analyst documents threat model review sheet on `$ARCH_LAB` LAB-ARCH-001 — links Module 4 STRIDE worksheet — without documenting offensive exploit how-tos, without reviewing stranger org threat models without authorization, without marking all threats mitigated without evidence. Cyberlium teaches defensive threat model review vocabulary on YOUR notes. Refused: offensive exploit recipes, stranger org TM theft, fake mitigation closure. Lab row: threat model review sheet (STRIDE check, boundary verify, open threat stub, LAB label).
1. Named TM review rows
STRIDE coverage, boundary verify, mitigation trace, open threat, cadence — five anchors.
Review cites Module 4 STRIDE worksheet on LAB-ARCH-001 — defensive mitigations only.
Command guide
Try these commands — Named TM review rows
═══ 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, python3. Reference sites: NIST 800-53 (https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final); NIST 800-53B (https://csrc.nist.gov/publications/detail/sp/800-53b/final); OWASP ASVS (https://owasp.org/www-project-application-security-verification-standard/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. Mitigation trace discipline
Mitigation trace links Module 8 control selection — honest open threat stub if gap remains.
No offensive step-by-step in review findings — defensive control references only.
3. Refused
No offensive exploit how-tos; no stranger org TM theft; no fake all-mitigated fiction.
TM review literacy supports defensive design — not attack cookbooks.
4. What you ship: threat model review sheet
STRIDE check + boundary verify + mitigation trace + open threat + NEVER exploit how-to line.
5. What you record before the next lesson
Threat model review sheet path.
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
Add offensive exploit step-by-step to `$ARCH_LAB` threat model review as 'awareness homework.'
Right
Threat model review sheet from `$ARCH_LAB` LAB-ARCH-001. Next: Documentation Standards.
Mission: threat model review sheet
1) Name five TM review literacy rows. 2) STRIDE coverage from Module 4 worksheet. 3) Mitigation trace to Module 8 controls. 4) Write NEVER offensive exploit how-to line.
Stuck? Ask Cyberlium AI Mentor
Ask Mentor: “Open threat stub — literacy when to document?”
Knowledge Check
APPLY: Threat model review literacy uses:
Multiple choice
Knowledge Check
APPLY: True or False: Offensive exploit steps belong in TM review.
True or False
Knowledge Check
APPLY: Threat model review includes:
Multiple choice