Question 1020
Following the issue — Defender Vulnerability Management reveals software weaknesses on Azure VMs but the team ranks them only by CVSS without asset exposure. — the team takes this action: Prioritize remediation using severity, exploitability, asset criticality and actual exposure context. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Revisit risk scores when threat intelligence or workload exposure changes. This mitigates the control weakness because: Technical vulnerability severity is one input to risk-based cloud remediation. Keep the intervention, Prioritize remediation using severity, exploitability, asset criticality and actual exposure context., in the approved deployment, monitoring and change governance process.
Incorrect Answers
This safeguard is for the dependency described by: Automated closure should not substitute for verified containment and incident disposition. The continuing risk here is determined by: Technical vulnerability severity is one input to risk-based cloud remediation. The targeted safeguard is “Revisit risk scores when threat intelligence or workload exposure changes”.
That review protects the control associated with: Backup security must resist intentional or accidental destruction by compromised high-privilege identities. It does not directly prevent the stated recurrence, which concerns: Technical vulnerability severity is one input to risk-based cloud remediation. The appropriate guardrail is “Revisit risk scores when threat intelligence or workload exposure changes”.
This safeguard is for the dependency described by: Automated compliance mappings indicate control posture rather than a complete legal determination. The continuing risk here is determined by: Technical vulnerability severity is one input to risk-based cloud remediation. The targeted safeguard is “Revisit risk scores when threat intelligence or workload exposure changes”.