Security-control investments should be evaluated according to organizational risk, implementation requirements, operational benefits, and total cost before being presented for executive approval.
Because the proposed cloud controls introduce significant expenditure, the architect must establish whether their expected benefits justify the associated financial and operational impact.
This assessment should identify which threats or compliance obligations each control addresses, the assets and processes affected, and the potential consequences of leaving the relevant risks untreated.
Cost analysis should include licensing, cloud resource consumption, administrative effort, integration requirements, maintenance, and possible performance effects.
Operational benefits may include improved attack prevention, stronger access restrictions, enhanced monitoring, reduced incident-response costs, and better compliance assurance.
The architect should also determine whether less expensive compensating controls can achieve an acceptable level of risk reduction.
A structured comparison enables the CISO to consider alternative implementation options, prioritize expenditure, and make an informed risk-management decision.
Option A prematurely limits consideration to a single control without establishing comparative value.
Option B provides useful compliance input but does not independently evaluate economic feasibility.
Option D concerns remaining contractual expenditure rather than the cost-effectiveness of the proposed controls.
The strongest approach is therefore to understand the control requirements and compare their costs against measurable operational and risk-reduction benefits.
Official reference / study topic: Splunk certification blueprint, Governance Risk and Compliance: control cost-benefit evaluation.
===============
Submit