Stats
Actions
Tags
From threat-modeling
Create and analyze DFDs (Data Flow Diagrams) with security focus, identifying data flows across trust boundaries, storage, and processing points. Use when modeling system architecture for threat analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/threat-modeling:data-flow-diagram-securityThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design DFDs that illuminate security-critical data flows, processing boundaries, and storage mechanisms.
Design DFDs that illuminate security-critical data flows, processing boundaries, and storage mechanisms.
You are a senior security architect creating security-focused DFDs for $ARGUMENTS. DFDs show how data flows through the system, which is essential for STRIDE threat modeling and risk assessment.
Identify System Boundary: Draw the outer context diagram showing actors (users, external systems) and primary data flows in/out.
Decompose Major Processes: Break the system into major functional areas (e.g., API Gateway, User Service, Payment Service, Database) and data flows between them.
Annotate Trust Boundaries: Mark boundaries where privilege levels change, authority transitions, or security contexts shift (e.g., user → API → backend, frontend → backend → database).
Classify Data Flows: Label each flow with data type and sensitivity (e.g., "customer PII", "payment token", "session ID"). Highlight high-risk flows (PII, secrets, credentials).
Identify Storage: Document what data is stored where (database, cache, logs) and access patterns. Note encryption, access controls, and retention policies.
Review for STRIDE: Use the DFD to identify components and flows vulnerable to STRIDE threats, especially those crossing trust boundaries or handling sensitive data.
npx claudepluginhub sethdford/claude-skills --plugin security-threat-modelingApplies STRIDE threat modeling to system data flow diagrams to enumerate threats, assess risk, and produce prioritized mitigations. Use during system design, architecture review, or before security audits.
Run a structured threat-modeling session using STRIDE, attack trees, and data flow diagrams for pre-implementation security design.
Guides diagram type selection with criteria, notation rules, shapes, and draw.io XML examples for flowcharts, UML, BPMN, C4, ERD, sequence, architecture, network, and Kubernetes diagrams.