Skip to main content
Checks that GCP users are identified and documented.

​
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 the Google Cloud Platform (GCP) integration is connected.
Identify all users
  1. In Google Cloud Platform (GCP), review all users and service accounts with access (in GCP: IAM & Admin → IAM).
  2. Ensure each is a known, named individual — remove generic or shared accounts.
  3. In DSALTA, confirm all users appear in Data Library → Access and map to real employees.
Once all users are identified, DSALTA sets the check status to Passing.

​
Frequently Asked Questions

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.
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.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
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).