> 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/select-targets-for-attack-surface-testing.md).

# Select targets for Attack Surface Testing

Choose specific or all directly-discovered services for Attack Surface Testing.

Attack Surface Testing targets are directly-discovered services, which are services that are definitively associated with an asset that belongs to your organization. You can choose to run attack surface tests on all your relevant directly-discovered services or you can specify a subset of services.

How to select a set of targets for attack surface testing

1. Navigate to **Settings** → **Configurations** → **Vulnerability Testing Configuration**
2. In the **Target Testing** section, click **Edit Targets** (or **Add Targets** if this is the first time you have selected targets.)
3. Use the filter to define a set of targets from your list of Services.
4. Click **Save Targets**.
5. Make sure the toggle is set to **Selected Targets**. Setting the toggle to All Targets will override your target selection.

How to select all targets for attack surface testing

1. Navigate to **Settings** → **Configurations** → **Vulnerability Testing Configuration**
2. In the **Target Testing** section, set the toggle to **All Targets**.


---

# 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/select-targets-for-attack-surface-testing.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.