50. Mitigated Threats — Threat Modelling

Summary

Threat families mitigated in this chapter + mitigation strength. The analysis follows the §26 canon §4 discipline: Manual surface + CAPEC primary; CWE supporting limited; mitigation strength explicitly labelled.

Six sections:

• § Manual ontology V2 entities — canonical Threat + AntiPattern + Signal
• § Threat surfaces — Manual + CAPEC primary surfaces
• § AntiPattern exposure mapping — antipattern → threat exposure relations
• § CWE references — supporting only (per §26 §4 discipline)
• § V1 overlay — mitigation pathway where Core-mapped
• § Future-work register — threat gaps registered for P8 §10

---

§ Manual ontology V2 — canonical entities (threats + antipatterns + signals)

Total: 18 entities (Threat × 16, AntiPattern × 2, Signal × 0) mapped to this chapter.

Entity type	ID	Label	Authority class	Source mode
Threat	MT-039	Unknown and unaddressed threats	normative	heuristic
Threat	MT-040	Poorly defined security priorities	normative	heuristic
Threat	MT-041	Requirements defined without a basis in threats	normative	heuristic
Threat	MT-042	Privacy threats ignored	normative	heuristic
Threat	MT-043	Lack of coverage of non-technical threats	normative	heuristic
Threat	MT-044	Insecure architecture not identified	normative	heuristic
Threat	MT-045	Superficial validation in design reviews	normative	heuristic
Threat	MT-046	Controls applied without a basis in architecture	normative	heuristic
Threat	MT-047	Absence of review of critical interfaces	normative	heuristic
Threat	MT-048	Threats discovered too late	normative	heuristic
Threat	MT-049	Critical changes without new modelling	normative	heuristic
Threat	MT-050	Discontinuity between teams and phases	normative	heuristic
Threat	MT-051	Threats not visible in the CI/CD pipeline	normative	heuristic
Threat	MT-052	Threat knowledge not accumulated	normative	heuristic
Threat	MT-053	Inconsistency between projects and teams	normative	heuristic
Threat	MT-054	Tools disconnected from the cycle	normative	heuristic
AntiPattern	sem:antipattern:ausencia-de-ameaca-no-modelo	Absence of a threat from the model	semantic	scored
AntiPattern	sem:antipattern:omissao-estrutural-de-ameacas	Structural omission of threats	semantic	scored

---

§ Threat surfaces — Manual + CAPEC primary

Canonical threat surfaces per Manual + CAPEC primary anchor (per §26 §4 discipline). Mitigation strength explicitly labelled (strong / partial / dependente_de_outros_capitulos).

Threat ID	Category	Essence	CAPEC anchor	Associated controls	Mitigation strength	§26 label
MT-039	STRIDE	Unknown and unaddressed threats	—	addon/01-metodologias-e-ferramentas.md	partial	Explicit
MT-040	STRIDE	Poorly defined security priorities	—	addon/07-mapeamento-threats-requisitos.md	partial	Explicit
MT-041	STRIDE	Requirements defined without a basis in threats	—	addon/07-mapeamento-threats-requisitos.md	partial	Explicit
MT-042	LINDDUN	Privacy threats ignored	—	addon/08-exemplo-privacidade.md	partial	Explicit
MT-043	STRIDE	Lack of coverage of non-technical threats	—	addon/01-metodologias-e-ferramentas.md	partial	Explicit
MT-044	STRIDE	Insecure architecture not identified	—	addon/09-validacao-arquitetura.md	partial	Explicit
MT-045	STRIDE	Superficial validation in design reviews	—	15-aplicacao-lifecycle.md	partial	Explicit
MT-046	STRIDE	Controls applied without a basis in architecture	—	addon/07-mapeamento-threats-requisitos.md	partial	Explicit
MT-047	STRIDE	Absence of review of critical interfaces	—	addon/01-metodologias-e-ferramentas.md	partial	Explicit
MT-048	STRIDE	Threats discovered too late	—	15-aplicacao-lifecycle.md	partial	Explicit
MT-049	STRIDE	Critical changes without new modelling	—	addon/09-validacao-arquitetura.md	partial	Explicit
MT-050	STRIDE	Discontinuity between teams and phases	—	addon/07-mapeamento-threats-requisitos.md	partial	Explicit
MT-051	STRIDE	Threats not visible in the CI/CD pipeline	—	addon/06-threat-modeling-ci.md	partial	Explicit
MT-052	STRIDE	Threat knowledge not accumulated	—	addon/10-integracao-iriusrisk.md	partial	Explicit
MT-053	STRIDE	Inconsistency between projects and teams	—	addon/01-metodologias-e-ferramentas.md	partial	Explicit
MT-054	STRIDE	Tools disconnected from the cycle	—	addon/07-mapeamento-threats-requisitos.md	partial	Explicit

---

§ AntiPattern exposure mapping

(No antipattern→threat relation mapped to this chapter.)

---

§ CWE references (supporting only)

(No threat with a CWE reference for this chapter.)

---

§ V1 overlay — mitigation pathway (where Core-mapped)

V1 controls/mechanisms anchored to this chapter that mitigate the threats listed above. The V1 overlay keeps the three-way routing visible per Manual ontology V2 + AppSec Core V1 + Substrate v7.

(The relations between anti-patterns, threats and controls are not yet complete in this version. Each entity's grounding in external sources is in the chapter's Traceability page.)

---

§ Future-work register (threat gaps)

(No threat in gap state for this chapter.)