skills.rest
machenjie
machenjieCOMMUNITY
Explore all skills by this author →
GitHub

threat-modeling

Construct explicit threat models mapping assets, trust boundaries, and mitigations.

4|Updated May 16, 2026
Search Tags:#access control#threat modeling#risk management#residual risk#security design#trust boundaries#abuse cases
One-click install
npx skills add https://github.com/machenjie/rd-skills --skill threat-modeling-machenjie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: threat-modeling
Source: https://github.com/machenjie/rd-skills/tree/main/src/foundation/capabilities/threat-modeling
Command: npx skills add https://github.com/machenjie/rd-skills --skill threat-modeling-machenjie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents high-impact security mistakes by forcing teams to define an explicit threat model that maps assets, trust boundaries, abuse cases, mitigations, and residual risk before implementation.

Core Features & Use Cases

  • Threat modeling with concrete abuse cases: Enumerates assets and actors (including insider/abuse-of-trust scenarios) to expose both attacker and legitimate-workflow misuse paths.
  • Trust-boundary driven risk design: Draws every trust boundary crossing (client→API gateway, gateway→backend, backend→DB, backend→third-party, admin UI→admin API) and requires validation/authorization design per boundary.
  • Mitigations tied to evidence: Requires each mitigation to include an implementation location, an executable/automated test ID or description, and production monitoring signals, plus explicit residual-risk acceptance with owner and review date.

Quick Start

Use the threat-modeling capability to produce a structured threat model for your planned change by providing the entry points, data flows, trust boundaries, and the specific mitigations you intend to implement.

Frequently Asked Questions about threat-modeling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is threat modeling and how does it help with security design?▼

Threat modeling is the process of identifying security and abuse risks by enumerating protected assets, actors, trust boundaries, and data flows. It ensures every threat is mapped to a mitigation with implementation ownership before development begins.

How do I create a threat model for public API authentication changes?▼

To create a threat model for public API authentication, provide the entry points, data flows, and trust boundaries. The model will enumerate abuse cases and require validation and authorization design for each boundary crossing, such as client to API gateway.

When do I need to perform threat modeling for sensitive data handling?▼

Threat modeling is required for high-impact changes involving sensitive data handling, administrative or tenant actions, infrastructure boundary changes, and security-critical architecture reviews to prevent severe security mistakes before implementation.

How are mitigations tied to evidence in a threat model?▼

Mitigations are tied to evidence by requiring an implementation location, an executable or automated test ID, and production monitoring signals. This ensures every security control is verified and actively monitored in production environments.

What is residual risk acceptance in threat modeling?▼

Residual risk acceptance is the documented approval of remaining risks after mitigations are applied. It requires an explicit owner, a review date, and defined escalation triggers to ensure accountability for any unmitigated threats.

Does this threat modeling approach cover insider and abuse-of-trust scenarios?▼

Yes, the threat modeling approach enumerates actors including insider and abuse-of-trust scenarios. It exposes both external attacker paths and legitimate-workflow misuse paths by drawing trust boundary crossings like admin UI to admin API.

Related Skills

Explore More Legal & Compliance Skills→
haabehaabe

threat-model

Conduct STRIDE threat modeling on system designs with data flows and trust boundaries.

Community
Advanced
SSiertsemaSSiertsema

risk-register

Maintain a canonical risk register with IDs, scores, controls, and history.

Community
Advanced
davidrrowleydavidrrowley

threat-modelling

Produce structured STRIDE threat models with DFD diagrams and DREAD scoring.

Community
Advanced
Handy369Handy369

security-and-hardening

Map trust boundaries and attacker paths in software changes.

Community
Intermediate