# Threat Mitigation Mapping

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

Source: https://skillsagentes.com/skills/wshobson/agents/threat-mitigation-mapping
Repository: https://github.com/wshobson/agents
Author: wshobson
License: MIT
Updated: hace 2 meses
Context cost: 45 tok installed, 837 tok once triggered, 6.7k tok with every bundled file
Bundle: 2 files, 26 KB
Permissions requested: none declared

## Install

```bash
npx -y skills add wshobson/agents --skill threat-mitigation-mapping --agent claude-code
```

## What it does

- Mapea amenazas identificadas a controles y mitigaciones de seguridad apropiados
- Clasifica controles en categorías preventivas, detectivas y correctivas
- Organiza controles por capas (red, aplicación, datos, endpoint, proceso)
- Genera plantillas para roadmap de implementación, resumen ejecutivo y reporte de brechas críticas

## Use it when

- Al priorizar inversiones en seguridad
- Al crear planes de remediación o roadmaps
- Al validar la cobertura y efectividad de controles
- Al diseñar defensa en profundidad o revisar arquitectura de seguridad

## What triggers it

- "Ayúdame a mapear estas amenazas a controles de seguridad"
- "Necesito un plan de remediación priorizado según riesgo"
- "Evalúa si tenemos defensa en profundidad para esta arquitectura"
- "Crea un roadmap de implementación de controles de seguridad"

## Before you install

- Requiere leer references/details.md para acceder a las plantillas y mapeos detallados de controles.

## Files

- SKILL.md — 3 KB
- references/details.md — 23 KB

## SKILL.md

Reproduced verbatim from wshobson/agents under MIT. This section is the upstream document and is in English.

# Threat Mitigation Mapping

Connect threats to controls for effective security planning.

## When to Use This Skill

- Prioritizing security investments
- Creating remediation roadmaps
- Validating control coverage
- Designing defense-in-depth
- Security architecture review
- Risk treatment planning

## Core Concepts

### 1. Control Categories

```
Preventive ────► Stop attacks before they occur
   │              (Firewall, Input validation)
   │
Detective ─────► Identify attacks in progress
   │              (IDS, Log monitoring)
   │
Corrective ────► Respond and recover from attacks
                  (Incident response, Backup restore)
```

### 2. Control Layers

| Layer           | Examples                             |
| --------------- | ------------------------------------ |
| **Network**     | Firewall, WAF, DDoS protection       |
| **Application** | Input validation, authentication     |
| **Data**        | Encryption, access controls          |
| **Endpoint**    | EDR, patch management                |
| **Process**     | Security training, incident response |

### 3. Defense in Depth

```
                    ┌──────────────────────┐
                    │      Perimeter       │ ← Firewall, WAF
                    │   ┌──────────────┐   │
                    │   │   Network    │   │ ← Segmentation, IDS
                    │   │  ┌────────┐  │   │
                    │   │  │  Host  │  │   │ ← EDR, Hardening
                    │   │  │ ┌────┐ │  │   │
                    │   │  │ │App │ │  │   │ ← Auth, Validation
                    │   │  │ │Data│ │  │   │ ← Encryption
                    │   │  │ └────┘ │  │   │
                    │   │  └────────┘  │   │
                    │   └──────────────┘   │
                    └──────────────────────┘
```

## Templates and detailed worked examples

Full 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.

## Best Practices

### Do's

- **Map all threats** - No threat should be unmapped
- **Layer controls** - Defense in depth is essential
- **Mix control types** - Preventive, detective, corrective
- **Track effectiveness** - Measure and improve
- **Review regularly** - Controls degrade over time

### Don'ts

- **Don't rely on single controls** - Single points of failure
- **Don't ignore cost** - ROI matters
- **Don't skip testing** - Untested controls may fail
- **Don't set and forget** - Continuous improvement
- **Don't ignore people/process** - Technology alone isn't enough

---

Skills Agentes — https://skillsagentes.com/skills/wshobson/agents/threat-mitigation-mapping