Question 680
A Microsoft Azure administrator receives this requirement: A regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints. Which operating control most directly reduces this recurring risk?
Explanation
Correct Answer
This guardrail addresses defender for cloud cloud security benchmark: A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. The prevention measure is: Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. “Require residual-risk signoff and evidence of compensating controls before closing high-severity posture exceptions” would address that alternative cause, not the condition in this question: a cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation.
“Continuously reconcile external attack surface discovery with mergers, new domains and cloud service changes” responds to this separate finding: internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. This question instead needs “Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy”, so the alternative does not meet the stated condition.
Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption. “Continuously audit subscription plan coverage after creating or moving subscriptions” applies to that separate problem. The observed case is a regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints; choosing this alternative would address the wrong failure mode.