Knowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search exact control and technique identifiers, Cyber Wiki articles, framework records, playbooks, books, podcasts, Academy courses, individual lessons, and BMC Cyber Challenge activities.

Design practiceIntermediate

Threat Modeling

Threat modeling examines what must be protected, how a system works, where trust changes, what can go wrong, and which safeguards or design changes reduce risk.

What it means

Teams may use structured methods, diagrams, misuse cases, attack trees, or scenario discussions. The value comes from shared reasoning and decisions, not from producing a perfect diagram.

Why it matters

Threat modeling helps teams find risky assumptions before they become deployed vulnerabilities or operational surprises.

Practical focus

  • Define assets, actors, data flows, and trust boundaries
  • Consider abuse and failure as well as expected use
  • Record decisions, assumptions, and unresolved risk
  • Update the model when architecture or use changes

Common mistakes

  • Completing the exercise after design is fixed
  • Focusing only on named attack techniques
  • Creating a document that engineers never use

BMC v0.2.2 cornerstone expansion

Start analysis of Threat Modeling with the mission or business outcome, then identify assets, identities, data, trust boundaries, dependencies, expected behavior, and credible failure or abuse cases.

Translate those observations into preventive, detective, responsive, and recovery controls. A mature explanation states not only what the concept is, but also how a practitioner demonstrates that it is working under normal, abnormal, and recovery conditions.

Evidence of effective implementation

  • Documented ownership, scope, decision criteria, and permitted exceptions.
  • Configuration or architectural evidence tied to a clear control objective.
  • Operational telemetry showing expected and unexpected behavior.
  • Testing that covers normal use, abuse cases, failure, rollback, and recovery.
  • Exceptions that are approved, time bounded, monitored, and revisited.
  • Lessons learned that result in updated designs, procedures, detections, or training.

Questions for learners

  • Which security properties and business outcomes does Threat Modeling support?
  • What assumptions must remain true for the control or process to work safely?
  • What could an attacker, insider, failure, or design error do at each trust boundary?
  • Which evidence would prove that controls work continuously rather than only on paper?
  • How would the organization respond, restore service, and re-establish trust after failure?

Certification relevance

This subject appears in or supports the following certification bodies of knowledge:

ISC2 CISSPCompTIA Security+ISC2 CCSP

Authoritative sources