Skip to main content

πŸ” 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)

AreaWhat It ProtectsManaged By
Account-Level SecurityUser identity, authentication, permissionsSnowflake Admins, IAM Team
Network-Level SecurityIPs, connectivity, private routing, TLSInfra & Network Security Teams

🎯 Summary Table

AreaControlsExample Purpose
Account-Level SecurityMFA, SSO, Key-Pair, OAuth, RBAC, Timeout, AuditsControls who logs in & what they can do
Network-Level SecurityIP Policies, CIDR, PrivateLink, TLS, FirewallsControls 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).