> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/marketplace/content-changes-when-upgrading-cortex-xsiam-versions.md). # Content changes when upgrading Cortex XSIAM versions Understand Cortex XSIAM Marketplace content changes during Cortex XSIAM upgrades. Cortex XSIAM will be upgraded automatically approximately every 3 months. During the upgrade, the following core content packs may automatically upgrade to a newer version: * Aggregated Scripts * Atlassian Jira * AWS * Azure * Base * Common Playbooks * Common Scripts * Common Types * Core * Core Issue Fields * Cortex Lock * Cortex Response And Remediation * Cortex REST API * Filters And Transformers * Generic Export Indicators Service * GCP * HelloWorld * Image OCR * Microsoft Teams * MITRE ATT\&CK Feed V2 * Prisma Cloud * Rasterize * ServiceNow * Slack * Threat Intelligence Management * Unit 42 Threat Intelligence by Palo Alto Networks * VirusTotal * Whois * WildFire by Palo Alto Networks --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/marketplace/content-changes-when-upgrading-cortex-xsiam-versions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.