> For the complete documentation index, see [llms.txt](https://intuitem.gitbook.io/ciso-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intuitem.gitbook.io/ciso-assistant/configuration/settings/vulnerability-sla.md).

# Vulnerability SLA policy

The Vulnerability SLA policy defines, by severity, how many days a vulnerability is allowed to remain open before it breaches the organisation's service-level agreement.

The platform uses this policy to compute remediation deadlines, surface overdue vulnerabilities, and feed SLA dashboards.

## Anchor

* **SLA anchor** — the date used as `day 0` when computing the deadline. Two options:
  * `detected_at` — the date the vulnerability was first recorded in CISO Assistant (default).
  * `published_date` — the date the vulnerability was publicly disclosed (relevant when working from CVE feeds).

The choice matters: `published_date` tightens deadlines for vulnerabilities that were known publicly before you imported them; `detected_at` gives a fresh clock starting from import.

## Deadlines by severity

For each severity level, set the number of days allowed to remediate. Leave a field empty (null) to mean *no policy at this severity*.

* **Critical** — typically the tightest (e.g. 7-14 days).
* **High** — typically 30 days.
* **Medium** — typically 60-90 days.
* **Low** — typically 180+ days, or unset.
* **Info** — usually unset; informational entries aren't on a clock.

## Behaviour

* Vulnerabilities whose `anchor_date + deadline_days` is in the past are flagged as **SLA breached**.
* Severity is read from the vulnerability record itself; the policy is a lookup, not a per-vulnerability field.
* Changes to the policy apply going forward *and* retroactively recompute the breach status of existing vulnerabilities.


---

# 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://intuitem.gitbook.io/ciso-assistant/configuration/settings/vulnerability-sla.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.