How to Configure Snowflake Password Policy
You set up a snowflake password policy by creating a schema rule and attaching it to your account. You can also attach a specific rule to individual user identities. Teams often apply one global rule across the entire platform. Still, broad permissions let too many admins alter or bypass these login rules. Overly broad roles also expose data once a user logs in. How a snowflake password policy works A snowflake password policy is a schema-level object that sets login string rules. Security ad
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You set up a snowflake password policy by creating a schema rule and attaching it to your account. You can also attach a specific rule to individual user identities. Teams often apply one global rule across the entire platform. Still, broad permissions let too many admins alter or bypass these login rules. Overly broad roles also expose data once a user logs in.
How a snowflake password policy works
A snowflake password policy is a schema-level object that sets login string rules. Security admins define minimum length, character mix, and age limits inside this object. The rule also controls how many failed attempts trigger a temporary lockout. Admins can set a lockout timer to slow down brute-force attacks. Password history rules stop users from reusing old strings during a reset.
After you create the policy object, you assign it at the account level. Every user in that account must follow the rule on their next change. Some service accounts or apps need different rules than human users. For those cases, admins attach a separate rule straight to the user object. A user-level rule always overrides the global account rule in Snowflake. Only roles with specific ownership or security rights should manage these objects.
Managing user roles and policy scope
Good password setup starts with strict role separation inside your data platform. You should separate the role that creates rules from the role that assigns them. If a standard admin role owns the rule, that admin can weaken it. Teams must audit which roles hold ownership over the schema containing the rule.
Many teams pair password rules with multi-factor checks for human users. Service accounts often switch to key pairs or external identity tools instead. Even during that migration, a fallback password rule protects any remaining static logins. Regular checks on account usage views help teams spot users without strong rules.
Application-to-Application Password Management + Snowflake Access Control: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native login rules leave open
Native password rules solve one specific problem. They make sure users pick strong strings and rotate them on time. This stops simple guessing attacks at the permissions door of your data platform.
Still, a password rule only checks who logs into a session. It does not inspect or control what SQL queries run during that session. Once a user passes the login check, their active role dictates all permissions. If an engineer or an automated app holds a wide role, risks remain high. A valid user can still run a broad query that pulls sensitive rows. They can read raw emails, phone numbers, card numbers, or national IDs. Native login rules also cannot require live human approval before a destructive command runs. Protecting data in flight requires controls that inspect queries and rewrite results dynamically.
Check database and API queries on the wire
Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.
Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.
Frequently asked questions
Does a user policy override an account policy?
Yes, a rule attached to a user overrides the global account rule. This lets teams enforce stricter rules for admins or special accounts.
Do new password rules force an immediate reset for active users?
No, existing passwords remain valid until their current age limit runs out. The platform enforces the new character rules on the next password change.
Can password rules mask sensitive data in query results?
No, password rules only check login strings when a session starts. To rewrite emails or card numbers in results, you need query-level masking controls.
Related guides
In this post