Accounts and Security · Topic 10 of 17
Security Principles and Encryption
Apply Snowflake security principles and know encryption: key hierarchy, 30 day rotation, rekeying, Tri-Secret Secure and client-side stage encryption.
- 5 min
- Everything is encrypted at rest and in transit by default, with a four level hierarchy: root, account, table, file keys.
- Keys rotate when 30 days old; rekeying of data older than one year needs Enterprise and
PERIODIC_DATA_REKEYING = TRUE. - Tri-Secret Secure combines a Snowflake key with a customer-managed key and needs Business Critical.
What it is
Snowflake security rests on a few principles that the exam applies to scenarios: defense in depth, least privilege, separation of duties, and encryption of everything by default. An Architect layers controls so that no single failure exposes data.
Encryption is the part with the most testable detail. Snowflake encrypts all customer data at rest and in transit by default, with no setting to turn on and no performance trade-off to manage.
How it works
Security principles and where to apply them
| Principle | How Snowflake supports it | Use case |
|---|---|---|
| Least privilege | Roles, grants, role hierarchy, managed access schemas | Analysts read only the schemas they need |
| Separation of duties | System roles split user management from grant management | USERADMIN creates users, SECURITYADMIN manages grants |
| Defense in depth | Network policy, authentication policy, MFA, masking, encryption | Stolen password alone cannot read data |
| Data minimization | Masking, row access, secure views, secure data sharing | Share a filtered view instead of copying data |
| Strong identity | SSO, MFA, key-pair, OAuth | Humans use SSO with MFA, services use key-pair |
| Auditability | ACCESS_HISTORY, LOGIN_HISTORY, QUERY_HISTORY views | Show who read a sensitive column |
Avoid ACCOUNTADMIN for daily work. Give it to few people, require MFA for it, and do not make it a default role.
Encryption in transit and at rest
Data in transit is protected with TLS between clients and Snowflake. Data at rest, including table data, internal stage files and query results, is encrypted with AES.
Files uploaded to an internal stage are encrypted by the client before they leave the machine and stay encrypted in the stage. Snowflake decrypts data only inside its secure processing layers, while the data is being processed.
The key hierarchy
Snowflake uses a hierarchical key model with four levels. Each level wraps the keys below it.
The root key is held in a cloud hardware security module (HSM). Account master keys are specific to each account, so one customer's keys never touch another's.
Key rotation and rekeying
Key rotation happens automatically: a key older than 30 days is retired and a new key encrypts new data. A retired key is kept only to decrypt data it already protected. Rotation needs no action and is on in every edition.
Periodic rekeying goes further. When a retired key is more than one year old, Snowflake creates a new key and re-encrypts the data that the old key protected. It needs Enterprise or higher and is enabled by an ACCOUNTADMIN:
ALTER ACCOUNT SET PERIODIC_DATA_REKEYING = TRUE;
Rekeyed files generate seven days of Fail-safe storage, so rekeying has a storage cost. Time Travel and Fail-safe periods themselves do not change.
Tri-Secret Secure
Tri-Secret Secure lets the customer hold part of the key. A Snowflake-maintained key is combined with a customer-managed key to form a composite master key that protects the data.
The customer-managed key lives in the customer's own AWS KMS, Azure Key Vault or Google Cloud KMS. It requires Business Critical or higher.
| Event | Result |
|---|---|
| Customer key unavailable for a short time | Snowflake tolerates it for up to 10 minutes |
| Key still unavailable after that | Data operations in the account stop until access is restored |
| Customer key deleted or destroyed | Data cannot be decrypted |
Revoking or deleting a customer-managed key is a kill switch. It stops all operations, and a destroyed key makes the data unreadable. Do not delete old key versions after rotation.
Client-side encryption for external stages
For external stages the customer may encrypt files before they reach cloud storage. The stage definition carries a MASTER_KEY (a 128 bit or 256 bit AES key, Base64 encoded) with TYPE = 'AWS_CSE' or the matching setting for Azure. The client creates a random key per file and encrypts that key with the master key.
Files in an internal stage already use Snowflake managed client-side encryption, and you cannot supply your own key for them.
Common mistakes
Believing encryption must be enabled. It is always on. The decisions are about who controls the keys (Tri-Secret Secure) and how often data is rekeyed.
Mixing up rotation and rekeying. Rotation is automatic every 30 days for keys, in every edition. Rekeying of old data after a year needs Enterprise and the PERIODIC_DATA_REKEYING parameter.
Choosing Tri-Secret Secure on Enterprise. It needs Business Critical or higher.
Treating encryption as the only control. Encryption does not stop an authorized role from reading data. Masking and RBAC do.
What to remember for the exam
- Everything is encrypted at rest and in transit by default, with a four level hierarchy: root, account, table, file keys.
- Keys rotate when 30 days old; rekeying of data older than one year needs Enterprise and
PERIODIC_DATA_REKEYING = TRUE. - Tri-Secret Secure combines a Snowflake key with a customer-managed key and needs Business Critical.
- If the customer key is unavailable beyond about 10 minutes, data operations stop.
- Least privilege, separation of duties and defense in depth are the principles behind most correct answers.
Check yourself
Which feature gives the customer control over part of the encryption key?
Tri-Secret Secure, which combines a Snowflake key and a customer-managed key into a composite master key. It needs Business Critical or higher.
How often are keys rotated, and what extra step needs Enterprise?
Keys are rotated when they reach 30 days of age in all editions. Rekeying data protected by retired keys older than one year needs Enterprise and
PERIODIC_DATA_REKEYING.What happens when a Tri-Secret Secure customer key stays unavailable for more than about 10 minutes?
Data operations in the account stop until access to the key is restored.
Topic 10 of 17 in Accounts and Security
Test yourself on Accounts and Security
The full Snowflake ARA-C01 question bank has 687 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.