> 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-test-results.md).

# View attack surface test results

{% hint style="info" %}

### Note

You must have a role that includes view or edit permission for Vulnerability Testing to see attack surface test results. To check your role-based permissions go to **Settings** → **Configurations** → **Access Management** → **Roles**, select the role. Select the **Components** tab, and find **Vulnerability Testing** under **Incident Response** → **Detections.**
{% endhint %}

Attack surface test results are displayed on the **Services** page in the Inventory. The following fields in the Services table enable you to search for specific vulnerabilities.

* **Confirmed Vulnerabilities**—This field lists the CVE IDs (or other vulnerability IDs) of the vulnerabilities that have been confirmed present on the service. You can search this field for a specific CVE ID to find all the services that have a confirmed vulnerability with that ID.
* **Confirmed Not Vulnerable**—This field lists CVE IDs (or other vulnerability IDs) of the vulnerabilities that have been confirmed to be not present on the service. You can search this field for a specific CVE ID to find all the services that have are confirmed not vulnerable for that vulnerability.
* **Vulnerability Test Result**—The value **Confirmed Vulnerable** indicates there is at least one confirmed vulnerability on the service. You can filter on this field to find all services with at least one confirmed vulnerability.

How to view attack surface test results for a specific CVE

1. Navigate to **Inventory** → **Services**
2. Filter the Services table to find the services with a specific confirmed vulnerability.

   1. Click on the filter icon at the top of the Confirmed Vulnerability ID column, and enter the vulnerability ID in the dialog box.

      ![ast-filter.png](/files/slmd5gql1mRO3dwzh3pO)
   2. Click anywhere outside the dialog box to filter.

   The list of services that are confirmed to have that vulnerability will display.
3. Click on a row in the table to display the details panel for that service.

   On the service details panel, you can review the list of tests run, test dates, whether each test produced a confirmed vulnerable or confirmed not vulnerable result, evidence, and remediation guidance.

   Click the arrow to the left of each test result to display the 14-day test history and the evidence payload returned by the service.

   ![vt-result-details.png](/files/uyzfzfyuWL4sZzUY3g7K)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xpanse/attack-surface-testing/view-attack-surface-test-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.