What you will be able to do
- Explain which app distribution settings and release-channel actions trigger the NAAAPS automated security scan
- Read a version's review status and know when a provider can set a release directive
- Apply the code, dependency, functionality and privilege requirements an app must meet to pass review
- Describe how rejections, appeals, continuous monitoring and the extra container approval work
Key concept
Native App Anti-Abuse Pipeline Service (NAAAPS) — NAAAPS is Snowflake's automated scanner. It checks every new version or patch of an externally distributed Native App for vulnerable code, malware and risky dependencies before consumers outside the provider's organization can install it. If the scan doesn't approve the version, a manual review decides.
1.Why provider code is reviewed before consumers run it
A Snowflake Native App is provider-written code that runs inside the consumer's account, close to the consumer's data. That trust model creates four risks. A malicious app could copy consumer data into external functions or logs. It could run unauthorized work such as cryptomining, at the consumer's expense. It could encrypt or corrupt data and demand a ransom. Or it could try to gain permissions it was never granted. Any of these would hurt the consumer without the consumer ever seeing the source.
Snowflake's answer is a security review that every published app must pass. NAAAPS runs the automated part: it copies the app into a dedicated scanning account, scans the app's files, and then either approves the app automatically or sends it to manual review. The scanners look for bugs, anti-patterns and vulnerabilities in the code. They also look for malware and for vulnerabilities in the app's dependencies. Together they target data exfiltration, ransomware, compute abuse, privilege escalation and dynamic code execution.
The scan runs in a region tied to the provider's region. On AWS, each listed provider region is scanned in that same region. Azure and GCP provider regions are grouped into a few scanning regions; for example, GCP US Central1 is scanned in AWS US West (Oregon). This matters for residency reviews, because setting a package for external sharing automatically shares the app's code with Snowflake for scanning.
Checkpoint 1 of 7· Check yourself
Your company is about to install a Snowflake Native App from an external provider, and the app has passed Snowflake's security review. A colleague says: "Snowflake already scanned it, so we can install it and grant whatever it asks for without our own review." How should you respond?
Snowflake's review lowers the risk of exfiltration, compute abuse, ransomware and privilege escalation, but the consumer is still responsible for their own checks. Snowflake tells consumers to review what the app can access and do against their own standards. Consumers don't run NAAAPS themselves; it runs in a dedicated Snowflake scanning account.
“consumers should independently review the permissions, access, and functionality of the provider’s app to ensure it meets their security requirements and standards”Source: docs.snowflake.com
Sources1
2.How DISTRIBUTION and release channels trigger the scan
The DISTRIBUTION property on the application package decides whether NAAAPS runs. INTERNAL lets the provider create only private listings inside its own organization, and no scan runs. EXTERNAL allows private listings outside the organization, public listings and Marketplace listings, and every one of those depends on the scan.
ALTER APPLICATION PACKAGE hello_snowflake_package
SET DISTRIBUTION = EXTERNAL;Without release channels, the scan starts in one of two ways. Either the provider adds a version or patch to a package that is already EXTERNAL, or it sets EXTERNAL on a package that already has versions. With release channels enabled, adding a version to the ALPHA or DEFAULT channel starts the scan on the 10 most recent patches of that version. Adding a version only to the QA channel does not start a scan.
The order of a release matters. The provider adds the version, waits for the scan, and only then sets the release directive and creates the listing. The listing itself is submitted to Snowflake for a separate approval before it can be published. SHOW VERSIONS IN APPLICATION PACKAGE shows each version's progress in the review_status column. In Snowsight, the same status appears as Security Scan Status under Projects » App packages.
| review_status | Meaning | What the provider can do next |
|---|---|---|
| NOT_REVIEWED | The automated scan has not been performed | Trigger a scan through EXTERNAL distribution or a release channel |
| IN_PROGRESS | The automated scan is running | Wait for the result |
| APPROVED | The scan completed and the package was approved | Set the release directive and continue publishing |
| REJECTED | The scan completed but the package was not approved | Fix the code based on the reason shown, or appeal |
Because each external version is scanned, Snowflake recommends using two packages. A development package stays INTERNAL, so developers can iterate quickly without a review on every change. A production package is EXTERNAL and receives only versions that have already passed the provider's own security review.
Checkpoint 2 of 7· Fill the gap
A provider has been building in an application package that already holds several versions. They now want to publish the app as a Snowflake Marketplace listing for consumers in other organizations. Which value completes the statement they need to run?
ALTER APPLICATION PACKAGE hello_snowflake_package
SET DISTRIBUTION = ? ;Only EXTERNAL allows listings outside the provider's organization, including Marketplace listings. Setting it on a package that already has versions sends the 10 most recent patches of each version to the security scan. INTERNAL allows only private listings inside the organization and skips the scan. PUBLIC and MARKETPLACE are not valid DISTRIBUTION values.
Source: docs.snowflake.comCheckpoint 3 of 7· Check yourself
An EXTERNAL application package has release channels enabled. A provider adds a new version to the QA channel only and runs SHOW VERSIONS IN APPLICATION PACKAGE the next day. What will the review_status column most likely show for that version?
With release channels enabled, the scan starts only when a version is added to the ALPHA or DEFAULT channel. A version that is only in QA is never sent to NAAAPS, so it stays NOT_REVIEWED.
“Adding a version only to the QA release channel does not initiate the security scan.”Source: docs.snowflake.com
Checkpoint 4 of 7· Exam question
A provider wants to publish a Native App on the Snowflake Marketplace for consumers outside its organization. Which sequence correctly gets a new version through the mandatory security review?
Correct answer: B — Set DISTRIBUTION = EXTERNAL on the application package, add the version, and wait for the scan to approve it before setting a release directive on it
- A. This is incorrect. Internal distribution is meant for same-organization use and does not publish to outside consumers, and consumers have no command for scanning provider code. The review is run by Snowflake against the provider's version before release.
- B. This is correct. External distribution makes each new version subject to the Native App Anti-Abuse Pipeline Service scan, and the release directive can only point at a version that has passed (automatically or after manual review). Skipping this order leaves the version unpublishable.
- C. This is incorrect. Trust Center scanners evaluate account configuration and do not gate application package versions. The Native App review happens before a version can reach consumers, not after installation.
- D. This is incorrect. MANAGE RELEASES is a provider-side privilege for managing release directives on an application package. Consumers do not approve scan results; Snowflake's pipeline and reviewers do.
3.Code, dependency and privilege rules an app must pass
The first code rule is self-containment. An app must not load or run code from outside its application package, apart from Snowflake-provided libraries. All library dependencies and setup code must be inside the app version. A design that downloads a script at runtime fails, because the scanner can only vouch for code it has seen.
Reviewers must also be able to read the code. Obfuscated code is rejected, and that includes minified JavaScript unless the app ships a source map that recovers the original source. Dependencies with critical or high CVEs must be updated to a secure version where one exists. Snowflake ranks CVEs by risk under its CVE Evaluation Criteria, which apply to every app under review.
The functionality rules cover what the app does at runtime. Consider an app that holds a customer's password as a plain string so it can reach an external API. It fails, because apps must not store or require plain-text customer secrets. Several other rules apply as well:
- Internet traffic must use HTTPS with a valid TLS certificate.
- Every connection to the app, including web UIs and APIs, must first authenticate through a Snowflake-provided method. Any app-specific login comes only after that.
- The app should create no public endpoint that skips Snowflake authentication.
- The listing must disclose every internet endpoint, every external function, any consumer data the app logs or stores, and any use of consumer data to train AI models.
- The manifest must declare every privilege the app needs on all objects, and every API integration, and the app should request only the minimum set.
The recommended practices beyond these rules make a rejection less likely. Review code for vulnerabilities during development, before cutting a version. Review third-party libraries and update them to the latest secure version at least once a quarter. Treat the scan as a final check, not as the first time anyone examines the code.
Checkpoint 5 of 7· Check yourself
Four provider teams are preparing app versions for an EXTERNAL application package. Which design meets Snowflake's security requirements for app code and functionality?
Minified JavaScript counts as obfuscated code unless the app includes a source map that recovers the un-minified code, so this design passes. The other three designs break rules: code loaded from outside the package, a plain-text customer secret, and an endpoint that skips Snowflake authentication.
“it must include a corresponding source map file that can be used to recover the un-minified code”Source: docs.snowflake.com
Sources3
4.Rejections, appeals and monitoring after approval
A failed automated scan is not the final answer, because Snowflake then reviews the package manually. A manual review ends in APPROVED or REJECTED, and Snowflake sends no notification on rejection. The provider has to check the status and open the package to read the reason, which may be a critical vulnerability or a policy violation.
A provider appeals by opening a severity 4 support ticket, and the Snowflake Security team decides. An appeal against a CVE-based rejection must explain why the CVE can't be exploited in this app, and include a reachability analysis if one exists. It must also include a plan to move to the fixed version, or a detailed reason why the vulnerable version can't be updated.
Approval is not permanent. Published Marketplace apps receive periodic image security analysis. If a new vulnerability or policy violation is found, the provider has 30 business days to patch, or can request an exception within 15 days.
Checkpoint 6 of 7· Check yourself
After a manual review, a provider's new app version shows REJECTED. The reason is a high-severity CVE in a bundled library, and the provider believes the vulnerable code path is never reached. What is the correct way to contest the decision?
Providers appeal through a severity 4 support ticket, and a CVE-based appeal must explain why the CVE isn't exploitable and give an update plan or a reason the version can't be updated. Snowflake sends no notification on rejection, so there's no email to reply to. Rescanning doesn't override the review.
“A provider can appeal the rejection by opening a severity 4 support ticket.”Source: docs.snowflake.com
5.Extra review for apps that ship containers
An app with containers runs its own services in the consumer account (the compute model is covered in SPCS compute pools and isolation model). That adds an approval step for the provider before the normal scan. A provider without that approval gets error 093197 when it sets DISTRIBUTION=EXTERNAL on a package with containers. To start the approval, the provider submits a security questionnaire covering its security practices and compliance readiness. Snowflake's Security and Compliance team evaluates the responses and replies by email.
After approval, every version gets the normal app scan plus a scan of its container images, so scan time grows with image count and size. At runtime, each containerized app runs in its own isolated network. External endpoints must be declared in the manifest, and Snowflake monitors egress for suspicious traffic patterns. Recommended hardening includes minimal base images, removing unneeded packages, encrypting traffic between containers and to external systems, logging container activity, and patching images regularly.
| App size | Approximate time to complete scan |
|---|---|
| Five images or fewer / smaller than 40 GB | Less than 8 hours |
| Ten images or fewer / smaller than 70 GB | Less than 24 hours |
| Ten images or more / larger than 70 GB | 2 business days or more |
Checkpoint 7 of 7· Put it in order
Put these steps in order for a provider that has never published an app with containers and now wants to share one with consumers outside its organization.
- 1.The app version undergoes the normal app security scan plus a scan of its container images
- 2.Snowflake's Security and Compliance team evaluates the responses and emails its decision
- 3.Submit the security questionnaire covering the provider's security practices and compliance readiness
- 4.Set DISTRIBUTION = EXTERNAL on the application package and receive error 093197
An app with containers needs the provider to be approved first. Without that approval, setting EXTERNAL fails with error 093197, and the questionnaire starts the approval process. The automated scan, which now also covers the container images, runs only after the provider is approved.
“This scan includes a normal app security scan and a scan of the container images included in the app.”Source: docs.snowflake.com
Sources
(4)
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.
“Data exfiltration: Malicious apps could copy consumer data to external functions or logs.”
↩︎ Why provider code is reviewed before consumers run it“This service automatically scans all new app versions using various tools to determine if an app can be distributed to consumers.”
↩︎ Why provider code is reviewed before consumers run it“providers automatically share the code in app with Snowflake for scanning.”
↩︎ Why provider code is reviewed before consumers run it“Snowflake does not send a notification if an app is rejected.”
↩︎ Rejections, appeals and monitoring after approval“Snowflake uses the Native App Anti-Abuse Pipeline Service (NAAAPS).”
↩︎ Key concept - 2.
“The automated security scan is not performed when the DISTRIBUTION property is set to INTERNAL.”
↩︎ How DISTRIBUTION and release channels trigger the scan“The provider can set the release directive for the application package.”
↩︎ How DISTRIBUTION and release channels trigger the scan“A provider can appeal the rejection by opening a severity 4 support ticket.”
↩︎ Rejections, appeals and monitoring after approval“the provider is notified and given 30 business days to patch the app or can request an exception within 15 days.”
↩︎ Rejections, appeals and monitoring after approval“Adding a version only to the QA release channel does not initiate the security scan.”
↩︎ Exam trap 1“The automated security scan is not performed when the DISTRIBUTION property is set to INTERNAL.”
↩︎ Exam trap 2“the automated security scan is automatically run on the 10 most recent patches of every version in the application package.”
↩︎ Prediction“Adding a version only to the QA release channel does not initiate the security scan.”
↩︎ Checkpoint - 3.
“Only versions that have passed the provider’s security review should be added to this package”
↩︎ How DISTRIBUTION and release channels trigger the scan“Your app must not load or execute any code from outside the application package except Snowflake-provided libraries.”
↩︎ Code, dependency and privilege rules an app must pass“Apps must not store or require any plain text customer secrets.”
↩︎ Code, dependency and privilege rules an app must pass“Review and update all third-party libraries in the app at least once a quarter.”
↩︎ Code, dependency and privilege rules an app must pass“Update and patch container images regularly to address known vulnerabilities and security issues.”
↩︎ Extra review for apps that ship containers“it must include a corresponding source map file that can be used to recover the un-minified code.”
↩︎ Exam trap 3“consumers should independently review the permissions, access, and functionality of the provider’s app to ensure it meets their security requirements and standards”
↩︎ Checkpoint“it must include a corresponding source map file that can be used to recover the un-minified code”
↩︎ Checkpoint - 4.
“Account is not allowed to create application package versions or patches with”
↩︎ Extra review for apps that ship containers“This scan includes a normal app security scan and a scan of the container images included in the app.”
↩︎ Extra review for apps that ship containers