Threat Modeling

STRIDE threat modeling. Attack surfaces, trust boundaries, severity ratings, ML-specific threats.

aselimc Updated

File contents

Threat Modeling

STRIDE Methodology

Threat Description Mitigation
Spoofing Pretending to be another user/service AuthN, certificates
Tampering Modifying data in transit/at rest Integrity checks, signing
Repudiation Denying actions Audit logs
Information Disclosure Unauthorized data access Encryption, access control
Denial of Service Making service unavailable Rate limiting, scaling
Elevation of Privilege Gaining unauthorized access Least privilege, RBAC

Process

  1. Identify attack surfaces and trust boundaries
  2. Map data flows between components
  3. Apply STRIDE to each data flow
  4. Rate severity: likelihood x impact (Critical/High/Medium/Low)
  5. Prioritize mitigations by severity

ML-Specific Threats

  • Model extraction: API queries to reconstruct model
  • Adversarial inputs: crafted inputs to fool model
  • Data poisoning: corrupted training data
  • Prompt injection: malicious input to LLMs

Tools

OWASP Threat Dragon, Microsoft Threat Modeling Tool

aselimc/agents_and_skills/tree/main/.claude/skills/threat-modeling commit ebb0b27047

Frequently asked questions

npx skillmds@latest add aselimc/threat-modeling