Professional review status
No professional domain review recorded
This bundle covers security, privacy, legal, safety subject matter. It uses cited sources to support research, but it is not professional advice and should not be the sole basis for consequential decisions.
Review before reliance: Qualified system owner, security architect, threat modeler, privacy, legal, safety, operations, and risk-acceptance reviewers.
Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.
Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Deliverable guide
Threat Model source-backed deliverable guide
Evidence-grounded planning, review, and authority boundaries for Threat Model.
Read the fileOverview
Threat Model overview
Scope, evidence, and authority boundaries for Threat Model.
Read the fileWorkflow
Threat Model source-backed workflow
Verify-first workflow for producing a reviewable threat model and mitigation decision record.
Read the fileQuality rubric
Threat Model source verification check
Rubric for checking evidence status, grounding, and authority boundaries.
Read the fileIs this bundle right for your task?
Who it is for
- People drafting, reviewing, approving, or relying on Threat Model
- Teams working in Cybersecurity, Software
When to use it
- A Threat Model draft needs a clear purpose, audience, evidence base, structure, and approval path.
- An existing draft needs unsupported claims, missing sections, unresolved decisions, and reviewer comments addressed.
What you need to provide
- The document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action.
- Existing drafts, templates, policies, examples, terminology, and review criteria that the output must follow.
Tasks and expected outputs
Questions it helps answer
- Model threats without inventing architecture, assets, adversary capability, vulnerabilities, control effectiveness, exploitability, or risk acceptance.
- Prepare a reviewable threat model and mitigation decision record with explicit evidence, limitations, validation, and approval boundaries.
What it helps produce
- threat model and mitigation decision record
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action. Ask the agent to draft or review Threat Model and return threat model and mitigation decision record with material claims tied to evidence and assumptions, open questions, reviewers, and approval gates marked. Begin with csrc.nist.gov — 154 / Ipd, then confirm that the reference is current and applicable. Inspect Threat Model source-backed deliverable guide before drafting.
Context path: bundles/deliverables/threat-model
What the bundle includes
Frameworks
- system, asset, trust-boundary, threat, control, residual-risk, and review analysis
Evaluations
- Threat Model source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Publishing, approving, or acting on a draft before its material claims, source evidence, owners, and approval gates have been reviewed.
Known limitations
- NIST and OWASP sources describe threat-modeling approaches but do not establish local architecture, assets, threats, vulnerabilities, likelihood, control operation, residual risk, compliance, or risk-acceptance authority.
- Task-specific conclusions require current inspected evidence for system and environment versions, architecture and data-flow diagrams, asset and data classifications, identity and trust boundaries, dependency and supplier evidence, threat intelligence scope and date, abuse cases, control design and test evidence, vulnerability records, ranking criteria and uncertainty, mitigations and owners, residual-risk decisions, reviews, and approvals.
- This bundle does not grant authority to access or test systems without authorization, expose sensitive architecture, declare vulnerabilities, change controls, exploit weaknesses, accept risk, claim security or compliance, or publish the model.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, medical, and unreleased information.
- Preserve prompt-supplied facts as Provided and mark missing facts Needs verification; do not invent owners, dates, versions, reviewers, or system state.
- Require explicit confirmation from an evidenced authorized reviewer before taking any action to access or test systems without authorization, expose sensitive architecture, declare vulnerabilities, change controls, exploit weaknesses, accept risk, claim security or compliance, or publish the model.