Information
Ensure that Snowflake password is unset for SCIM-managed users.
Allowing users to sign in with Snowflake passwords in the presence of a configured third-party identity provider SSO may undermine mandatory security controls configured on the SSO and degrade the security posture of the account. For example, the SSO sign-in flow may be configured to require multi-factor authentication (MFA), whereas the Snowflake password sign-in flow may not.
Note :
- This benchmark does not preclude configuration of key pair authentication https://docs.snowflake.com/en/user-guide/key-pair-auth.html for SSO users. Key pair authentication may be necessary for users to interact with Snowflake programmatically or through third party tools.
- To mitigate the risk of users not being able to sign-in due to SSO provider outage, ensure that at least one SSO break-glass user exists with Snowflake password reset privileges for account users. This break-glass user should be able to sign in using a Snowflake native password (coupled with MFA) or a key pair.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Programmatically:
For each SSO user <username> with a password, run the following command to set password to null :
ALTER USER <username>
SET PASSWORD = NULL;
If your IdP configuration automatically generates passwords for SCIM-managed users, consider disabling this functionality such that new SCIM-managed users will not have passwords generated by default.
Impact:
Users will not be able to sign into their Snowflake accounts if SSO sign-in flow breaks, for example due to SSO provider outage.