π Account-Level & Network-Level Security in Snowflake
Snowflake provides strong enterprise-grade security across two core pillars:
-
Account-Level Security β Managed in the Cloud Services Layer (Application Layer)
Controls who can access Snowflake and how they authenticate. -
Network-Level Security β Managed in the Network & Connectivity Layer
Controls from where Snowflake can be accessed and how network traffic flows.
This separation helps ensure protection for users, identity, network paths, and data-in-transit, while supporting compliance and governance.
π‘ 1. Account-Level Security
β Managed Byβ
- Snowflake Admins (SECURITYADMIN / SYSADMIN)
- Identity & Access Management (IAM) Team
- Enterprise Security Team
β Layerβ
- Cloud Services Layer (Application Layer)
β Authentication, Authorization, RBAC, Policies, Metadata
Account-level security protects authentication, user identity, access control, and session behavior within Snowflake.
π Multi-Factor Authentication (MFA)β
What: Adds OTP/app-based second authentication factor.
When to Use: Prevent unauthorized access even if passwords leak.
Real-world scenarios:
- Finance companies enforcing MFA for all user logins
- Healthcare orgs protecting PHI access
- Admin/Privileged roles requiring MFA by policy
How: Enable MFA in Snowflake β Users register using Google Authenticator or similar.
π Single Sign-On (SSO) with SAMLβ
What: Centralized authentication via IdPs like Okta, Azure AD, Ping Identity.
When to Use: Enterprise-wide unified login & auto user lifecycle management.
Real-world scenarios:
- Retail org integrating Snowflake with Okta
- Enterprises linking Snowflake with Azure AD onboarding/offboarding
- Insurance firms centralizing password policy controls
How: Configure SAML settings β Upload IdP metadata β Map roles.
π Key Pair Authenticationβ
What: Public-private RSA key pair for passwordless access.
When to Use: ETL/ELT pipelines, DevOps, Airflow, CI/CD.
Real-world scenarios:
- DevOps pipelines running Snowflake scripts securely
- Airflow jobs using private keys instead of passwords
- Third-party apps integrating programmatically
How: Generate RSA keys β Store public key in user profile β Use private key in scripts.
π OAuth Integrationβ
What: Token-based delegated access without passwords.
When to Use: BI tools and applications requiring short-lived secure tokens.
Real-world scenarios:
- Tableau / Power BI dashboards using OAuth tokens
- Internal applications querying Snowflake on behalf of users
- Marketing analytics tools integrating securely
How: Create OAuth Security Integration β Configure client credentials.
π₯ User, Roles & Access Control (RBAC)β
What: Fine-grained access control using roles, grants, and privileges.
When to Use: AlwaysβSnowflake is fully RBAC-driven.
Managed By: SECURITYADMIN role.
β³ Session Management Policiesβ
Session Timeoutβ
What: Logs out inactive sessions automatically.
When to Use: Compliance requirement for PCI, HIPAA, SOC2.
Real-world scenarios:
- 30-minute inactivity timeout
- Logging off analysts on shared workstations
How: Set SESSION TIMEOUT at account/user level.
π Federated Authentication (IdP Integration)β
What: Authentication handled entirely by Okta/Azure AD.
When to Use: Central role provisioning & automated user lifecycle.
Real-world scenarios:
- Organizations using Azure AD for all cloud apps
- HR-driven provisioning/deprovisioning
How: Configure SAML in Snowflake β Exchange metadata with IdP.
π Monitoring & Auditingβ
Login Historyβ
Track successful/failed logins to detect suspicious locations.
Query Historyβ
Audit access to sensitive tables and high-risk activity.
Real-world scenarios:
- Monitoring PII access for GDPR
- Investigating abnormal login attempts
- SOC2/ISO27001 auditing
How: Query ACCOUNT_USAGE.LOGIN_HISTORY and QUERY_HISTORY.
π 2. Network-Level Security
β Managed Byβ
- Cloud Infrastructure Team (AWS/Azure/GCP)
- Network Security Team
- Snowflake Admins (for creating network policies)
β Layerβ
- Network Layer Security
β IP filtering, private connectivity, TLS, firewall routing
This layer controls where Snowflake can be accessed from and how network traffic reaches Snowflake.
π‘ IP Whitelisting (Network Policies)β
What: Restrict Snowflake access to trusted IPs or VPN ranges.
When to Use: Corporate office, VPN users, government or regulated environments.
Real-world scenarios:
- Healthcare restricting access to VPN IP ranges
- Finance restricting to office subnet
- Remote staff needing secure VPN tunnel
How:
CREATE NETWORK POLICY my_policy
ALLOWED_IP_LIST = ('<your_ip>/32');
ALTER ACCOUNT SET NETWORK_POLICY = my_policy;
π’ CIDR-Based Access Controlβ
What: Manage IP ranges using CIDR notation.
/32β exact IP/24β 256 IPs/16β 65K IPs
Real-world scenarios:
- Allowing all branch office subnets
- Country/region-specific access (US/EU/APAC)
- University campus network restrictions
π Private Connectivity (No Public Internet)β
What: Private, secure connectivity between cloud VPC/VNet and Snowflake.
Options:
- AWS PrivateLink
- Azure Private Link
- GCP Private Service Connect
Real-world scenarios:
- Banks avoiding public internet traffic
- Healthcare ensuring PHI is securely transferred
- Fintech apps needing low-latency secure connectivity
How: Configure PrivateLink endpoints β Link to Snowflake account.
π TLS Encryption in Transitβ
What: TLS 1.2+ encrypts traffic between client and Snowflake.
Real-world scenarios:
- Users connecting via public Wi-Fi
- Corporate tools requiring encrypted traffic
- Compliance enforcement
How: TLS is always enabled by default.
π₯ Additional Network Controlsβ
Firewall / Proxy Rulesβ
Corporate network teams may restrict outbound access pathways.
Routing & Connectivity Securityβ
Ensures only approved pipelines and tools can reach Snowflake endpoints.
π Who Manages What? (Quick Reference)
| Area | What It Protects | Managed By |
|---|---|---|
| Account-Level Security | User identity, authentication, permissions | Snowflake Admins, IAM Team |
| Network-Level Security | IPs, connectivity, private routing, TLS | Infra & Network Security Teams |
π― Summary Table
| Area | Controls | Example Purpose |
|---|---|---|
| Account-Level Security | MFA, SSO, Key-Pair, OAuth, RBAC, Timeout, Audits | Controls who logs in & what they can do |
| Network-Level Security | IP Policies, CIDR, PrivateLink, TLS, Firewalls | Controls from where & how they access |
β One-Line Summary
Account-Level Security = Identity & Access Control (Cloud Services Layer). Network-Level Security = IP, Connectivity & Traffic Control (Network Layer).