Map Threats to Mitigation Controls

The skill connects threats to controls for effective security planning. It follows a fixed sequence: clarify the goals, constraints, and required inputs; apply relevant best practices and validate the outcome; and provide actionable steps with verification. When a request needs concrete patterns or worked examples of threat-to-control mapping, it opens resources/implementation-playbook.md for the detailed version rather than improvising.

Use it when prioritizing security investments, creating a remediation roadmap, validating control coverage against known threats, designing defense-in-depth, reviewing security architecture, or planning risk treatment. Do not use it for tasks unrelated to threat mitigation mapping, or when a different domain or tool is the better fit. It is not a substitute for environment-specific validation, testing, or expert review, and it stops to ask for clarification when required inputs, permissions, safety boundaries, or success criteria are missing.

Input is the identified threats or risk context and the planning purpose (investment prioritization, remediation roadmap, coverage validation, defense-in-depth design, architecture review, or risk treatment). Output is a threat-to-control mapping with actionable steps and verification, expanded into detailed patterns and worked examples via resources/implementation-playbook.md when the request calls for that depth.

Security architects and risk owners who need to justify security investments, build a remediation roadmap, or validate that existing controls actually cover the identified threats, rather than treating threats and controls as separate lists.