Integration description file
Cortex XSIAM integration description files and instance configuration.
The integration description file provides the supported integration use cases, and helps Cortex XSIAM users to easily configure an integration instance.
Common integration description file use cases
How to get credentials
How to get API Key/secret
How to get Application ID
Integration description file location
The description file should be placed with the rest of the integration's files.
For example, if the pack name is HelloWorld and the integration name is also HelloWorld, the description file path is:
~/.../content/Packs/HelloWorld/Integrations/HelloWorld/HelloWorld_description.md
Integration description file content
The description file contains details on how to configure an integration instance, together with the relevant details needed from the product that are important for configuration. The file content can include troubleshooting tips and advanced details for different configuration cases.
Integration description file example
This is the content of the HelloWorld_description.md file:
View integration description file content in Cortex XSIAM
The content of the description file is displayed in the Help tab next to the integration instance settings configurations:

Support level header YAML metadata key
The supportlevelheader key can be set to one of the following values to set the support level header in the content description:
xsoar- The description specifies that Palo Alto Networks supports this integration.partner- The description specifies that this integration is partner supported and list the partner's contact information.community- The description specifies that this integration is community supported or lists the pack's author.
Set the support level header YAML metadata key
To set the key, open the YAML file for the integration in the same folder where the description file is located and add the supportlevelheader key with of the supported values listed above.
If the key is not set in the integration YAML, the support level header is set to the support key in the pack_metadata.json file.
Last updated
Was this helpful?
