Latest IIBA-CCA Practice Questions BY Boyle

A cybersecurity infrastructure business case is typically driven by the Risk function because the justification for security investments is grounded in reducing enterprise risk to an acceptable level and aligning with the organization's risk appetite and regulatory obligations. Risk-focused teams (often working with the CISO and security governance) translate threats, vulnerabilities, and control gaps into business impact terms such as likelihood of adverse events, potential operational disruption, financial exposure, regulatory penalties, and reputational harm. This framing is what a formal business case requires: a clear problem statement, quantified or prioritized risk scenarios, expected risk reduction from proposed controls, and how residual risk compares to tolerance thresholds.

While IT usually leads implementation and provides architecture, sizing, and operational cost estimates, IT alone does not typically ''drive'' the business case without the risk rationale that explains why the investment is necessary and what enterprise outcomes it protects. Legal contributes requirements related to compliance, contracts, and breach handling, but it generally supports rather than owns investment prioritization. Finance evaluates budgeting, funding options, and return-on-investment assumptions, yet it relies on risk inputs to understand why the spend is warranted and what loss exposure is being reduced.

Therefore, the organizational area most responsible for driving a cybersecurity infrastructure business case---by defining the risk problem, articulating risk-based benefits, and enabling executive decision-making---is Risk.

Bottom of Form

When analyzing a web-based business environment for potential cost savings, the Business Analyst must account for application vulnerabilities because they directly affect the organization's exposure to cyber attack and the true cost of operating a system. Vulnerabilities are weaknesses in application code, configuration, components, or dependencies that can be exploited to compromise confidentiality, integrity, or availability. In web environments, common examples include insecure authentication, injection flaws, broken access control, misconfigurations, outdated libraries, and weak session management.

Cost-saving recommendations frequently involve consolidating platforms, reducing tooling, lowering support effort, retiring controls, delaying upgrades, or moving to shared services. Without including known or likely vulnerabilities, the analysis can unintentionally recommend changes that reduce preventive and detective capability, increase attack surface, or extend the time vulnerabilities remain unpatched. Cybersecurity governance guidance emphasizes that technology rationalization must consider security posture: vulnerable applications often require additional controls (patching cadence, WAF rules, monitoring, code fixes, penetration testing, secure SDLC work) that carry ongoing cost. These costs are part of the system's ''total cost of ownership'' and should be weighed against proposed savings.

While impact severity and threat likelihood are important for overall risk scoring, the question asks what risk factor must be included when documenting the current state of a web-based environment. The most essential factor that ties directly to the environment's condition and drives remediation cost and exposure is application vulnerabilities.