> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/exclusions-and-sla/scope-policy-and-sla-compliance.md).

# About Scope Policy and SLA Compliance

OX lets you define what is in scope and how fast you resolve it. Exclusion policy removes noise by excluding irrelevant applications, issues, detection rules, and policies from evaluation. SLA compliance sets time targets for what remains in scope, tracks progress, and flags overdue work.

Exclusions narrow the set of items that SLAs evaluate. When you exclude an entity, SLA clocks and breach calculations pause for it. When you remove an exclusion, evaluation resumes on the next scan under current SLA rules.

Management views in OX:

* [**Exclusions:**](https://docs.ox.security/exclusions-and-sla/scope-policy-and-sla-compliance/exclusions.md) Central list of out-of-scope entities. Search, expire, or remove exclusions. Excluded items do not count toward SLA timers, breaches, or reports until re-included.
* [**SLA management:**](https://docs.ox.security/exclusions-and-sla/scope-policy-and-sla-compliance/enforcing-sla.md) Configure targets, track remaining time, review breaches, and drill into root cause, affected assets, and remediation steps.


---

# 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://docs.ox.security/exclusions-and-sla/scope-policy-and-sla-compliance.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.
