> 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-xpanse-expander-rn/expander-release-information.md). # Cortex Xpanse Expander Release Information Cortex Xpanse Expander is a cloud-based attack surface management solution that helps organizations find and fix their known and unknown internet-connected risks. Expander performs automated, continuous scans to index the entire internet and discover all connected assets, misconfigurations, and exposed services. Expander's supervised machine-learning model accurately attributes assets to your organization, identifies exposures, and prioritizes these exposures for remediation. With the Cortex Xpanse Active Response add-on module, AI-powered playbooks automatically identify service owners and remediate exposures. The topics in this release note describe the new features and enhancements introduced in Cortex Xpanse Expander. --- # 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-xpanse-expander-rn/expander-release-information.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.