Network Policies & MFA
Snowflake · Advanced Security & Governance
Theory
RBAC controls what a user can do after logging in; network policies and authentication controls decide who can log in at all. A network policy lists allowed and blocked IP addresses (newer setups reference network rules) and can be set on the account or on individual users, with a user-level policy taking priority over the account one. Connections from addresses that are not allowed are rejected.
Multi-factor authentication adds a second factor such as a passkey, an authenticator app code or Duo, and Snowflake is making it mandatory for password sign-ins by people. Stronger options avoid passwords altogether: key-pair authentication for service users and scripts, and single sign-on through SAML or OAuth with an identity provider such as Okta or Microsoft Entra ID.
Why we use it
Stolen passwords are a common cause of data breaches. Limiting where connections can come from and requiring strong authentication means a leaked password alone is not enough to reach the data.
When to use it
Apply an account-level network policy for known office, VPN and tool IP ranges, use SSO with MFA for people and key pairs for service users. Test a new account-level policy on a single user first so you do not lock yourself out.
Network Policies (IP Allowlisting)
A network policy defines allowed (and optionally blocked) IP ranges; attached to the account or a specific user, it rejects login attempts from outside the allowed list before credentials are even checked.
Multi-Factor Authentication
Snowflake MFA supports passkeys (recommended), authenticator apps that generate one-time codes, and Duo. Snowflake is rolling out mandatory MFA for every password sign-in by human users, and authentication policies let admins control which methods are allowed. Service users cannot use MFA and should use key-pair or OAuth instead.
SSO, SAML & OAuth
For enterprise accounts, federated authentication through SAML or OAuth lets users log in with their existing corporate identity provider, centralizing access control outside Snowflake itself.
How it works
- Login attempt
- Is the client IP allowed by the user's or account's network policy? Yes: Continue to authentication. No: Reject the connection.
- Authenticate: SSO, key pair or password
- Is MFA required for this user? Yes: Verify the second factor. No: Create the session.
- Session starts with the user's default role
Example
CREATE OR REPLACE NETWORK POLICY office_only_policy
ALLOWED_IP_LIST = ('203.0.113.0/24')
BLOCKED_IP_LIST = ('203.0.113.99');
ALTER ACCOUNT SET NETWORK_POLICY = office_only_policy;
ALTER USER john_smith SET NETWORK_POLICY = office_only_policy;
SELECT NAME, HAS_MFA_TOKEN FROM SNOWFLAKE.ACCOUNT_USAGE.USERS WHERE DELETED_ON IS NULL;Key points
- Network policies block by IP before credentials are checked
- A user-level network policy overrides the account-level policy
- MFA options: passkeys (recommended), authenticator apps and Duo
- MFA is becoming mandatory for human password sign-ins
- Use key-pair or OAuth for service users; they cannot use MFA
- Test new account-level policies carefully to avoid locking out admins