Skip to content

The 34 Snowflake security checks Black Cat runs

Black Cat SSPM evaluates 34 security policies against your Snowflake configuration on every scan, classifies each finding by risk, and provides remediation steps. Browse them by topic below.

How to connect Snowflake — what access Black Cat needs, and why.

Access control & privilege (11)

Data sharing & exposure (6)

Network security (4)

Configuration hardening (10)

Other checks (3)

severity: critical MFA Not Enabled fix difficulty: easy #

Enable MFA for the Snowflake user account

  1. Navigate to Snowsight at https://app.snowflake.com and sign in as ACCOUNTADMIN or USERADMIN
  2. Go to Admin > Users & Roles > Users and select the flagged user
  3. Click Edit and enable multi-factor authentication (MFA) enrollment for the user
  4. Alternatively, enforce MFA via an authentication policy — run: CREATE AUTHENTICATION POLICY require_mfa MFA_AUTHENTICATION_METHODS = ('TOTP') MFA_ENROLLMENT = REQUIRED;
  5. Attach the policy to the user: ALTER USER <username> SET AUTHENTICATION POLICY require_mfa;
  6. Verify the change: SHOW USERS LIKE '<username>';

Vendor docs ↗

Satisfies: ISO 27001:2022 A.8.5 SOC 2 Type II CC6.1 CIS Controls v8 CIS-06.3 NIST CSF 2.0 PR.AA-03 GDPR (SaaS Security) GDPR-32.1b.i HIPAA (SaaS Security) HIPAA-312.d NIS2 Directive NIS2-21.j DORA (SaaS Security) DORA-9.4

severity: critical Authentication Policy No MFA fix difficulty: easy #

Update the authentication policy to require MFA for all users

  1. Connect to Snowflake as ACCOUNTADMIN or SECURITYADMIN
  2. Identify the authentication policy: SHOW AUTHENTICATION POLICIES;
  3. Alter the policy to require MFA: ALTER AUTHENTICATION POLICY <policy_name> SET MFA_AUTHENTICATION_METHODS = ('TOTP') MFA_ENROLLMENT = REQUIRED;
  4. Verify the updated policy: DESCRIBE AUTHENTICATION POLICY <policy_name>;
  5. Ensure the policy is applied to the account or specific users/roles as intended
  6. Communicate the MFA requirement to affected users and provide enrollment instructions

Vendor docs ↗

Satisfies: ISO 27001:2022 A.8.5 SOC 2 Type II CC6.1 CIS Controls v8 CIS-06.3 NIST CSF 2.0 PR.AA-03 GDPR (SaaS Security) GDPR-32.1b.i HIPAA (SaaS Security) HIPAA-312.d NIS2 Directive NIS2-21.j DORA (SaaS Security) DORA-9.4

severity: medium Data Rekeying Disabled fix difficulty: easy #

Enable periodic data rekeying to ensure encryption keys are regularly rotated

  1. Connect to Snowflake as ACCOUNTADMIN
  2. Enable periodic rekeying: ALTER ACCOUNT SET PERIODIC_DATA_REKEYING = TRUE;
  3. Verify the setting: SHOW PARAMETERS LIKE 'PERIODIC_DATA_REKEYING' IN ACCOUNT;
  4. Note that rekeying runs in the background and may take time depending on data volume
  5. For enhanced key management, consider Snowflake Tri-Secret Secure with a customer-managed key
  6. Review your encryption key rotation policy and document the rekeying schedule

Vendor docs ↗

Satisfies: ISO 27001:2022 A.8.24 SOC 2 Type II CC6.1 CIS Controls v8 CIS-03.10 NIST CSF 2.0 PR.DS-02 GDPR (SaaS Security) GDPR-5.1f.ii GDPR (SaaS Security) GDPR-32.1a HIPAA (SaaS Security) HIPAA-312.e NIS2 Directive NIS2-21.h DORA (SaaS Security) DORA-9.7

The information on this page is provided for general informational purposes and is believed to be accurate as of its most recent update. Product names, logos, and trademarks are the property of their respective owners and are used for identification purposes only; their use does not imply any affiliation with or endorsement by those owners. Descriptions of third-party applications and of compliance frameworks are based on publicly available documentation and may change over time.

See these checks run on your stack

Start a free 14-day trial — no credit card required.

Start Free Trial