-
Notifications
You must be signed in to change notification settings - Fork 56
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Create paid-packs-process * Update paid-packs-process * Rename paid-packs-process to paid-packs-process.md * Update paid-packs-process.md * Update paid-packs-process.md * Update premium_packs.md * Update premium_packs.md * Update marketplace.md * Update marketplace.md * Update marketplace.md * Update marketplace.md * Update paid-packs-process.md * Update premium_packs.md * Update paid-packs-process.md * Update marketplace.md * Update paid-packs-process.md * Update docs/partners/paid-packs-process.md Co-authored-by: Shahaf Ben Yakir <[email protected]> * Update marketplace.md * Update become-a-tech-partner.md * Update become-a-tech-partner.md * Update become-a-tech-partner.md * Update paid-packs-process.md * Update paid-packs-process.md Co-authored-by: Shahaf Ben Yakir <[email protected]>
- Loading branch information
1 parent
f2589da
commit ff5b7c5
Showing
4 changed files
with
43 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,7 @@ With the release of Cortex XSOAR v.6 in August 2020, we are pleased to announce | |
|
||
[Cortex XSOAR Marketplace](/marketplace) is a digital storefront for discovering, exchanging and contributing security orchestration content centrally within the Cortex XSOAR platform. It enables users to install turnkey content packs to help solve any security use case with content contributed by SecOps experts and the world’s largest SOAR partner community, including you. | ||
|
||
Additionally, Partners have the ability to monetize their content on the Marketplace. You decide the content, the price, and how to best market it, and get a healthy share of the revenue. The customer gets premium content to solve their use case. It's a win-win. | ||
Additionally, Partners have the ability to monetize their content on the Marketplace. You decide the content, the price, and how to best market it, and get a healthy share of the revenue. The customer gets premium content to solve their use case. It's a win-win. Partners who wish to contribute paid packs must follow a few [additional onboarding steps](/docs/partners/paid-packs-process). | ||
|
||
## Packs | ||
|
||
|
@@ -57,10 +57,5 @@ This page is meant as an overview to Marketplace. Please see the [Palo Alto Netw | |
|
||
## More Information | ||
|
||
Marketplace is an in-product experience for our users. Existing partners can simply upgrade their NFR to v.6+ and Marketplace will be included so you can see your pack! Contact the [Alliances Team](mailto:[email protected]) with any questions. | ||
If you are interested in contributing a pack, please [submit your application](https://start.paloaltonetworks.com/become-a-technology-partner) today. Contact the [Partner Success Team](mailto:[email protected]) with any questions. | ||
|
||
If you are interested in contributing a pack, please [submit your application](https://start.paloaltonetworks.com/become-a-technology-partner) today. | ||
|
||
## Contact us | ||
|
||
Reach out to the [Alliances Team](mailto:[email protected]) to discuss your new or improved listing on our marketplace. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
--- | ||
id: paid-packs-process | ||
title: Paid Packs Process | ||
--- | ||
|
||
The process for submitting a paid pack on XSOAR differs slightly from that of a free pack but our <a href="mailto:[email protected]">Partner Success Team</a> will help you through the whole way. | ||
|
||
## 1. Sign the Terms & Conditions Document | ||
|
||
All publishers who wish to contribute a paid pack on Marketplace must sign a 2pg terms and conditions document that defines a few additional terms to the Technology Partner Agreement (TPA) including taxes, invoicing, revenue share, etc. It will be executed via DocuSign and we do not accept redlines. | ||
|
||
## 2. Complete Vendor Onboarding | ||
|
||
In order for us to pay the revenue share, publishers of paid packs must complete Palo Alto Networks vendor onboarding. This process is straightforward and begins by completing a form and then you can expect communications with our Onboarding team via email and our secure portal. | ||
|
||
## 3. Create Private Repository | ||
|
||
Paid packs are not stored in the XSOAR open source repository but instead in the publisher's own, private GitHub repo. We'll help you [set it up](/docs/packs/premium_packs). | ||
|
||
## 4. Build Paid Pack(s) | ||
|
||
Build the content for the paid packs. | ||
|
||
- If you're submitting a premium content pack, add the dashboards, playbooks, etc. as you would normally. Revisit the [Contributor Guidlines](https://xsoar.pan.dev/docs/contributing/contributing#contributor-guidelines) if needed. | ||
- If you're submitting a premium resell pack, the pack is mostly empty except for some basic metadata files. | ||
|
||
Either way, we'll work with you to define, scope and guide you through the process. | ||
|
||
## 5. Open a Pull Request on Private Repo | ||
|
||
In order for us to review the content, we must receive a pull request and access as detailed [in our docs](/docs/packs/premium_packs). After our review, we'll add your pack Marketplace automatically. | ||
|
||
----- | ||
|
||
We've strived to make this a simple process with minimal burden on the partner. If you're interested in submitting premium content on our Marketplace, please <a href="mailto:[email protected]">contact the Partner Success Team</a> today. |