What you will be able to do
- Choose between a private listing and a Snowflake Marketplace listing, and know which of them needs Snowflake's listing approval
- Predict which versions and patches the automated security scan reviews when DISTRIBUTION becomes EXTERNAL or a new patch is added
- Prepare app code that passes the scan: human-readable code, source maps for minified JavaScript, everything shipped inside the package
- Explain how Snowflake's CVE criteria decide whether a vulnerable dependency blocks approval
- Find a rejection reason, file a valid appeal, and get a Marketplace listing through Approved to published
Key concept
Two publishing gates — An app shared outside its organization has to pass two separate checks. First, every version or patch must pass Snowflake's automated security scan, which runs once the package is EXTERNAL. Second, only for Snowflake Marketplace, Snowflake has to approve the listing itself before it can be published.
1.From approved version to published listing
Consumers never install an application package directly. They install from a listing: the provider adds the application package to the listing as its data product, and the consumer installs the app into their own account from that listing. Publishing therefore means getting two things ready. The app version has to be ready to ship, and the listing has to be ready to show.
These steps have a fixed order:
- Set the default release directive so it points at the version or patch being published.
- Start the automated security scan and wait until that version shows APPROVED.
- In Provider Studio, create a listing and attach the application package.
- Optionally add a pricing plan.
- Submit the listing for approval. Only Marketplace listings need this step.
- Publish the listing.
The release directive is how consumers end up on a particular version. It is covered in release directives and release channels. Here it matters as a prerequisite: before you create the listing, the default release directive must point to the version or patch you are publishing. If you use release channels, set it on the default channel. Pricing plans are covered in monetization.
Ownership limits who can do the publishing. The role that attaches the application package to a listing and publishes it must be the role that owns the package. If a different role manages the listing, grant MODIFY on the listing to the package-owning role. The listing-owning role then needs OWNERSHIP on the listing and the global CREATE LISTING privilege.
Checkpoint 1 of 10· Put it in order
A provider wants to publish their Native App on the Snowflake Marketplace. The application package is already EXTERNAL and has a new patch. Put the remaining steps in order.
- 1.Publish the listing
- 2.Submit the listing to Snowflake for approval
- 3.In Provider Studio, create a listing and attach the application package
- 4.Optionally add a pricing plan to the listing
- 5.Wait until the security scan shows APPROVED for the patch
The app version must pass the security scan before the listing is built around it. A Marketplace listing then has to be approved by Snowflake before it can be published. A private listing for specified consumers would skip the approval step.
“Before you can publish a listing to the Snowflake Marketplace, you must submit the listing to Snowflake for approval.”Source: docs.snowflake.com
Sources1
2.Private listings versus Marketplace listings
One setting decides who can see an app: Who can discover the listing, chosen when you create the listing in Provider Studio. Choose Only specified consumers to make a private listing, then add the account identifiers of the consumers allowed to use it. Choose Anyone on the Marketplace and the listing appears in the public Snowflake Marketplace catalog. A provider who wants an app available to two named accounts and invisible to everyone else uses a private listing that names those accounts. No Marketplace listing setting does that.
Marketplace listings also ask a second question, How will consumers access the data product?, with the answers Free or Paid. This controls how consumers get the app, not who can see it. A Paid Marketplace listing is still public. Auto-fulfillment is a separate matter too. A private listing needs it when a named consumer account is in another region, and it governs delivery, not discovery.
| Listing type | Discovery setting | Provider profile | Snowflake listing approval | Result of saving |
|---|---|---|---|---|
| Private listing | Only specified consumers, plus consumer account identifiers | Not required | Not required | Publish straight to the named accounts, or Save Draft |
| Marketplace listing | Anyone on the Marketplace, plus Free or Paid | Used for the listing | Required before publishing | A draft listing that needs more configuration |
Being private does not exempt a listing from the security scan. The DISTRIBUTION property sets where a package can be listed. INTERNAL packages can only be listed privately inside the provider's own organization, and they are never scanned. Once a private listing targets an account in another organization, the package has to be EXTERNAL, and its versions have to pass the scan just as a Marketplace app's do. The only thing a private listing skips is Snowflake's approval of the listing.
Checkpoint 2 of 10· Check yourself
A provider wants their Native App visible only to two accounts that belong to a partner company's Snowflake organization. They create a listing with "Only specified consumers" and add those two account identifiers. Which publishing gates must the app pass?
Only Marketplace listings need Snowflake's listing approval, so this private listing can be published right away. But because the consumers are in another organization, the package must be EXTERNAL and its versions must pass the security scan first.
“Submit your listing for approval. You only need to approve listings published to the Snowflake Marketplace.”Source: docs.snowflake.com
Checkpoint 3 of 10· Exam question
A provider wants to make a Snowflake Native App available only to two specific consumer accounts, without the app appearing in the Snowflake Marketplace catalog. Which listing configuration should the provider use?
Correct answer: A — Create a private listing that targets those two accounts by organization and account identifier
- A. A private listing is scoped to specified consumer accounts using their organization and account identifiers, and it never appears in the Marketplace catalog, which matches the requirement to reach only two named accounts.
- B. Public Marketplace listings are visible to any consumer in the enabled regions; restricting a region does not limit visibility to two specific accounts, so this still exposes the listing to the wrong audience.
- C. Limited Trial is an access type for public Marketplace listings and controls trial duration, not which accounts can see the listing, so it does not meet the private-targeting requirement.
- D. Paid access with Stripe billing is a monetization setting for public Marketplace listings and does not restrict the listing to specific consumer accounts.
3.What starts the automated security scan
Nobody asks for a scan by hand. Snowflake's Native App Anti-Abuse Pipeline Service (NAAAPS) scans new app versions automatically. It copies the app into a dedicated scanning account, scans its files, and then either approves the app or sends it for manual review. What starts this depends on when the package became EXTERNAL.
Without release channels, there are two triggers. If the package was created with DISTRIBUTION = EXTERNAL, each version or patch added afterwards is scanned as soon as it is added. If an existing package is switched to EXTERNAL with ALTER, the scan runs straight away on the 10 most recent patches of every version it already holds. Nothing waits for a consumer install or a support request.
ALTER APPLICATION PACKAGE hello_snowflake_package
SET DISTRIBUTION = EXTERNAL;With release channels enabled, the trigger is the channel. Adding a version to the ALPHA or DEFAULT release channel scans that version's 10 most recent patches. Adding a version only to the QA channel does not start a scan, so QA is where testers can try builds without waiting for a review.
Each version and patch has a review status. In SQL, check the review_status column of SHOW VERSIONS IN APPLICATION PACKAGE. In Snowsight, go to Projects » App packages and look at the Security Scan Status column.
| Status | Meaning |
|---|---|
| NOT_REVIEWED | The automated scan has not been run on this package |
| IN_PROGRESS | The scan is running |
| APPROVED | The scan finished and approved the package, so the provider can now set the release directive |
| REJECTED | The scan finished and the package was not approved |
Checkpoint 4 of 10· Check yourself
Release channels are enabled on an EXTERNAL application package. The team has a new build that internal testers should try right away, without starting a security review. Which action does that?
When release channels are enabled, adding a version to ALPHA or DEFAULT starts a scan of its 10 most recent patches. Adding it only to QA starts no scan. Scans never wait for a consumer install, and leaving the release directive unchanged does not stop one.
“Adding a version only to the QA release channel does not initiate the security scan.”Source: docs.snowflake.com
Checkpoint 5 of 10· Exam question
A provider has an existing application package with several versions and patches already added under DISTRIBUTION = INTERNAL. The provider now changes the package to DISTRIBUTION = EXTERNAL to prepare for Marketplace publication. What happens as a result?
Correct answer: A — Snowflake immediately scans the 10 most recent patches of every version for security issues
- A. Switching an existing package to EXTERNAL distribution triggers Snowflake to scan the 10 most recent patches of every version already in the package, not just the latest one.
- B. The scan is not limited to a single most-recent patch; Snowflake scans up to 10 recent patches per version once EXTERNAL distribution is set.
- C. The scan runs when the DISTRIBUTION property changes, not when a consumer later installs the app, so this describes the wrong trigger.
- D. No manual support case is needed to start the scan; setting DISTRIBUTION to EXTERNAL triggers it automatically.
Sources2
4.Code requirements: readable, mapped and self-contained
The scanner checks code for bugs, anti-patterns, security vulnerabilities and malware. It can only do that if it can read the code. That is why all app code must be un-obfuscated, meaning a human can read it, and JavaScript is included. Code that is packed or scrambled so nobody can follow it breaks the rule, whatever language it is written in.
Minified JavaScript is allowed only if it comes with a source map. The source map has to let a reviewer recover the un-minified code. Shipping a minified bundle for a Streamlit component or a front end is fine. Shipping it without the map is a violation.
This can look like it conflicts with protecting your code. Intellectual property protection is about stopping *consumers* from seeing provider code. It is not permission to make the code unreadable. Snowflake's security review still has to be able to read the code, so obfuscating it to protect your IP fails the readability requirement.
The code also has to be complete. An app must not load or run code from outside its application package, except Snowflake-provided libraries. All library dependencies and setup code must be part of the app version in the package. A setup script that downloads a module at run time breaks this rule even if the module is harmless.
Checkpoint 6 of 10· Match them up
Match each way of packaging app code to how the security review's code requirements treat it.
Tap a term, then the definition that fits it.
The scanner can only check code it can read and code that is inside the package. So minified code needs a source map, obfuscation is never allowed, and only Snowflake-provided libraries may come from outside the application package.
“it must include a corresponding source map file that can be used to recover the un-minified code.”Source: docs.snowflake.com
Checkpoint 7 of 10· Exam question
According to Snowflake's security requirements for Native Apps, what is required of all application code, including JavaScript?
Correct answer: A — The code must be un-obfuscated and human readable in its submitted form
- A. Snowflake requires that all app code, including JavaScript, be un-obfuscated and human readable so it can be reviewed as part of the security scan.
- B. There is no requirement to avoid JavaScript in favor of Python; the readability rule applies regardless of programming language used.
- C. Snowflake's published readability requirement concerns un-obfuscated code, not digital signing with a provider certificate.
- D. Compiling to WebAssembly would make the code less readable, which conflicts with the human-readability requirement rather than satisfying it.
Sources3
5.Dependency vulnerability scanning
Dependencies get their own scan. During the security review, Snowflake checks every incoming app's packages and dependencies for known Common Vulnerabilities and Exposures (CVEs). The rule for providers is simple: any dependency with a critical or high CVE must be updated to a secure version, if one exists.
Not every CVE the scanner finds blocks approval. Snowflake judges each one against three criteria. An app is rejected if any of its packages has a CVE that meets them and has not been properly remediated.
| Criterion | What it means |
|---|---|
| Confirmed fix | The National Vulnerability Database (NVD) lists a fix, so the provider can actually remediate it |
| High integrity impact | Under the Common Vulnerability Scoring System (CVSS), a total loss of integrity: data can be changed or tampered with without restriction |
| EPSS score of 10 percent or higher | The Exploit Prediction Scoring System (EPSS) rates the vulnerability as likely to be exploited |
The confirmed-fix criterion is the practical one. Snowflake reports a CVE as actionable only if a fixed version exists, so upgrading the library is nearly always the remedy. Waiting for a rejection is the expensive way to find out. Snowflake recommends reviewing third-party libraries during development and updating every library in the app at least once a quarter. A CVE in an old pinned library can block an otherwise finished release.
Checkpoint 8 of 10· Match them up
During the dependency scan, Snowflake weighs each CVE it finds in an app's packages against fixed criteria. Match each criterion, or the provider rule, to what it means.
Tap a term, then the definition that fits it.
Snowflake reports a CVE as actionable only when a fix exists, and it focuses on CVEs with high integrity impact or a high likelihood of exploitation. That is why upgrading the affected library to a secure version is nearly always the remedy.
“Snowflake provides actionable information and reports only on CVEs that have a confirmed fix according to the National Vulnerability Database (NVD).”Source: docs.snowflake.com
6.Rejections, manual review and appeals
A failed automated scan is not the final decision. When an app fails, Snowflake reviews it manually, and that review sets the status to APPROVED or REJECTED. If the manual review finds critical vulnerabilities or policy violations, the package is rejected, and the reason is recorded in the application package.
Snowflake does not notify you when a scan rejects an app. You have to check the status yourself in Snowsight. If it says Rejected, select the app package to see the rejection reason and code. You get the reason, but not the scan's internal details, which Snowflake does not provide.
After a rejection, you can fix the code and add a new patch, which is scanned again. If you think the rejection is wrong, you can appeal. Appeals have strict rules:
- Open a severity 4 support case. Use the category General Administration and the subcategory Other, and write the summary as
Appeal <App Name>, <Version>, <Patch>. - Snowflake allows one appeal per patch. Put everything in that one case, because later appeals for the same patch are rejected, and an incomplete case can be rejected without review.
- Appeals take 3–5 business days. Cases filed at a higher severity may be downgraded to severity 4.
Appeals against a CVE rejection need specific evidence: why the CVE cannot be exploited in this app, a reachability analysis report if you have one, and a plan for upgrading to the fixed version. If you have no upgrade plan, explain in detail why the vulnerable version cannot be updated. The Snowflake Security team decides every appeal.
Passing the scan once does not end the checks. Published Marketplace apps are monitored continuously. If new issues are found, the provider is notified and has 30 business days to patch, or can request an exception within 15 days.
Checkpoint 9 of 10· Check yourself
Days after adding a patch to an EXTERNAL package, a provider opens Snowsight and sees the patch marked Rejected, citing a CVE in a dependency. The provider believes the CVE cannot be exploited in the app. What is the right way to contest it?
Snowflake accepts only one appeal per patch and rejects later ones, so all the evidence has to go into a single severity 4 case. Snowflake sends no email when a scan rejects an app and does not share scan details. Cases filed at a higher severity may be downgraded to severity 4.
“Snowflake allows one appeal per patch of an app. You must provide all information about your appeal in a single support case.”Source: docs.snowflake.com
7.Listing content and approval for Snowflake Marketplace
Choosing Anyone on the Marketplace creates a draft, not a live listing. In Provider Studio, open the draft from the Listings tab and fill in each required section. The listing content is part of the security requirements, not just presentation. Every app must tell consumers in its listing:
- How to install and set up the app.
- All of the app's functionality and features.
- Whether consumer data is used to train or optimize AI models.
- Every Internet endpoint and URL the app connects to.
- Every external function in the app.
- Any consumer data, queries, prompts or responses the app logs, collects or stores.
The manifest file must also declare every privilege the app needs, on every object, and every API integration. The app should request only the privileges it needs to work. Its behaviour has to match the listing too: apps must not store or require plain-text customer secrets, and Internet traffic should use HTTPS with a valid TLS certificate.
If the Submit for Approval button is greyed out, check three things. Has every listing section been configured? Are you ACCOUNTADMIN, or do you hold OWNERSHIP on the attached data product? Do all of the listing's sample SQL queries pass validation?
After Snowflake reviews the listing, its state changes to Approved or Denied. Unlike a scan rejection, either decision triggers an email to the Business Contact and the Technical Contact in the provider profile linked to the listing. If the listing is denied, update it based on the reviewer's comments and submit it again. Once it is approved, select Publish to put it on the Snowflake Marketplace. After that you can create a referral link that sends consumers straight to the listing.
Checkpoint 10 of 10· Check yourself
Snowflake reviewed a provider's Snowflake Marketplace listing for their Native App and set its state to Denied. How does the provider find out, and what should they do next?
Unlike a scan rejection, a listing decision (Approved or Denied) triggers an email to both contacts in the provider profile. A denied listing is fixed by updating it based on the reviewer's comments and submitting it again. The support-case appeal and the new-patch rescan both belong to the security scan, not to listing approval.
“When a listing is approved or denied, an email notification is sent to both the Business Contact and Technical Contact email addresses”Source: docs.snowflake.com
Practise it for real
Start the automated security scan on an existing application package and read its result
1.Run ALTER APPLICATION PACKAGE hello_snowflake_package SET DISTRIBUTION = EXTERNAL; on a package that already has versions.
Why: Switching an existing package to EXTERNAL is one of the triggers for the scan.
You should see: The 10 most recent patches of every version are queued for scanning.
2.Run SHOW VERSIONS IN APPLICATION PACKAGE hello_snowflake_package; and read the review_status column.
Why: review_status is where SQL shows the scan state of each version and patch.
You should see: Each patch shows NOT_REVIEWED, IN_PROGRESS, APPROVED or REJECTED.
3.In Snowsight, open Projects » App packages, select the package and look at the Security Scan Status column.
Why: No notification is sent on rejection, so you have to check here.
You should see: The same statuses appear. For a rejected patch, selecting the package shows the rejection reason.
4.Once a patch is APPROVED, set the default release directive to it.
Why: An approved version is what makes setting the release directive, and then the listing, possible.
You should see: The package is ready to attach to a listing in Provider Studio.
Stuck? Get a nudge
If nothing is scanned, check whether the package uses release channels. Then the scan starts only when you add a version to the ALPHA or DEFAULT channel, never QA.
Sources
(6)
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.https://docs.snowflake.com/en/developer-guide/native-apps/ui-provider-publishing-app-packageOfficial docs
“you must specify the default release directive that points to the version or patch of the app you are publishing.”
↩︎ From approved version to published listing“must be the same role that created, and therefore owns, the application package or share.”
↩︎ From approved version to published listing“select Only specified consumers to privately share the listing with specific accounts.”
↩︎ Private listings versus Marketplace listings“select Anyone on the Marketplace to publish the listing on the Snowflake Marketplace.”
↩︎ Private listings versus Marketplace listings“Creating a provider profile is not required for private listings.”
↩︎ Private listings versus Marketplace listings“All sample SQL queries attached to the listing pass validation.”
↩︎ Listing content and approval for Snowflake Marketplace“If the listing has been denied, update the listing based on the feedback provided in comments, and resubmit it for approval.”
↩︎ Listing content and approval for Snowflake Marketplace“To publish a listing for an application package to an account outside of your organization, your application package must pass an automated security scan.”
↩︎ Key concept“You only need to approve listings published to the Snowflake Marketplace.”
↩︎ Exam trap 1“Before you can publish a listing to the Snowflake Marketplace, you must submit the listing to Snowflake for approval.”
↩︎ Checkpoint“Submit your listing for approval. You only need to approve listings published to the Snowflake Marketplace.”
↩︎ Checkpoint“When a listing is approved or denied, an email notification is sent to both the Business Contact and Technical Contact email addresses”
↩︎ Checkpoint - 2.
“INTERNAL indicates that a provider can only create a private listing within the same organization where the application package was created.”
↩︎ Private listings versus Marketplace listings“any versions or patches added to the application package later are scanned immediately.”
↩︎ What starts the automated security scan“Adding a version only to the QA release channel does not initiate the security scan.”
↩︎ What starts the automated security scan“The review_status column displays the status of the automated review scan.”
↩︎ What starts the automated security scan“A provider can appeal the rejection by opening a severity 4 support ticket.”
↩︎ Rejections, manual review and appeals“given 30 business days to patch the app or can request an exception within 15 days.”
↩︎ Rejections, manual review and appeals“the automated security scan is automatically run on the 10 most recent patches of every version in the application package.”
↩︎ Exam trap 2“the automated security scan is automatically run on the 10 most recent patches of every version in the application package.”
↩︎ Prediction - 3.
“it must include a corresponding source map file that can be used to recover the un-minified code.”
↩︎ Code requirements: readable, mapped and self-contained“Your app must not load or execute any code from outside the application package except Snowflake-provided libraries.”
↩︎ Code requirements: readable, mapped and self-contained“All dependencies or libraries with critical or high common vulnerabilities and exposures (CVE) must be updated to a secure version, if available.”
↩︎ Dependency vulnerability scanning“All apps must provide the following information in the manifest file: All privileges required by the app on all objects. All API integrations.”
↩︎ Listing content and approval for Snowflake Marketplace“All app code must be un-obfuscated, meaning that the code must be human readable. This requirement includes minified JavaScript code.”
↩︎ Exam trap 3 - 4.
“An app is rejected if it contains any packages with a CVE that meets the criteria below or is not appropriately remediated.”
↩︎ Dependency vulnerability scanning“The CVE has an EPSS score of 10 percent or higher”
↩︎ Dependency vulnerability scanning“Snowflake provides actionable information and reports only on CVEs that have a confirmed fix according to the National Vulnerability Database (NVD).”
↩︎ Checkpoint - 5.
“All appeals have a turnaround time of 3-5 business days (Monday to Friday).”
↩︎ Rejections, manual review and appeals“Snowflake allows one appeal per patch of an app.”
↩︎ Exam trap 5“Snowflake allows one appeal per patch of an app. You must provide all information about your appeal in a single support case.”
↩︎ Checkpoint
Also cited
“Snowflake does not send a notification if an app is rejected. Providers can view the status of the review in Snowsight.”
↩︎ Exam trap 4