Threat modeling is best described as what?

• A. Reactive process after deployment
• B. Proactive identification of security threats during design
• C. Only for penetration testing
• D. Only used for compliance

Answer: (B)

Threat modeling focuses on identifying security threats early, by analyzing the system’s design and architecture during planning and before code is written. It involves mapping assets, trust boundaries, attacker capabilities, and potential attack paths to spot threats proactively and prioritize mitigations that address the most significant risks. This proactive, design-time approach is what makes it the best description: you’re recognizing and planning defenses before deployment, not reacting afterward.

Think of modeling how data flows through the system—where sensitive data moves, where it’s stored, and who or what accesses it. This helps surface risks like leakage or tampering and leads to concrete design decisions, such as input validation, encryption, and appropriate access controls.

In contrast, a reactive process after deployment focuses on fixing issues once they’re already in production, which misses the opportunity to prevent them in the first place. It’s not limited to penetration testing, and it isn’t just about meeting compliance requirements; threat modeling informs secure design choices across the architecture.