Define threat modeling and its importance in MDC3 security.

• A. Threat modeling is about implementing encryption.
• B. Threat modeling is a test to see if system is secure.
• C. Threat modeling is a structured process to identify potential threats, attack surfaces, and mitigations early in design; it reduces risk in MDC3 security.
• D. Threat modeling is a compliance checklist.

Answer: (C)

Threat modeling is a proactive, structured approach used during system design to identify where threats could come from, what parts of the system are exposed (attack surfaces), and what defenses would mitigate those threats. By doing this early, it helps reduce risk in MDC3 security by guiding architectural decisions, prioritizing security controls, and allocating resources to the most significant issues. In practice, you map assets and data flows, define trust boundaries, consider potential attackers and their capabilities, sketch possible attack paths, assess risk, and then specify mitigations such as secure design practices, authentication and authorization improvements, input validation, appropriate encryption, logging and monitoring, and defense-in-depth. This is an ongoing activity that evolves with the design, not a one-time check.

This stands in contrast to encryption being the sole focus, or to treating security as only a test after implementation, or reducing security to a simple compliance checklist.