About
When you connect Google Cloud Platform (GCP) to DSALTA, the platform syncs your users, roles, and access settings using read-only API access. DSALTA evaluates this control on every sync. If the requirement is not met, DSALTA activates this check.Why This Matters
Generic or shared accounts make it impossible to attribute actions to a person, which undermines accountability and audit trails. Ensuring every user is individually identified is a foundational access-control requirement in SOC 2 and ISO 27001.How to Fix
Before you begin- Ensure you have the appropriate admin role on the GCP project.
- Sign in to the Google Cloud Console and navigate to IAM & Admin → Essential Contacts.
- Click Add contact and add contacts for each notification category, especially Security.
- Save.
Frequently Asked Questions
How often does this check run?
How often does this check run?
This check runs automatically every 24 hours while the Google Cloud Platform (GCP) integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
What happens if it keeps failing?
What happens if it keeps failing?
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Can I exclude this check?
Can I exclude this check?
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
Does DSALTA change my Google Cloud Platform (GCP) configuration?
Does DSALTA change my Google Cloud Platform (GCP) configuration?
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Google Cloud Platform (GCP).
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)