> 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-cloud-posture-management/cases-and-issues/case-concepts/case-scoring.md).

# Case scoring

A case score is a numeric value that indicates the urgency of a case. Scoring can help you to streamline the process of prioritizing and investigating your cases, and help you to identify the cases that require immediate attention.

### Types of scoring

Cortex Cloud uses the following scoring methods:

* **Rule-based scoring:** The score is determined by user-defined scoring rules that match the issues linked to the case.

  You create scoring rules that define scores for issues with specific attributes or assets. You can base scoring rules on:

  * Hostnames
  * Asset objects, such as asset names, classes, categories, groups, providers, and business application names.
  * IP addresses
  * Users
  * Active Directory, or Azure groups and organization units

    (Requires the Cloud Identity Engine to be configured).

  When an issue is created, Cortex Cloud searches for scoring rules that match the issue. An issue can match multiple rules or sub-rules. If a match is found, Cortex Cloud assigns the scores of the matching rules to the issue. If multiple rules match the issue, the issue score is an aggregation of the rule scores. By default, a score is applied only to the first issue in the case that matches the defined rule and sub-rule.

  You can create a rule hierarchy by setting up sub-rules. If an issue matches one or more sub-rules, the sub-rule scores are also aggregated in the issue score. However, a sub-rule score is only applied to an issue if the top-level rule was a match.

  To determine the case score, Cortex Cloud calculates the combined issue score total for all issues in the case. You can see a breakdown of the score by clicking on the score in the details pane.
* **Manual scoring:** The score is defined by the user.

### How Cortex Cloud assigns the score

{% hint style="info" %}
For Cortex Cloud to provide effective rule-based scores, you must define accurate scoring rules that are suitable for your environment and workflows.
{% endhint %}

When a case is created, Cortex Cloud searches for a match between your scoring rules and the issues linked to a case. If a match is found, a rule-based score is assigned.

You can view the assigned score on the **Cases** page.

### Case starring

To help you focus on the most important cases, you can star a case. Starring enables you to narrow down the scope of cases on the **Cases** page. Cortex Cloud identifies starred cases with a purple star.

You can star cases manually, or create a starring configuration. A starring configuration automatically categorizes and stars cases that contain issues with specific attributes. For example, you can define a starring configuration that stars all issues containing specific assets, hosts, or business application names. If an issue matches the attributes in the starring configuration, the issue and case linked to the issue are starred.

You can manage all starring configurations under Case & Issues → Case Configuration → **Starred Issues**. For more information see [Create a starring configuration](/cortex-cloud-posture-management/cases-and-issues/customize-cases-and-issues/create-a-starring-configuration.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 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-cloud-posture-management/cases-and-issues/case-concepts/case-scoring.md?ask=<question>&goal=<endgoal>
```

`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.