> 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/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/change-the-display-name-of-security-incidents.md).

# Change the Display Name of Security Incidents

Change security incident display names in Cortex XSOAR 6.12.

In Cortex XSOAR, the default term used for a security incident is **`incident`**. You can change the term that is used for security incidents from a predefined list of options. This term displays in reports, menus, tables, and commands (local and server) in Cortex XSOAR.

When you change the display name of a security incident, the following commands are deprecated and are replaced with commands with the new name:

* **`associateIndicatorstoIncident`**
* **`associateIndicatortoIncident`**
* **`createNewIncidents`**
* **`linkIncidents`**
* **`relatedIncidents`**
* **`setIncident`**
* **`unAssociateIndicatorstoIncident`**
* **`unAssociateIndicatortoIncident`**

For example, if you change the security incident name to **`Cases`**, the **`setIncident`** command appears as **`setIncident (Deprecated)`** and the **`setCase`** command replaces it. You can still use the deprecated command but we recommend replacing the command for clarity.

The term you select does not change the display name for content-related items, such as playbooks, integrations, scripts, dashboards, or the API.

{% hint style="info" %}

### Note

(Multi-Tenant) When changing the display name of security incidents, the URL link which contains **`/incident`** may not work properly. For example, when changing the **incident** to **case**, sometimes the links are formed with the\*\*`/incident`\*\* URL and not with the **`/case`** URL. This can usually be corrected by clearing the browser cache and reloading the page.
{% endhint %}

1. Navigate to Settings → About → **Troubleshooting**.
2. In the **Server Configuration** section, click **Add Server Configuration**.
3. In the **Key** field type **`UI.term.incident`**.
4. In the **Value** field enter the value for the term. In the following table, the Command column displays the correct command to use.

   | Value | Term                | Command           |
   | ----- | ------------------- | ----------------- |
   | 0     | Incidents (default) | **`setIncident`** |
   | 1     | Cases               | **`setCase`**     |
   | 2     | Alerts              | **`setAlert`**    |
   | 3     | Events              | **`setEvent`**    |
   | 4     | Plays               | **`setPlay`**     |
   | 5     | Tickets             | **`setTicket`**   |
   | 6     | Issues              | **`setIssue`**    |
5. Restart the server.


---

# 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/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/change-the-display-name-of-security-incidents.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.