stride-threat-modeling
Run a STRIDE-based threat modeling workshop — diagram the system, enumerate threats per element, rank them, and drive mitigations into the backlog. Use during design reviews and new feature planning.
v2026.8.26-b2b6b523 installs+3 in 7 days0 Starssynced 19 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install securityskills/stride-threat-modelingWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package504f8f4b…a45ab124
504f8f4b0426…b87ba45ab1241 file · 1.2 KBScanMedium1 finding
- No license found
Sourcegithub.com/securityskills/skills/tree/main/threat-modeling/stride-threat-modeling@b2b6b52
On this page
Threat model a system in a structured workshop format.
1. Model the System
Draw the diagram: processes, data stores, data flows, external actors, and trust boundaries (dashed lines where privilege/context changes).
- Every element numbered; technologies noted on processes/stores
- Include the boring parts: auth flows, async jobs, admin tooling, backups
2. Enumerate with STRIDE
For each element, apply the applicable categories:
| Category | Applies To | Question |
|---|---|---|
| Spoofing | Processes, actors | Can someone pretend to be this? (auth) |
| Tampering | Flows, stores | Can data be modified in transit/at rest? (integrity) |
| Repudiation | Processes | Can actions be denied? (logging/audit) |
| Information disclosure | Flows, stores | Can data leak to unauthorized parties? (confidentiality) |
| Denial of service | Processes, flows | Can this be exhausted or crashed? (availability) |
| Elevation of privilege | Processes | Can rights be gained? (authz) |
Work systematically: element × category grid so nothing is skipped.
3. Rank
Score each threat by impact (worst realistic outcome) × likelihood (attack complexity, exposure). Prioritize: unauthenticated remote > authenticated remote > local > physical.
4. Mitigate
For each accepted threat, pick a strategy: reduce (control), transfer, accept (documented, with owner), or avoid (design change). Map mitigations to concrete backlog tickets with acceptance criteria.
5. Validate
- Review the model when the architecture changes (trigger: new external dependency, new trust boundary, new data class)
- Retro: incidents found in prod vs threats previously modeled — feed misses back into the method
Output
System diagram with trust boundaries, element × STRIDE threat grid, ranked risk register, and mitigations as tracked tickets.
Files in this version
- SKILL.md2.1 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumLicense · No license found
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.8.26-b2b6b52 | Nov 13, 2026 | b2b6b52 | 504f8f4b | Signed | – |
More from securityskills
All from this publisherMore in Recon and OSINT
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login