Skip to main content

​
What this check does

Checks SCC API for enabled state. Passes when: Security Center is enabled.

​
Why this matters

SCC provides threat and vulnerability visibility.

​
How to fix

Enable Security Command Center
  1. Sign in to the Google Cloud Console with the Organization Administrator role and navigate to Security → Security Command Center.
  2. Use the resource picker at the top of the page to select your organization — Security Command Center is activated at the organization level, not per project.
  3. Click Enable Security Command Center and choose a service tier: Standard for free basic findings, or Premium / Enterprise for threat detection and compliance reporting.
  4. On the services step, turn on Security Health Analytics, Web Security Scanner, and Event Threat Detection.
  5. Grant the Security Center Admin permissions when prompted, then click Enable.
  6. Open Settings → Continuous Exports, click Create export, and point findings at a Pub/Sub topic or email channel so new findings are surfaced to your team.
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.