Create a Content Pack - Administrator Guide - 6.10 - Cortex XSOAR - Cortex - Security Operations

Cortex XSOAR Administrator Guide

Product
Cortex XSOAR
Version
6.10
Creation date
2022-10-13
Last date published
2024-12-04
End_of_Life
EoL
Category
Administrator Guide
Abstract

Create a Content Pack and submit it to Cortex XSOAR for approval. Add your Content Pack to the Marketplace.

Any user can add content that has been created to a content pack. The content pack is submitted and reviewed by Cortex XSOAR to ensure it complies with Cortex XSOAR standards. After approval, the content pack can be accessed in the Marketplace.

This topic specifically addresses contributing content through the Cortex XSOAR Marketplace, and is intended for smaller contributions and contributors who are not as familiar with GitHub and pull requests. Technology partners should instead submit their content packs via GitHub pull request.

  1. Select MarketplaceCONTRIBUTIONSContribute Content.

  2. In the Content Pack Editor field type a meaningful name for the content pack.

  3. In the Add Content section, from the dropdown list select the type of content you want, locate the content you want to add and click Add.

    market-contribution.png

    For more information about how to build a content pack, see the Dev Hub documentation.

  4. If you want to continue adding content at a later time or to use the Validate Pack option, click the save button.

  5. (Optional) Click Validate Pack to check for errors. The pack must be saved before you validate.

  6. If you have finished and want to send the content pack to a Cortex XSOAR developer for review, click Save and contribute to either contribute or download your contribution.

  7. (Optional) In the Contribute dialog box, add a description.

  8. Select Save and submit your contribution, enter your email address and click Contribute.

    market-cont-review-2.png

    Note

    Instead of submitting the contribution, you can also download the content pack and upload it, for example, to GitHub.

  9. After you contribute the content pack, you will receive an email with a link to a form you must complete.

    1. Fill in additional details, such as pack name, author, and description.

    2. Log in to your GitHub account to participate in the review process of the pull request that is automatically opened for your content pack.

    3. Sign the Palo Alto Networks Contributor License Agreement.

    If you are updating an existing content pack:

    1. Select Update Existing Pack from the Select Contribution Mode menu.

    2. Select the pack you want to update from the Select Existing Pack menu.

    3. Log in to your GitHub account to participate in the review process of the pull request that is automatically opened for the content pack.

    4. Sign the Palo Alto Networks Contributor License Agreement.

    5. Given a version number MAJOR.MINOR.REVISION, select Update Type.

      Type

      Description

      Revision

      When you make backwards compatible bug fixes.

      Minor

      When you add functionality in a backwards compatible manner.

      Major

      A major revision contains one or more of the following:

      • Incompatible API changes

      • New features

      • Changes to existing features that could break backward compatibility

      Documentation

      When only documentation files are updated.

  10. After you submit the form, a GitHub branch is created in the xsoar-contrib content repository fork with the changes from your contribution.

  11. You will receive an invitation to join the xsoar-contrib organization. Being a member of the organization enables the xsoar-bot to invite you to a GitHub team and grant you write permissions to the created branch. (Each contributor can only modify files in content packs that they contributed).

  12. The pull request is created and a reviewer is assigned.

    Note

    The documentation for new integrations/scripts/playbooks is automatically generated and contains basic information. You need to review the documentation file, README.md, and modify it according to Cortex XSOAR standards. The files to be reviewed are listed at the pull request comment.

  13. You can now modify the files changed in the pull request as part of the review process.