threat-modellisted

# Threat Model ## Purpose Create a threat model that delivers actionable, measurable results. **Category**: Cybersecurity & Information Security ## Inputs ### Required - **Objective**: What you want to achieve with this deliverable - **Context**: Relevant background information (systems, scope, environment) ### Optional - **Constraints**: Any limitations or requirements to consider - **Existing Work**: Previous documents or data to build on ## Context Before starting, read the repo's `CLAUDE.md` and any relevant notes under `memory/` (e.g. `memory/repo/<repo>/`, `memory/feedback/`) for prior decisions and constraints. ## Process ### Step 1: Context & Research - Review any existing threat model documents in the project - Identify key stakeholders and their requirements - Select the most appropriate framework: STRIDE, PASTA, LINDDUN ### Step 2: Analysis & Framework Application - Apply the selected framework to structure the threat model - Identify gaps, opportunities, and risks - Define success metrics: Threats Identified per Component, Mitigations Coverage %, Residual Risk Score, Trust Boundary Violations - Document assumptions and dependencies - Validate approach against industry best practices ### Step 3: Build the Deliverable - Structure the threat model using the output format below - Include specific, actionable recommendations — not generic advice - Add concrete numbers, timelines, and benchmarks where applicable - Cross-reference with existing project docume