> 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/onboard-and-configure-cortex-xpanse/configure-cortex-xpanse.md).

# Configure Cortex Xpanse

Configure attack surface rules, risk scoring, dashboards, and other customizable features to match your use cases.

After you have completed onboarding with Cortex Xpanse, you can start configuring the tenant to match your use cases and preferences.

| Section                | Description                                                                                                                                                              | More Information                                                    |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------- |
| Attack surface rules   | Review and configure attack surface rules so that Cortex Xpanse creates alerts for risks that matter to you.                                                             | [Attack surface rules](/cortex-xpanse/attack-surface-rules.md)      |
| Risk scoring           | Customize risk score settings to prioritize incidents and quantify your risk based on your specific requirements.                                                        | [Risk Scoring](/cortex-xpanse/incidents-and-alerts/risk-scoring.md) |
| Integrations           | Configure additional collection, automation, and outbound integrations.                                                                                                  | [Integrations](/cortex-xpanse/integrations.md)                      |
| Active Response        | <p>Set up Active Response, including remediation path rules, to automate enrichment and remediation of incidents.</p><p>Requires the Active Response add-on license.</p> | [Active Response](/cortex-xpanse/active-response.md)                |
| Attack Surface Testing | <p>Enable Attack Surface Testing to confirm the presence of vulnerabilities on your attack surface.</p><p>Requires the Attack Surface Testing add-on license.</p>        | [Attack Surface Testing](/cortex-xpanse/attack-surface-testing.md)  |
| Dashboards and Reports | Customize dashboards, reports, and widgets.                                                                                                                              | [Dashboards and reports](/cortex-xpanse/dashboards-and-reports.md)  |

#### What to do next

After you have configured Cortex Xpanse, you are ready to use it to manage and protect your attack surface.

* Manage your [inventory](/cortex-xpanse/inventory.md)and investigate assets.
* Investigate and remediate [alerts and incidents](/cortex-xpanse/incidents-and-alerts.md).
* Research and respond to emerging and global threat events in the [Threat Response Center](/cortex-xpanse/threat-response-center.md).
* Confirm the presence and remediation of vulnerabilities in your attack surface with [Attack Surface Testing](/cortex-xpanse/attack-surface-testing.md).
* Monitor your [security rating](/cortex-xpanse/security-rating.md).


---

# 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/onboard-and-configure-cortex-xpanse/configure-cortex-xpanse.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.