> 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/view-attack-surface-tests.md). # View attack surface tests View information about the available attack surface tests, and enable or disable tests on the **Vulnerability Testing** page. By default all tests are enabled. 1. Navigate to **Rules** → **Vulnerability Testing**. 2. Filter and sort the list of tests as needed to identify the tests you want to enable or disable. 3. Select one or more tests using the check boxes, and right click to **Enable** or **Disable** them. ## Attack surface test field descriptions


Field	Description
Affected Software	Software names and versions impacted by this vulnerability.
CWE IDs	Common Weakness Enumeration ID. This ID is defined by MITRE.
Created	When Cortex Xpanse released this test.
Description	Description of the vulnerability.
EPSS Score	The Exploit Prediction Scoring System (EPSS) score indicates the likelihood that a vulnerability will be exploited in the wild. Possible values are between 0 and 100%, and the higher the score, the greater the probability that a vulnerability will be exploited.
First Published	When this vulnerability was first published.
ID	Unique ID for this test.
Name	Name of the test.
References	Research references and supporting documentation.
Remediation Guidance	Recommended steps for remediating or mitigating the vulnerability.
Severity Score	The CVE severity score is based on the NIST Common Vulnerability Scoring System (CVSS).
Services Found Vulnerable	The number of directly-discovered services owned by your organization that Cortex Xpanse has confirmed vulnerable with this test.
Status	Indicates whether the test is Enabled or Disabled.
Vendor Names	Name of the vendor whose product is impacted by the vulnerability.
Vulnerability IDs	CVE number or other public identifier for the vulnerability.

--- # 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/view-attack-surface-tests.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.