I'm leaning towards C as well. Threat modeling is a structured way to analyze the system, identify threats, and define appropriate security controls. The other options are more reactive approaches that come later in the development lifecycle.
Threat modeling sounds like the right approach here. It's all about proactively identifying potential security risks and vulnerabilities during the design process, which is key for building secure software from the ground up.
Hmm, I'm a bit unsure about this one. I know penetration testing and requirements review are important for security, but I'm not sure if they provide the same level of upfront threat identification as threat modeling. I'll have to think this through carefully.
I'm pretty sure the answer is C - Threat modeling. That's the practice that helps identify security threats and define security requirements during the design phase.
Ty
7 months agoLeonor
7 months agoTeddy
7 months agoTrinidad
7 months agoHuey
8 months agoWinifred
8 months agoJose
8 months agoLorrine
8 months agoDomonique
9 months agoVerda
9 months agoIsreal
9 months agoAriel
9 months agoDick
9 months agoMari
10 months agoNan
9 months agoJosue
9 months agoAntonio
9 months agoRaymon
9 months agoMira
10 months agoJettie
10 months agoEvelynn
11 months agoTarra
11 months agoJohana
11 months agoMaurine
11 months agoBrett
12 months agoJenelle
12 months agoMaurine
1 year ago