You manage a large fleet of Compute Engine instances. Security Health Analytics (SHA) has generated a CONFIDENTIAL_COMPUTING_DISABLED finding within Security Command Center (SCC). You need to…

The correct answer is D. Delete the offending VM instance, and allow the finding to be automatically marked as inactive. When you delete the offending VM instance, the related SHA finding will be automatically marked as inactive in Security Command Center (SCC). This is the correct and efficient way to remediate the finding without manually muting or disabling detectors, ensuring the issue is…

Detecting Threats

Question

You manage a large fleet of Compute Engine instances. Security Health Analytics (SHA) has generated a CONFIDENTIAL_COMPUTING_DISABLED finding within Security Command Center (SCC). You need to quickly remediate this finding. What should you do?

Options

ADelete the offending VM instance, and mute the finding.
BDelete the offending VM instance, and disable the SHA detector.
CDelete the offending VM instance, and manually mark the finding as inactive.
DDelete the offending VM instance, and allow the finding to be automatically marked as inactive.

How the community answered

(33 responses)

A
12% (4)
B
6% (2)
C
3% (1)
D
79% (26)

Explanation

When you delete the offending VM instance, the related SHA finding will be automatically marked as inactive in Security Command Center (SCC). This is the correct and efficient way to remediate the finding without manually muting or disabling detectors, ensuring the issue is resolved and tracked properly.

Topics

#Security Command Center#Security Health Analytics#finding remediation#Confidential Computing

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-SECURITY-OPERATIONS-ENGINEER Practice