Define Your Team's Service-Level Agreement
Set targets for how quickly your team commits to remediating findings, and track real performance against them.
A service-level agreement (SLA) in Mondoo is a target for how quickly your team commits to remediating security findings. Mondoo tracks your team's actual mean time to remediate (MTTR) and compares it against the targets you've set, so you can see how you're doing at a glance.
You can set SLAs for each space, or set them once for the whole organization so every space works to the same deadlines.
For how those findings are prioritized and driven to resolution, see Track and fix findings.
Review SLA performance
In the left navigation, expand Findings and select SLAs.

SLAs apply to vulnerability findings. The page counts only findings that are nearing or past their SLA deadline, so a finding that's still well inside its window doesn't appear here. The header shows how many findings that is.
Three cards at the top of the page break the numbers down by risk level (Critical, High, Medium, and Low):
- Overdue counts findings past their SLA deadline.
- Due soon counts findings whose deadline is inside the warning window.
- Mean time to resolve shows the team's MTTR for each risk level next to that level's target in days.
Select a row in the Overdue or Due soon card to filter the table to that risk level and SLA status, sorted by that column. Select the same row again to clear the filter.
Below the cards, a table lists the findings that are nearing or past their SLA. For each finding it shows:
- Its SLA Status: Overdue if any affected asset is past the deadline, otherwise Due Soon
- How many affected assets are Due Soon and how many are Overdue
- The number of Affected Assets and when the finding was First Detected
Use the search box to filter the list, for example by risk rating or by SLA status. To download the list as CSV, JSON, or XLSX, open the menu next to the search box.
If you can change the space's SLAs, select Manage SLAs to open its SLA settings. The button doesn't appear when the organization sets the SLAs.
Default targets
| Risk level | Days to resolve | Warning threshold (days) |
|---|---|---|
| Critical | 30 | 23 |
| High | 30 | 23 |
| Medium | 60 | 53 |
| Low | 90 | 83 |
By default, Mondoo uses the Mondoo risk score to decide a finding's risk level and starts the SLA clock when it first detects a vulnerability.
Set SLAs for a space
Only team members with Owner, Editor, or SLA Manager access to the space can change SLA settings.
If your organization sets SLAs, the space's Service Level Control page shows the organization's values read-only, with a link to the organization SLA settings. To change them, see Set SLAs for the whole organization.
-
Navigate to the space.
-
In the left navigation, expand Security Model, then select Service Level Control.

-
Under Scoring Method, choose the score Mondoo uses to decide each finding's risk level:
- Mondoo Risk Score (recommended) combines CVSS severity with exploitability, blast radius, asset importance, and exposure.
- CVSS Score uses the raw CVSS base score from the CVE record. Choose it when your program is tied to industry-standard CVSS bands.
-
Under Start Date, choose when the SLA clock starts on a newly discovered vulnerability:
- CVE Detected (recommended) starts the clock when Mondoo first detects the vulnerability.
- CVE Published starts the clock when the CVE was first publicly disclosed. Newly scanned assets may already be past their deadline.
-
Under Deadlines, set two numbers for each risk level:
- Days to resolve is how long your team has to fix a finding before it's overdue.
- Warning threshold (days) is when Mondoo starts flagging a finding as due soon. It must be less than Days to resolve.
-
Select SAVE CHANGES.
To see the findings these targets apply to, select VIEW SLA FINDINGS at the top of the page.
Set SLAs for the whole organization
Organization SLAs apply to every space in the organization, including spaces created later, and spaces can't override them. Set them when remediation deadlines are an organization policy rather than a choice each team makes.
Only team members with Owner, Editor, or SLA Manager access to the organization can set organization SLAs.
-
Navigate to the organization.
-
In the left navigation, expand Security Model, then select Service Level Control.
Until you save organization SLAs, each space uses its own settings, and the page shows the Mondoo defaults as a starting point.
-
Choose the Scoring Method, the Start Date, and the Deadlines for each risk level. The settings are the same as for a space; see Set SLAs for a space.
-
Select APPLY TO ALL SPACES, then confirm.
Findings pick up the new deadlines on each asset's next scan. To change the organization SLAs later, edit the values and select SAVE CHANGES.
To hand SLAs back to the spaces, select REMOVE ORGANIZATION SLAS and confirm. Each space returns to its own SLA settings, or to the Mondoo defaults if it never set any.