> 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/xsoar-6-release-notes/6.13/new-features.md). # New Features New features are available in Cortex XSOAR 6.13. #### Platform Cortex XSOAR 6.13 now supports the following: * Oracle Linux versions 7.x, 8.9, 9.3, and 9.4 (for engine and server installation) * RHEL versions 8.x and 9.x, including all minor versions (for engine and server installation) * Elasticsearch versions 8.11, 8.12 and 8.13 * OpenSearch versions 2.10, 2.11, 2.12, 2.13, and 2.14 #### Migration Seamlessly migrate all your data, configurations, and settings including indicators and incidents from Cortex XSOAR 6.13 On-prem to Cortex XSOAR 8 Cloud using a built-in wizard that streamlines the migration process. Cortex XSOAR 8 has been designed to deliver improved performance and reliability. It is now highly scalable, based on revamped cloud-native microservice architecture. Palo Alto Networks manages performance and scaling, enabling you to focus on investigation and response. To start the migration, users need to upgrade to this version. For more information about the Migration process, see [Cortex XSOAR Migration Guide](https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Migration-Guide-From-V6-to-V8). --- # 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/xsoar-6-release-notes/6.13/new-features.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.