> 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/work-with-slas/sla-overview.md).

# SLA Overview

Cortex XSOAR supports specific fields for managing SLAs and timers.

SLAs are an important aspect of case management. You can incorporate SLA fields in your cases so you can view how much time is left before the SLA becomes past due, as well as configure actions to take in the event that the SLA does pass.

In addition, you can now view the number of cases that are at risk of passing the SLA, or are already late, using pre-configured widgets. The widgets present information based on the default threshold, [which can be configured globally](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/work-with-slas/configure-the-global-risk-threshold.md).

**Present SLAs in Incident Summary Layouts**

Once you have configured the SLA fields and timers, your incident summary screens will display information about the status of the SLA, if any of the SLAs are past due, and if so, by how much.

![SLA\_Incident\_Summary\_Screen.png](/files/7eCvj3jpmUfWou5BxKJD)

In the image above, for example, we see that the timers for several of the fields are in various states. **`Detection SLA`** is past due, while **`Remediation SLA`** has nearly 5 days remaining.

**Customize CSV Reports for SLA Fields**

You can add SLA specific information to your CSV reports. Edit the table columns field in the JSON report to include the SLA data that you want.

For example, assuming that you have an existing timer field named **`myslatimer`**, we can use the following options as CSV columns:

* **`myslatimer`**: displays a summary of the timer status and SLA.
* **`myslatimer.runStatus`**: displays a run status of the current timer.
* **`myslatimer.totalElapsed`**: displays the total elapsed time, in seconds, of the current timer. If the timer has ended, it displays the total duration.


---

# 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/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/work-with-slas/sla-overview.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.