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