> 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-xsoar-8-feature-changes/cortex-xsoar-8-feature-changes/readme.md). # Cortex XSOAR 8 Feature Changes Explore feature changes in Cortex XSOAR 8 SaaS and Cortex XSOAR 8x On-prem. Cortex XSOAR 8 comes in the following formats: * Cortex XSOAR SaaS * Cortex XSOAR On-prem ### Cortex XSOAR SaaS Cortex XSOAR 8 SaaS is built on the Cortex Platform, which offers: * Improved performance, scalability, and reliability * Centralized user management * An enhanced user experience unified with the broader Cortex portfolio * Simplified deployment and onboarding across the Cortex portfolio * Auto-scalability and built-in high availability * Automatic software updates are free of compatibility issues ### Cortex XSOAR On-prem Cortex XSOAR 8 On-prem offers the following: * Unified look and feel * Simplified deployment and onboarding * Improved performance and reliability * User-friendly installation with an easy-to-follow step-by-step TUI to install and configure Cortex XSOAR. --- # 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-xsoar-8-feature-changes/cortex-xsoar-8-feature-changes/readme.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.