<!-- Copyright (c) 2026 defconxt. All rights reserved. -->
<!-- Licensed under AGPL-3.0 — see LICENSE file for details. -->
<!-- NERF is a trademark of defconxt. -->
---
name: implementing-threat-model-review-process
description: >-
  Implement structured threat model review processes with quality gates.
domain: cybersecurity
subdomain: threat-modeling
tags:
  - review-process
  - quality-gates
  - sdlc-integration
  - peer-review
  - continuous-validation
  - governance
version: "1.0"
author: defconxt
license: AGPL-3.0
metadata:
  mitre-attack:
  - "T1195"
  - "T1199"
---

# Implementing Threat Model Review Process

## Overview

Threat models degrade without regular review. This technique establishes a structured review
process with peer review checklists, quality gates for CI/CD integration, stakeholder sign-off
workflows, and triggers for re-assessment when architecture changes occur.

Mode: `[MODE: ARCHITECT]` — Governance and continuous assurance for threat models.

## Prerequisites

- Existing threat model documentation
- Defined SDLC phases with security touchpoints
- Python 3.10+
- Version control system (Git)

## Key Concepts

### Review Triggers

| Trigger | Action | SLA |
|---------|--------|-----|
| New feature / epic | Create or update threat model | Before design review |
| Architecture change | Re-assess affected components | Within sprint |
| Dependency update (major) | Review supply chain threats | Within 5 business days |
| Security incident | Validate model coverage | Within 48 hours |
| Quarterly schedule | Full model review | Every 90 days |

### Quality Gates

| Gate | Criteria | Stage |
|------|----------|-------|
| **Completeness** | All components modeled, DFDs current | Design |
| **Coverage** | STRIDE applied to trust boundary crossings | Development |
| **Mitigations** | Every HIGH+ threat has documented mitigation | Pre-release |
| **Validation** | Mitigations verified through testing | Release |

## Workflow

### Step 1: Assess Threat Model Currency

```bash
node scripts/agent.js --action assess --input threat_model.json
node scripts/agent.js --action validate --input threat_model.json
```

### Step 2: Run Quality Gate Checks

```bash
node scripts/agent.js --action gates --input threat_model.json
node scripts/agent.js --action gates --input threat_model.json --query completeness
```

### Step 3: Generate Review Report

```bash
node scripts/agent.js --action report --input threat_model.json --output review.json
```

## Verification

- [ ] Review process documented with roles, triggers, and SLAs
- [ ] Quality gates integrated into CI/CD pipeline
- [ ] Peer review checklist applied to every threat model update
- [ ] Stakeholder sign-off captured and tracked
- [ ] Review history maintained for audit trail
- [ ] Metrics tracked: review frequency, finding density, time to remediate

## References

- [OWASP Threat Modeling Process](https://owasp.org/www-community/Threat_Modeling_Process)
- [SAFECode — Tactical Threat Modeling](https://safecode.org/resource-secure-development-practices/tactical-threat-modeling/)
- [NIST SP 800-160 Vol. 1 — Systems Security Engineering](https://csrc.nist.gov/publications/detail/sp/800-160/vol-1/final)
- [Microsoft SDL Threat Modeling](https://www.microsoft.com/en-us/securityengineering/sdl/threatmodeling)
