Skip to main content

​
What this check does

Manual review or label checks.
This check also runs on 2 other integrations — see Infra entity should be classified for the full list.
Passes when: Classification in place.

​
Why this matters

Classification supports governance.

​
How to fix

Classify your GCP infrastructure entities
  1. Sign in to the Google Cloud Console and open the resource the test flagged — for example Compute Engine → VM instances or Cloud Storage → Buckets.
  2. Click the resource, click Edit, expand Labels, click + Add label, and add the key criticality with a value from one vocabulary — critical, high, medium, or low — then click Save.
  3. Label whole projects in one place from IAM & Admin → Labels: add the same criticality key there and click Save.
  4. In DSALTA, go to Data Library → Inventory and filter the Source column to GCP.
  5. Click each asset whose Tags column is empty, add the matching tag (for example criticality:critical), and set an Owner so the classification has someone accountable behind it.
  6. For anything outside your audit boundary, open the asset drawer and choose Mark as out of scope instead of tagging it.
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.