What you will be able to do
- Enable and schedule Trust Center scanner packages, including CIS Benchmarks, as recurring compliance audit checks
- Manage violation and detection findings so their history stands up as audit evidence
- Produce compliance evidence from the posture report and obtain Snowflake's own reports from the Compliance Center
1.Scanner packages as recurring audit checks
The Trust Center is Snowflake's built-in posture checker. It is the quickest way to turn a compliance requirement into a check that runs on its own. It tests each account against recommendations written into scanners, which are background processes grouped into scanner packages. Turning on a package is how you define an audit policy. Its schedule is how you automate it. And a regulator's or framework's expectation becomes a finding when the account drifts from it.
The packages differ in how they are switched on and what they cost:
- Security Essentials is always on, cannot be deactivated, and runs on a fixed schedule with no serverless compute charge. Any additional run you trigger is billed. It checks for an MFA-enforcing authentication policy, MFA enrollment of password users, and an account-level network policy, and it scans human users only.
- CIS Benchmarks evaluates the account against the Center for Internet Security Snowflake Benchmarks. It is off by default, runs once a day once enabled, and its schedule can be changed.
- Threat Intelligence contains the event-driven scanners that look for anomalous activity, such as sign-ins from unusual IP addresses.
- AI Security watches AI-related configuration. Snowflake can turn it on automatically for Business Critical and VPS accounts with a capacity contract.
Enabling a package needs a role granted the SNOWFLAKE.TRUST_CENTER_ADMIN application role. In Snowsight, go to Governance & security » Trust Center, choose a warehouse, open Scanner Packages, select the package and choose Enable. The package runs immediately, regardless of its schedule. You can then turn individual scanners on or off and give them their own schedules. Every package's schedule can be changed except Security Essentials. Run Package triggers an on-demand run, which is useful the day before an audit.
Scheduled and event-driven scanners catch different things. A scheduled scanner that checks a Boolean parameter every 10 minutes misses it being switched off and back on between runs. An event-driven scanner reports each change, and the Trust Center surfaces those detections within an hour of the event. Where a regulation cares about every change to a sensitive setting, rather than its state at check time, enable the Threat Intelligence package. To act on custom checks beyond the scanners, such as a query against access history, schedule them with Snowflake alerts and notification integrations so drift raises a notification.
Checkpoint 1 of 4· Check yourself
A compliance requirement says every change to a sensitive Boolean account parameter must be recorded, including one that is switched off and back on within minutes. A scheduled scanner already checks the parameter every 10 minutes. Which Trust Center approach meets the requirement?
A scheduled scanner sees only the configuration as it is when it runs, so a setting that is turned off and back on between runs is never reported. Event-driven scanners in Threat Intelligence report each event as its own detection. Security Essentials checks only MFA and network policies, and running it more often or on demand still checks only the state at that moment.
“Scanners report each detection based on an event trigger.”Source: docs.snowflake.com
2.Violations, detections and an auditable finding history
Findings come in two kinds, and only one of them has a lifecycle you can manage. A violation is a configuration that currently fails a scanner's requirement, for example password users without MFA. It keeps being reported until the configuration changes. A detection is a one-off event, such as a sign-in from an unrecognised IP address or a large transfer to an external stage. It happened in the past, so it cannot be remediated, and its lifecycle cannot be managed. You investigate it and change controls so a similar event cannot happen again.
The Violations tab is where the audit trail is built. There you can triage violations, record evidence or progress notes, and resolve or reopen a violation with a written justification. Each status change carries a reason, so a later reviewer can see what was decided and why. Violations can be sorted by low, medium, high and critical severity, and by scanner package, version, time and status, and each one carries remediation guidance.
Resolving a violation is not the same as fixing it. Marking it Resolved suppresses its email notifications while you work on the misconfiguration. The configuration stays non-compliant until it is actually changed and a scanner run confirms it. The Organization tab, which needs the ORGANIZATION_SECURITY_VIEWER application role in the organization account, shows violation counts across every account. It does not show detections, and you cannot resolve or reopen anything from it. That is done by signing in to the account that has the violation.
Checkpoint 2 of 4· Check yourself
The day before an audit, an admin marks every open MFA violation in the Violations tab as Resolved and writes a justification for each. No user or authentication-policy settings are changed. What has this achieved?
Setting a violation to Resolved changes its status and suppresses its email notifications. Only changing the configuration fixes it, and a later scanner run confirms the fix. The lifecycle you can manage belongs to violations, not detections.
“Email notifications are suppressed for resolved violations. Suppression prevents more notifications while you work to remediate the underlying misconfigurations.”Source: docs.snowflake.com
Sources1
3.What a clean CIS Benchmarks result proves
CIS Benchmark violations map straight to a framework an assessor already knows. The Trust Center shows the CIS section number, such as 1.1, against each violation, so a finding can be cited by benchmark reference in an audit workpaper. CIS checks such as limiting how many users hold ACCOUNTADMIN and SECURITYADMIN, disabling users who have not logged in for 90 days, and keeping tasks off those admin roles each turn into a remediation item with guidance.
For several benchmarks, Snowflake only checks that a control exists, not that it works. Three examples show the gap:
- 3.1 raises a violation when there is no account-level network policy, but it does not check which IP addresses the policy allows.
- 4.3 checks that DATA_RETENTION_TIME_IN_DAYS is 90 for the account or at least one object, but it does not judge which data is critical.
- 4.10 passes if at least one masking policy exists, even one assigned to no table or view.
A clean 4.10 therefore says nothing about whether PHI or cardholder columns are masked. That evidence has to come from POLICY_REFERENCES.
Section 2 checks monitoring, and it does so by checking other scanners. Each Section 2 scanner confirms that the matching Threat Intelligence or Security Essentials scanner is enabled and has produced findings in the last 90 days. If it has not, the Trust Center raises a finding naming the missing alerting control. In practice, most Section 2 benchmarks pass only once Threat Intelligence is enabled. Benchmark 2.9, on vulnerable driver versions, relies on the always-on Security Essentials client-security scanner.
Checkpoint 3 of 4· Check yourself
A PCI assessor asks for proof that the card-number columns in one payments table are masked. The Trust Center shows no violation for CIS benchmark 4.10. What should you hand over as evidence?
CIS 4.10 passes as long as one masking policy exists anywhere, even if it is assigned to no table or view, so a clean result says nothing about specific columns. Only per-column records, such as POLICY_REFERENCES or the policies_referenced column in ACCESS_HISTORY, show that those columns are actually protected.
“a column protected by a masking policy, Snowflake records the policy information in the policies_referenced column”Source: docs.snowflake.com
Sources1
4.Producing evidence: posture reports and the Compliance Center
Auditors need to see controls that pass, not only open risks, and the account posture report shows both. On the Trust Center Overview tab, the Account posture section summarises a period you choose (28 days by default) and generates a PDF. Any role with SNOWFLAKE.TRUST_CENTER_VIEWER or SNOWFLAKE.TRUST_CENTER_ADMIN can produce it. Scanners that ran clean are listed alongside open findings, so a reviewer can see which checks the account satisfies. Violations are grouped as newly opened, remediated, increased, decreased, unchanged or muted, which shows progress over the period rather than a single count.
| Report section | Audit question it answers |
|---|---|
| Scanner enablement | Which first-party scanners and packages were switched on? |
| Scanner activity in period | Did the checks actually run, and how many found no at-risk entities? |
| Configuration changes | Who enabled or disabled a package, and what triage (mute, unmute, comments) happened? |
| Violation findings activity in period | Which violations opened, were remediated, or were muted? |
| Detection findings activity in period | Which events were detected, and which scanners ran clean? |
| Scanner status | What is each scanner's schedule and last run? |
The PDF is a self-contained, point-in-time record with all timestamps in UTC, so you can give it to an auditor who has no account access. Its Configuration changes section has limits. It covers the latest enable or disable per package and triage activity, but not schedule edits, notification-setting changes or individual scanner toggles. For those, query the account's query history.
Evidence about Snowflake itself comes from Snowflake. The SOC 2 Type II report is an independent auditor's attestation of how Snowflake's security, availability and confidentiality controls were designed and how well they operated over the coverage period. You request it through the Snowflake Compliance Center. The PCI DSS Attestation of Compliance is also available on request. Put together, the audit pack has three layers. Snowflake's attestations cover the platform, the posture report covers your account's configuration, and access-history queries cover what users did with the data.
Checkpoint 4 of 4· Match them up
An auditor sends four evidence requests. Match each request to the source that answers it.
Tap a term, then the definition that fits it.
Snowflake's attestations cover the platform, the posture report covers your account's Trust Center configuration and findings, and ACCESS_HISTORY covers what users did with the data. The posture report's Configuration changes section leaves out schedule edits, so you have to find out who changed a schedule from query history.
“schedule updates, or notification-setting changes. To see who made other configuration changes, review your account’s query history.”Source: docs.snowflake.com
Sources
(5)
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.
“The Trust Center evaluates each Snowflake account against recommendations that are specified in scanners.”
↩︎ Scanner packages as recurring audit checks“Scanner packages are deactivated by default, except for the Security Essentials scanner package.”
↩︎ Scanner packages as recurring audit checks“This scanner package runs once a day by default, but you can change the schedule.”
↩︎ Scanner packages as recurring audit checks“After you enable a scanner package, the scanner package runs immediately, regardless of the configured schedule.”
↩︎ Scanner packages as recurring audit checks“The Trust Center reports detections that are generated by event-driven scanners within an hour of the time that an event occurs.”
↩︎ Scanner packages as recurring audit checks“A detection occurs one time and represents a unique event.”
↩︎ Violations, detections and an auditable finding history“Resolve or reopen violations for any reason and record justification for audit needs.”
↩︎ Violations, detections and an auditable finding history“Use a role that has the ORGANIZATION_SECURITY_VIEWER application role.”
↩︎ Violations, detections and an auditable finding history“the Trust Center provides section numbers for each violation if you want to reference the Snowflake CIS Benchmarks”
↩︎ What a clean CIS Benchmarks result proves“the absence of a violation does not guarantee that the security measure is implemented in an effective manner”
↩︎ What a clean CIS Benchmarks result proves“is enabled and has produced findings within the last 90 days”
↩︎ What a clean CIS Benchmarks result proves“Trust Center displays a violation if the account does not have at least one masking policy”
↩︎ Exam trap 1“Email notifications are suppressed for resolved violations.”
↩︎ Exam trap 2“Scanners report each detection based on an event trigger.”
↩︎ Checkpoint“the violation still appears in the Violations tab until the next scheduled run of the scanner package”
↩︎ Prediction“Email notifications are suppressed for resolved violations. Suppression prevents more notifications while you work to remediate the underlying misconfigurations.”
↩︎ Checkpoint - 2.
“You can change the schedule for all scanner packages, except the Security Essentials scanner package.”
↩︎ Scanner packages as recurring audit checks“Scanners that ran clean during the period are reported alongside open findings, so a reviewer can see which checks your account satisfies.”
↩︎ Producing evidence: posture reports and the Compliance Center“The PDF is a self-contained, point-in-time record of the period you select”
↩︎ Producing evidence: posture reports and the Compliance Center“violation triage activity (mute, unmute, comments) within the reporting period”
↩︎ Producing evidence: posture reports and the Compliance Center“schedule updates, or notification-setting changes. To see who made other configuration changes, review your account’s query history.”
↩︎ Checkpoint - 3.https://docs.snowflake.com/en/user-guide/cert-soc-2Official docs
“For information about requesting a copy of the report, see the Snowflake Compliance Center.”
↩︎ Producing evidence: posture reports and the Compliance Center - 4.
“The AoC (Attestation of Compliance) is available upon request.”
↩︎ Producing evidence: posture reports and the Compliance Center
Also cited
“a column protected by a masking policy, Snowflake records the policy information in the policies_referenced column”
↩︎ Checkpoint