Skip to main content

​
What this check does

Checks open HIGH/CRITICAL Security Command Center findings as unresolved incidents. Passes when: Incidents closed.

​
Why this matters

Track and close incident remediation in DSALTA.

​
How to fix

Close out the open Security Command Center findings
  1. Sign in to the Google Cloud Console and go to Security → Security Command Center → Findings.
  2. In the Quick filters panel, set Severity to Critical and High and State to Active — those are the findings this check counts as open incidents.
  3. Open each finding and follow the Recommendation on its detail panel to fix the affected resource — for example remove a public IAM binding, enable a missing log, or rotate an exposed key.
  4. Let the detector re-scan; a remediated finding moves to State: Inactive on its own. For a finding you have formally accepted, use Mute → Mute finding and record why.
  5. In DSALTA, go to Data Library → Incidents and open the matching record.
  6. Fill in Root cause, Remediation, and Lessons learned, set Status to Closed, and save — the change is timestamped against your name in the Timeline.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.