Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.dsalta.com/llms.txt

Use this file to discover all available pages before exploring further.

Checks that incidents detected in Google Security Command Center are closed.

​
Why This Matters

This configuration is a security baseline requirement. Without it, your environment may be exposed to unauthorized access, data loss, or compliance violations. Addressing this check ensures your Google Cloud Platform (GCP) environment meets industry best practices required by SOC 2, ISO 27001, and other compliance frameworks.

​
What DSALTA Checks

DSALTA connects to your Google Cloud Platform (GCP) environment using read-only API access and evaluates this configuration on every sync cycle. The test result appears in your Data Library → Tests dashboard:
  • Passing — The configuration meets requirements. No action needed.
  • Failing — The configuration does not meet requirements. Follow the remediation steps below.
  • Not configured — The integration is connected but the required service or feature has not been set up yet.
This test runs automatically every 24 hours. If you fix the underlying issue, DSALTA detects the change on the next sync and updates the status to Passing. You can also trigger a manual sync from Integrations in the sidebar.

​
How to Fix

If this test is failing, follow these steps in your Google Cloud Platform (GCP) console to remediate the issue. Refer to your platform’s official documentation for detailed guidance specific to your environment. Once the configuration is updated, DSALTA will detect the change on the next sync cycle and update the test status to Passing.

​
Frequently Asked Questions

This test runs automatically every 24 hours when the Google Cloud Platform (GCP) integration is connected. You can trigger a manual sync at any time from the integration settings page.
A failing test generates an alert in your DSALTA dashboard. Remediate the issue to maintain your compliance posture.
Yes. If this test does not apply to your environment, you can mark it as Not Applicable with a justification. This exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources in your environment.