> 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-scoring/set-up-incident-scoring.md). # Set up incident scoring To set up incident scoring you need to enable SmartScore, and enable and define scoring rules.
Enable SmartScore 1. Select Settings → Configurations → **Cortex XDR- Analytics** and click **Enable**. 2. Select to Incident Response → Incident Configuration → **Incident Scoring** and enable **SmartScore**. {% hint style="info" %} ### Note On the first activation, it can take up to 48 hours for SmartScore to calculate and display the score. Enabling SmartScore subsequently impacts the User Score. {% endhint %}
Enable and define scoring rules 1. Selec Incident Response → Incident Configuration → **Scoring Rules** and enable **User Scoring Rules**. The **Scoring Rules** table displays the user-defined rules and sub-rules. 2. Click **Add Scoring Rule**. 3. In the **Create New Scoring Rule** dialog, define the rule criteria: 1. Under **Rule Name**, enter a unique name for your rule. 2. Under **Score**, define the score that Cortex XDR should apply to alerts that matching the rule criteria. 3. Under **Base Rule**, select whether to create a top-level rule (labeled **Root**) or a sub-rule (labeled ***Rule Name (ID:#)***). By default, rules are defined at the root level. 4. Select or deselect **Apply score only to first alert of incident**. By selecting this option you choose to apply the score only to the first alert that matches the defined rule. Subsequent alerts of the same incident will not receive a score from this rule. By default, a score is applied only to the first alert that matches the defined rule and sub-rule. 5. In the alert table, use the filters to define the alert attributes you want to include in the rule match criteria. Example: With this rule, Cortex XDR assigns a score of 30 to any XDR BIOC alerts with a severity level of Critical: * Score = 30 * Base Rule = Root * Filters: `Alert Source=XDR BIOC AND Severity=Critical` 4. Click **Create**. You are automatically redirected to the **Scoring Rules** table. 5. In the **Scoring Rules** table, click **Save** to save your scoring rule.

Note

For scoped users, a small lock icon indicates that you don't have permissions to edit a rule.

**What to do next** After setting up your scoring rules, you can take the following actions:
See a breakdown of the score You can see details about the scoring method and the assigned score. 1. Select Incident Response → Incidents. 2. On the **Incidents** page, click on the menu icon to switch to the detailed view. 3. Click on the assigned score. If you are not satisfied with the score, you can change the scoring method, or overwrite the score by setting the score manually. If you see a discrepancy with the assigned score, consider the following: * For rule-based scores, revise your scoring rules. * For SmartScores, help to improve the accuracy of SmartScore. **Give feedback** by hovering over the displayed score.
Change the scoring method or set the score manually You can change the default scoring method. In addition, if Cortex XDR was unable to assign a score, you can set the score manually. 1. Select Incident Response → Incidents. 2. On the **Incidents** page, click on the menu icon to switch to the detailed view. 3. Click on the assigned score. If no score was assigned, in the incident pane click the more options icon and select **Manage Score**. 4. Select a different scoring method, or click **Set score manually** and define a new score.
Revise existing scoring rules In the Scoring Rules table, take the following actions to review your rules and sub-rules: * Use the arrows to rearrange rule priorities. Make sure to click **Save** after any changes. * Select one or more rules and right-click to see the available actions.
Scope-Based Access Control considerations Incident Scoring supports Scope-Based Access Control (SBAC). If you're a scoped user, a small lock icon indicates that you don't have permissions to edit a rule. The following parameters are considered when editing a scoring rule: * If Scoped Server Access is enabled and set to restrictive mode, you can edit a rule if you are scoped to all tags in the rule. * If Scoped Server Access is enabled and set to permissive mode, you can edit a rule if you are scoped to at least one tag listed in the rule. * To change the order of a rule, you must have permissions to the other rules of which you want to change the order. * If a rule was added when set to restrictive mode, and then changed to permissive (or vice versa), you will only have view permissions.
--- # 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-scoring/set-up-incident-scoring.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.