Index of every page on this site: llms.txt
All skills
wshobson avatar

/threat-mitigation-mapping

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

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

Use this Skill: https://skilld.dev/gh/wshobson/agents/threat-mitigation-mapping

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈52 tokens for metadata: the name and description. ≈778 when used: this file. ≈5.9k more on demand in 1 file.

Description uses 2.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈209 characters, or 2.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides comprehensive documentation and Python code templates for threat mitigation mapping and security architecture review. It defines structured data models for threats, security controls, and risk analysis without any malicious functionality.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 4220308. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 6 months ago
  • threat-modeling
  • security-controls
  • risk-management
  • mitigation-planning
  • defense-in-depth
  • vulnerability-assessment
  • remediation
  • security-architecture

README badge

README badge for wshobson/agents/threat-mitigation-mapping

Maps identified threats to security controls and mitigations across network, application, data, endpoint, and process layers. Use this skill to prioritize security investments, validate control coverage, and design defense-in-depth strategies during risk treatment planning or security architecture reviews.

Generated from the current SKILL.md.

What is the difference between preventive, detective, and corrective controls?
Preventive controls stop attacks before they occur (e.g., firewalls, input validation). Detective controls identify attacks in progress (e.g., IDS, log monitoring). Corrective controls respond and recover after an attack (e.g., incident response, backup restore).
Does this skill help with defense-in-depth architecture?
Yes. The skill includes layered control models across network, application, data, endpoint, and process layers to design defense-in-depth strategies.
Where are the templates for creating mitigation roadmaps?
The skill references a `references/details.md` file that contains the full template library, including Mitigation Model, Defense in Depth scoring, Executive Summary scaffolding, and Implementation Roadmap templates.
Can this skill be used for validating existing security controls?
Yes. The skill explicitly supports validating control coverage and effectiveness as part of security architecture review and control validation workflows.

Generated from the current SKILL.md. These answers refresh after source changes.