Menu

Individual skill

regulatory-threat-model

0upvotes

Threat-model regulatory and compliance risk — mapping legal obligations to security controls and residual exposure.

skills/regulatory-threat-model/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
56
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Regulatory threat modeling applies threat-modeling discipline to compliance risk: systematically identifying which regulations apply, where the organization is exposed, what controls mitigate the exposure, and what residual risk remains. It turns "we need to be compliant" from a vague anxiety into a structured, prioritized work program.

This skill covers the method: obligation inventory, exposure analysis per obligation, control mapping, residual-risk assessment, and the ongoing monitoring that keeps the model honest as regulations evolve. It is practical guidance, not legal advice.

Think like an attacker, but the attacker is a regulator with a checklist and penalty schedule: where would they find you non-compliant, what evidence would they ask for, and what would the finding cost? That adversarial framing finds the gaps that self-assessed "we're probably fine" misses.

## When to use

- Entering new jurisdictions or sectors with unfamiliar regulatory landscapes.
- Building the compliance roadmap with prioritized, costed work items.
- Assessing regulatory exposure before M&A, funding, or major product launches.
- Rationalizing overlapping obligations into one control program.
Back to top