> 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/attack-surface-testing.md). # Attack Surface Testing Attack Surface Testing runs benign exploits against your externally facing assets to confirm the presence of vulnerabilities. Cortex Xpanse Attack Surface Testing confirms the presence of a vulnerability on your external attack surface, enabling you to quickly and confidently prioritize risks. With your approval, Cortex Xpanse runs benign exploits against externally facing assets to confirm the presence of vulnerabilities. Rather than manually verifying inferred CVEs yourself, Cortex Xpanse Attack Surface Testing runs daily scans based on your preferences. When you set up Attack Surface Testing, you select the targets for the testing, either all or a subset of your directly-discovered services (services that are definitively associated with an asset that belongs to your organization). Once you've selected targets, Cortex Xpanse runs attack surface scans daily. Attack surface test results are displayed on the Services tab in the Inventory, so you can review the data as part of your existing attack surface management (ASM) workflow. All attack surface tests are enabled by default, but you can view information about the tests and disable tests if needed from the Attack Surface Tests page. Attack surface test results can [generate alerts](/cortex-xpanse/attack-surface-testing/alerts-for-positive-attack-surface-test-results.md) and impact an incident's [risk score](/cortex-xpanse/incidents-and-alerts/risk-scoring.md). {% hint style="info" %} ### Note Attack Surface Testing scans are not typically CFAA compliant, meaning that they may attempt more extensive fuzzing to confirm or deny the presence of a CVE. {% endhint %} --- # 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/attack-surface-testing.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.