A company is assessing nth-party risk from a critical cloud provider. Which approach should be taken to manage this risk effectively?
Contractual flow-down obligations make the cloud provider accountable for vetting, monitoring and reporting on its own subcontractors, satisfying the stem's nth-party risk requirement. Direct assessment of every downstream supplier is impractical, so the provider becomes the control point.
Why this answer
The correct approach is to require the cloud provider to contractually manage and report on their subcontractors. Under CISM's governance principles, an organization cannot feasibly audit every nth-party (subcontractor) directly, so it must extend its risk management through contractual flow-down clauses. This ensures the provider assumes responsibility for vetting, monitoring, and reporting on its own supply chain, giving the customer visibility and accountability without overstepping operational boundaries.
Exam trap
CISM often tests the misconception that direct auditing of nth parties is feasible or that ignoring them is acceptable, when the correct governance answer is always to push responsibility down through contracts and reporting.
How to eliminate wrong answers
Option A is wrong because replacing the cloud provider with an in-house solution is a disproportionate, costly overreaction that ignores the business benefits of cloud services and does not inherently eliminate nth-party risk. Option B is wrong because conducting a direct audit of the provider's subcontractors is typically impractical, may violate contractual boundaries, and is not scalable for complex supply chains. Option C is wrong because ignoring nth-party risk is a governance failure — regulators and frameworks (e.g., GDPR, DORA, NIST) explicitly require visibility into the extended supply chain.