> 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-xdr-3.x/cortex-xdr-3.x-documentation/configure-incidents-and-alerts/prioritize-incidents-with-starring-and-scoring/incident-starring.md).
# Incident starring
To help you focus on the most important incidents, you can star an incident. Starring incidents enables you to narrow down the scope of incidents on the **Incidents** page and in the **Incident management** dashboard. Cortex XDR identifies starred incidents with a purple star.
You can star incidents manually, or create an incident starring configuration. An incident starring configuration automatically categorizes and stars incidents that contain alerts with specific attributes. In a starring configuration you define attributes or assets for alerts that you want to star. If an alert matches the attributes in the starring configuration, the alert and incident containing the alert are starred. You can manage all starring configurations under Incident Response → Incident Configuration → **Starred Alerts**.
Scope-Based Access Control considerations
Incident starring supports Scope-Based Access Control (SBAC). The following parameters are considered when editing a starring configuration:
* If Scoped Sever Access is enabled and set to restrictive mode, you can edit a configuration if you are scoped to all tags in the configuration.
* If Scoped Sever Access is enabled and set to permissive mode, you can edit a configuration if you are scoped to at least one tag listed in the configuration.
* If a policy was added when set to restrictive mode, and then changed to permissive (or vice versa), you will only have view permissions.
Star a specific incident
You can manually star an incident during or after investigation:
1. Select Incident **Response → Incidents**.
2. In the list of incidents, locate the incident you want to star.
3. Select the star icon.
Create a starring configuration
You can proactively star alerts and incidents containing alerts by creating a starring configuration:
1. Select **Incident Response** → **Incident Configuration** → **Starred Alerts**.
2. Select **Add Starring Configuration**.
3. Under **Configuration Name**, enter a name to identify your starring configuration.
4. (Optional) Under **Comment**, enter a descriptive comment.
5. In the alert table, use the filters to define the alert attributes you want to include in the match criteria.
You can also right-click a specific value in the alert to add it as match criteria.
6. Click **Create**.
---
# 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-xdr-3.x/cortex-xdr-3.x-documentation/configure-incidents-and-alerts/prioritize-incidents-with-starring-and-scoring/incident-starring.md?ask=&goal=
```
`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.