Service levels
Set the deadlines and review cadences your organization works to: how long a security finding may stay open, how often suppliers are reviewed, and more.
What it is
A service level is a deadline or a cadence your organization commits to, such as "fix a critical finding within 7 days". The Service levels tab is the one place those numbers live. Dashboards, lists, reminders and generated policies all read them from here, so the number in your policy is the number Noru measures against.
Every target starts at a default. You do not have to set anything: change a value only when your policy or a customer contract says something different.
Where to find it
SettingsService levelsIt sits under Compliance, next to Frameworks.
The targets
| Group | Target | Default |
|---|---|---|
| Security findings | Critical | 7 days |
| Security findings | High | 30 days |
| Security findings | Medium | 90 days |
| Security findings | Low | 180 days |
| Supplier reviews | Critical tier | 12 months |
| Supplier reviews | High tier | 12 months |
| Supplier reviews | Medium tier | 24 months |
| Supplier reviews | Low tier | None |
| Access reviews | Follow-up on decisions | 14 days |
| Policies | Review interval | 12 months |
| Evidence | Uploaded evidence validity | 365 days |
Key actions
Change a target
Type the new value in the row. It saves by itself; the top bar shows when it is saved. Reset returns a changed row to its default.
A supplier tier can have no review cadence: clear the field to set it to none.
Meet a framework's limit
Most frameworks, including SOC 2 and ISO 27001, let you choose your own timeframes and then audit you against them. A few set a limit. When one of your enabled frameworks does, the row says so, for example "PCI DSS 6.3.3 requires 30 days or less". If your value is looser than the limit the row is flagged, and Use 30 days tightens it in one click. Noru never changes your value on its own.
How security finding deadlines work
- A finding's clock starts when it was observed, or when it was recorded if there is no observation date.
- Its deadline is that start plus the target for its severity. A supplier finding with its own due date keeps that date.
- Changing a target moves the deadline of every open finding straight away.
- Findings that are already closed keep the deadline they were closed under, so a new target never rewrites who was on time.
- The Overview shows, per severity, how many open findings are past or nearing their deadline, and the share of findings fixed within their deadline over the last 90 days with the average time to fix. Only resolved findings count; accepted and false-positive findings are left out.
Tips and gotchas
- Policies drafted after a change state the new numbers. Policies you already have are not rewritten: review them when you change a target.
- A policy with its own review frequency keeps it. The review interval here applies only to policies without one.
- Evidence with an expiry date of its own keeps it.
For developers
GET /v1/service-levels and PATCH /v1/service-levels read and change the
same values, as do the getServiceLevels and updateServiceLevels MCP tools.
See the MCP server page.
Related
Last updated on