Question 1060
Following the issue — A GitHub workflow contains a credential but security staff assume Defender DevOps Security automatically revokes leaked secrets. — the team takes this action: Triage the finding and rotate or revoke the secret through the owning credential system. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Connect secret detection findings to tracked rotation and code remediation steps. This mitigates the control weakness because: Detection of exposed credentials does not necessarily perform credential lifecycle remediation. Keep the intervention, Triage the finding and rotate or revoke the secret through the owning credential system., in the approved deployment, monitoring and change governance process.
Incorrect Answers
“Reconcile AWS account creation and removal with multicloud connector scope” addresses a different recurring failure: Connected cloud scope must align with the actual organizational account inventory. For the condition in this question, maintain “Connect secret detection findings to tracked rotation and code remediation steps” because detection of exposed credentials does not necessarily perform credential lifecycle remediation.
That review protects the control associated with: Certificate trust depends on expiry and proper deployment of renewed material to consuming services. It does not directly prevent the stated recurrence, which concerns: Detection of exposed credentials does not necessarily perform credential lifecycle remediation. The appropriate guardrail is “Connect secret detection findings to tracked rotation and code remediation steps”.
This safeguard is for the dependency described by: Unknown exposed services can bypass standard production security lifecycle controls. The continuing risk here is determined by: Detection of exposed credentials does not necessarily perform credential lifecycle remediation. The targeted safeguard is “Connect secret detection findings to tracked rotation and code remediation steps”.