nerdexam
Isaca

CRISC · Question #584

Recent penetration testing of an organization's software has identified many different types of security risks. Which of the following is the MOST likely root cause for the identified risk?

The correct answer is B. Threat modeling was not utilized in the software design process. The discovery of many different types of security risks through penetration testing in an organization's software most likely indicates a failure in early design-phase security practices.

Submitted by carter_n· Apr 18, 2026IT Risk Assessment

Question

Recent penetration testing of an organization's software has identified many different types of security risks. Which of the following is the MOST likely root cause for the identified risk?

Options

  • ASIEM software is producing faulty alerts.
  • BThreat modeling was not utilized in the software design process.
  • CThe configuration management process is not applied consistently during development.
  • DAn identity and access management (IAM) tool has not been properly integrated into the software.

How the community answered

(13 responses)
  • A
    8% (1)
  • B
    69% (9)
  • C
    15% (2)
  • D
    8% (1)

Why each option

The discovery of many different types of security risks through penetration testing in an organization's software most likely indicates a failure in early design-phase security practices.

ASIEM software is producing faulty alerts.

SIEM software producing faulty alerts is an operational issue related to monitoring, not a root cause for fundamental security risks in software design or development itself.

BThreat modeling was not utilized in the software design process.Correct

Threat modeling is a structured approach to identify potential threats and vulnerabilities early in the software development lifecycle, during the design phase. If threat modeling was not utilized, security risks would not be identified and addressed proactively, leading to numerous vulnerabilities being discovered later during penetration testing.

CThe configuration management process is not applied consistently during development.

Inconsistent configuration management could lead to some vulnerabilities, but a wide variety of risks points to a more fundamental issue in initial security design rather than just configuration.

DAn identity and access management (IAM) tool has not been properly integrated into the software.

Improper integration of an IAM tool would lead to specific authentication/authorization vulnerabilities, but 'many different types of security risks' suggests a broader failure than just IAM.

Concept tested: Threat modeling in SDLC

Source: https://learn.microsoft.com/en-us/security/engineering/threat-modeling-tool-getting-started

Topics

#Threat Modeling#Software Security Design#Vulnerability Root Cause#Penetration Testing

Community Discussion

No community discussion yet for this question.

Full CRISC Practice