> 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/active-response/how-active-response-works.md). # How Active Response Works Learn how Active Response automates alert investigation, remediation, and resolution validation. When Expander identifies an exposure on your attack surface, it creates a new alert and the Active Response module executes an automation playbook. This playbook progresses through a set of stages, as illustrated in the figure below. During each of these stages various automation integrations may be utilized to collect data, send Expander data to another system, or take a remediation action. The Active Response playbook contains a set of sub-playbooks, which support many different remediation paths that can be taken depending on the types of configured integrations, the type of alert, and input provided by the analyst. After the final stage, the alert is resolved. ![how-active-response-works.png](https://2229240073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F02CCMTnqc4fWJkdEuCs8%2Fuploads%2Fgit-blob-8bf8bc8166c68b3ea43a30465ede727d062d7aca%2F5e237202c841d3c2f71b5c5f160973b531bdbdc89d8f86ed532026041f6487eb.png?alt=media) ## Remediation Confirmation Scanning During the validation stage, Xpanse validates the resolution of alerts by completing a remediation confirmation scan. This scan utilizes the same payloads and global scanning infrastructure that was used for service discovery to ensure that the risk has been addressed and that it won't inadvertently generate a new alert during the next scheduled scan of this asset. --- # 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/active-response/how-active-response-works.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.