AgentAlley

Skills · Security

Threat Mitigation Mapping

Unverified●30/40

Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.

Originally by wshobson · MIT

Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add threat-mitigation-mapping

This command does not work yet — the CLI is still being built. Until then, use Raw in the reader below to take the file.

Who is stuck, and on what

Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.

The whole source

No sign-in, no blur, nothing truncated
threat-mitigation-mapping/SKILL.md83 lines3.3 KBRawView on GitHub
Frontmatter — 2 properties
namethreat-mitigation-mapping
descriptionMap identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.
1---
2name: threat-mitigation-mapping
3description: Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.
4---A5 — No allowed-tools declared — no way to tell what this skill may touch
5 
6# Threat Mitigation Mapping
7 
8Connect threats to controls for effective security planning.
9 
10## When to Use This Skill
11 
12- Prioritizing security investments
13- Creating remediation roadmaps
14- Validating control coverage
15- Designing defense-in-depth
16- Security architecture review
17- Risk treatment planning
18 
19## Core Concepts
20 
21### 1. Control Categories
22 
23```
24Preventive ────► Stop attacks before they occur
25 │ (Firewall, Input validation)
26 │
27Detective ─────► Identify attacks in progress
28 │ (IDS, Log monitoring)
29 │
30Corrective ────► Respond and recover from attacks
31 (Incident response, Backup restore)
32```
33 
34### 2. Control Layers
35 
36| Layer | Examples |
37| --------------- | ------------------------------------ |
38| **Network** | Firewall, WAF, DDoS protection |
39| **Application** | Input validation, authentication |
40| **Data** | Encryption, access controls |
41| **Endpoint** | EDR, patch management |
42| **Process** | Security training, incident response |
43 
44### 3. Defense in Depth
45 
46```
47 ┌──────────────────────┐
48 │ Perimeter │ ← Firewall, WAF
49 │ ┌──────────────┐ │
50 │ │ Network │ │ ← Segmentation, IDS
51 │ │ ┌────────┐ │ │
52 │ │ │ Host │ │ │ ← EDR, Hardening
53 │ │ │ ┌────┐ │ │ │
54 │ │ │ │App │ │ │ │ ← Auth, Validation
55 │ │ │ │Data│ │ │ │ ← Encryption
56 │ │ │ └────┘ │ │ │
57 │ │ └────────┘ │ │
58 │ └──────────────┘ │
59 └──────────────────────┘
60```
61 
62## Templates and detailed worked examples
63 
64Full template library and detailed mitigation/control mappings live in `references/details.md`. Read that file when you need the concrete templates for: Mitigation Model, Defense in Depth scoring, Executive Summary scaffolding, Critical Gaps reporting, Recommendations, Implementation Roadmap, Results by Control.
65 
66## Best Practices
67 
68### Do's
69 
70- **Map all threats** - No threat should be unmapped
71- **Layer controls** - Defense in depth is essential
72- **Mix control types** - Preventive, detective, corrective
73- **Track effectiveness** - Measure and improve
74- **Review regularly** - Controls degrade over time
75 
76### Don'ts
77 
78- **Don't rely on single controls** - Single points of failure
79- **Don't ignore cost** - ROI matters
80- **Don't skip testing** - Untested controls may fail
81- **Don't set and forget** - Continuous improvement
82- **Don't ignore people/process** - Technology alone isn't enough
83 

Reviews

Installed this one?Write the first review and take the Trailblazer badge.

Reviews only open after a real install, so this is empty — and we leave it empty rather than invent one.

Alternatives

Also in Security
Block No Verify HookConfigure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.Security · MIT◐····●35/40Sast ConfigurationConfigure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.Security · MIT◐····●32/40Binary Analysis PatternsMaster binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.Security · MIT◐◐◐◐◐●31/40Anti Reversing TechniquesUnderstand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use this skill when analyzing malware evasion techniques, when implementing anti-debugging protections for CTF challenges, when reverse engineering packed binaries, or when building security research tools that need to detect virtualized environments.Security · MIT◐◐◐◐◐●30/40