Skip to main content
Checks that users with access to critical systems are authorized in Snowflake.

​
About

When you connect Snowflake 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

Access tends to accumulate over time as roles change, leaving people with more than they need. Excess access widens your attack surface and breaks the principle of least privilege. Regularly validating who can reach critical systems is a core control in SOC 2 and ISO 27001.

​
How to Fix

Before you begin
  • Ensure the Snowflake integration is connected so DSALTA has the current list of users.
Validate user access
  1. In DSALTA, go to Data Library → Access and filter for Snowflake.
  2. Review each user’s role and permission against their current job function.
  3. For any user whose access is no longer appropriate, remove it in Snowflake or adjust their role.
  4. In DSALTA, mark each reviewed user as In Scope (valid) or Not in Scope (to be revoked), and record the reviewer.
  5. Set a recurring access review schedule (quarterly is recommended).
Once all users have valid, documented access, DSALTA sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Snowflake 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 Snowflake.