Threat Modeling

Decide what a design must be true before code exists: naming assets and actors, locating trust boundaries, producing a written (asset, boundary, threat, control, owner) list, recording the assumptions the design rests on, and knowing when a change invalidates the model. Use when scaffolding a new feature, service, or endpoint, writing or reviewing a design doc, RFC, or ADR, or introducing a new trust boundary, integration, or data flow.

ShieldNet-360 Updated 23 repo stars

File contents

ShieldNet-360/secure-vibe commit 5dbf729ac9

Frequently asked questions

npx get-skill add shieldnet-360/threat-modeling