> 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

Find, filter, and review Attack Surface Testing results in the Services inventory.

{% 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](https://2229240073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F02CCMTnqc4fWJkdEuCs8%2Fuploads%2Fgit-blob-99464324336771a89421a1a2c8840655a5055e31%2F1a70e9b73bf764dc480ada2ecfec0c503f36ac8dcc8229461d4567883b799c53.png?alt=media)
   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](https://2229240073-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F02CCMTnqc4fWJkdEuCs8%2Fuploads%2Fgit-blob-35159de6f080a14e15991ad6a5f6d9490ffd7509%2Fa5fa00bebbf1a9ac97aa70735baae3bfd1c5bf3b719a67c05a6e1da9ce064353.png?alt=media)


---

# 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-test-results.md?ask=<question>&goal=<user_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.