What is a threat model and what are common steps in creating one?

Get ready for your WGU ITEC2034 D385 Software Security and Testing Test. Study with multiple choice questions that include hints and explanations. Boost your confidence for your exam day!

Multiple Choice

What is a threat model and what are common steps in creating one?

Explanation:
A threat model is a structured representation of potential threats to a system, helping you understand what could go wrong and where to focus defenses. In practice, you map out what you’re protecting, who might threaten it, how data flows through the system, and where weaknesses could be exploited. Common steps in creating one include: defining the scope and security objectives for the system, identifying and classifying assets and security requirements, building a simplified model of the system (including data flows and trust boundaries), enumerating potential threats to those assets (using a method like STRIDE), assessing risk by considering likelihood and impact, selecting and implementing mitigations or controls to reduce risk, and finally documenting and regularly reviewing the threat model to keep it current. The other descriptions don’t fit because they describe things like coding standards, performance testing frameworks, or hardware configuration guides, which aren’t about systematically identifying and mitigating threats to a system.

A threat model is a structured representation of potential threats to a system, helping you understand what could go wrong and where to focus defenses. In practice, you map out what you’re protecting, who might threaten it, how data flows through the system, and where weaknesses could be exploited.

Common steps in creating one include: defining the scope and security objectives for the system, identifying and classifying assets and security requirements, building a simplified model of the system (including data flows and trust boundaries), enumerating potential threats to those assets (using a method like STRIDE), assessing risk by considering likelihood and impact, selecting and implementing mitigations or controls to reduce risk, and finally documenting and regularly reviewing the threat model to keep it current.

The other descriptions don’t fit because they describe things like coding standards, performance testing frameworks, or hardware configuration guides, which aren’t about systematically identifying and mitigating threats to a system.

Subscribe

Get the latest from Examzify

You can unsubscribe at any time. Read our privacy policy