Security › Module 4 › Lesson 1
STRIDE Named
STRIDE named literacy covers Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, and Elevation of privilege — map STRIDE row on YOUR $ARCH_LAB fictional component for design review.
Visual · t41_stride_named
STRIDE named literacy. $ARCH_LAB only. Original Cyberlium.
Opening
Threat categories without names scatter review — literacy teaches STRIDE vocabulary so fictional org components on $ARCH_LAB get structured threat analysis for defensive design.
STRIDE — Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege — organizes threat thinking for architecture and design review. On Cyberlium you apply STRIDE to fictional LAB-ARCH-001 components — lab API gateway, example.local auth service — to document mitigations, not to draft attack cookbooks against live targets. Cyberlium writes STRIDE row on YOUR $ARCH_LAB — component name, one STRIDE category, example mitigation for LAB-ARCH-001. Next: Trust Boundaries.
1. STRIDE categories (named)
Spoofing: fake identity on YOUR fictional auth endpoint. Tampering: unauthorized data change in transit or at rest. Repudiation: missing audit trail on LAB-ARCH-001 admin action. Information disclosure: data leak across trust boundary. Denial of service: availability attack on example.local service. Elevation of privilege: gaining unauthorized role.
On $ARCH_LAB, write STRIDE row — component, category, mitigation example for one fictional element.
Command guide
Try these commands — STRIDE categories (named)
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
Microsoft STRIDE — https://learn.microsoft.com/en-us/azure/security/develop/threat-modeling-tool OWASP Threat Modeling — https://cheatsheetseries.owasp.org/cheatsheets/Threat_Modeling_Cheat_Sheet.html Microsoft SDL — https://www.microsoft.com/en-us/securityengineering/sdl/
═══ 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}
curl -sS https://learn.microsoft.com/en-us/azure/security/develop/threat-modeling-tool | head -10
cat > "$ARCH_LAB/notes/stride-named.txt" <<'EOF'
STRIDE — NAMED LITERACY (defensive threat modeling):
Spoofing: impersonating user/system — mitigate with strong authN
Tampering: unauthorized data change — integrity controls + validation
Repudiation: denying action — audit logs + non-repudiation where needed
Information disclosure: data leak — encryption + access control
Denial of service: availability impact — rate limits + redundancy literacy
Elevation of privilege: gaining higher access — least privilege + authZ
Lab: STRIDE worksheet markdown in stride/ — fictional LAB-ARCH-001 only
NEVER: turn worksheets into attack cookbooks against real systems
EOFCommand — copy this
grep -E 'Spoofing|Tampering|NEVER|worksheet' "$ARCH_LAB/notes/stride-named.txt"
Primary tools to practice this lesson: curl, grep. Reference sites: Microsoft STRIDE (https://learn.microsoft.com/en-us/azure/security/develop/threat-modeling-tool); OWASP Threat Modeling (https://cheatsheetseries.owasp.org/cheatsheets/Threat_Modeling_Cheat_Sheet.html); 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. Why STRIDE supports architecture review
Design reviews need shared threat vocabulary — STRIDE maps categories to control types. Documented mitigations survive sprint and architecture board questions on lab templates. STRIDE here means defensive analysis — not offensive exploit steps against real systems.
Students draft lab STRIDE notes — production threat models follow org methodology and authorized scope.
3. Lab boundary
Forbidden: converting STRIDE notes into step-by-step attack cookbook against live domains. Allowed: STRIDE named card — category and mitigation with $ARCH_LAB fictional component.
Ship: STRIDE row for YOUR lab component. Next: Trust Boundaries.
4. What you ship: STRIDE row for $ARCH_LAB
Component, STRIDE category, mitigation example. $ARCH_LAB named. chmod 600.
5. What you record before the next lesson
Date. STRIDE row. $ARCH_LAB named. File t41-m04-l01-stride-named.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
Write STRIDE as exploit walkthrough against real company. Skip mitigation column entirely.
Right
Write STRIDE row for YOUR $ARCH_LAB fictional component. Next: Trust Boundaries.
Mission: draft STRIDE on YOUR lab component
1) Name one fictional LAB-ARCH-001 component. 2) Pick one STRIDE category. 3) Write defensive mitigation example. 4) chmod 600.
Stuck? Ask Cyberlium AI Mentor
STRIDE on Cyberlium means defensive mitigations — not live attack recipes.
Knowledge Check
APPLY: STRIDE on Cyberlium literacy covers:
Multiple choice
Knowledge Check
APPLY: True or False: STRIDE includes Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, and Elevation of privilege.
True or False
Knowledge Check
APPLY: STRIDE literacy on Cyberlium uses:
Multiple choice