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 the GCP service account user/token creator role is not assigned at the project level.

​
Why This Matters

Stale or overly permissive credentials are a primary attack vector. Unused access keys, unrotated credentials, and root account usage all expand your blast radius. Credential hygiene is a core control in SOC 2 (CC6.1) and CIS Benchmarks.

​
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 will detect the change on the next sync cycle and update the status to Passing. You can also trigger a manual sync from Settings → Integrations → Google Cloud Platform (GCP).

​
How to Fix

If this test is failing, follow these steps to remediate:
  1. Sign in to the Google Cloud Console and navigate to IAM & Admin → IAM.
  2. Review all IAM bindings at the project level.
  3. Identify any entries with the role Service Account User (roles/iam.serviceAccountUser) or Service Account Token Creator (roles/iam.serviceAccountTokenCreator) assigned at the project level.
  4. Remove these project-level bindings and instead assign the role at the service account level (on specific service accounts only).
  5. Once removed from project level, DSALTA will detect the change on the next sync 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. The assigned responsible role receives a notification. Remediate the issue before it affects 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. Remediation actions must be performed by your team directly in Google Cloud Platform (GCP).