How to resolve Sprinto check for resolving vulnerability within the SLA

Configure and manage SLA timelines for vulnerability checks in Sprinto to control escalation, remediation deadlines, and compliance outcomes.

Sprinto allows you to define and manage remediation SLAs for vulnerability-related automated checks. These SLAs determine how long vulnerabilities can remain unresolved before tasks move through Due, Critical, and Failing states and trigger escalations.

This article explains how to view and update SLA timelines for vulnerability checks using the latest Monitoring experience in Sprinto.

SLA configuration is currently supported for a limited set of vulnerability checks. Availability depends on the check type.

---

What you can configure

For supported vulnerability checks, you can configure:

• The time allowed to resolve vulnerabilities for each severity level:

  • Critical

  • High

  • Moderate

  • Low

• When a task:

  • Becomes due

  • Escalates

  • Breaches the SLA and moves to a failing state

Each severity level is configured independently.

The following checks get activated upon vulnerability detection based on your integrated monitoring service on Sprinto:

Monitoring service	Sprinto check
Dependabot	Dependabot vulnerability alert should be resolved within SLA
SLScan	SLScan vulnerability alert should be resolved within SLA
AWS Inspector	AWS Inspector vulnerability alert should be resolved within SLA
Google Security Center	Google Security Center vulnerability alert should be resolved within SLA
SonarQube	SonarQube vulnerability alert should be resolved within SLA
RapidFort	RapidFort vulnerability alert should be resolved within SLA
SonarCloud	SonarCloud vulnerability alert should be resolved within SLA
Semgrep	Semgrep vulnerability alert should be resolved within SLA

Before you begin

• You must have access to the Monitoring module.

• The vulnerability check must be enabled and actively monitoring entities.

• SLA settings apply to all tasks created by the selected check.

---

Update SLA for a vulnerability check (recommended path)

This is the primary and most direct way to manage SLAs.

Step 1: Go to Monitoring

1. Log in to the Sprinto dashboard.

2. Navigate to Monitoring from the left navigation.

3. Go to the Automated checks tab.

---

Step 2: Filter for vulnerability checks

1. Use the Area filter.

2. Select Vulnerabilities.

This displays all vulnerability-related automated checks that support SLA configuration.

---

Step 3: Open the required check

1. Select the vulnerability check you want to update (for example, AWS Inspector vulnerability alert should be resolved within SLA).

2. You are taken to the check details page.

---

Step 4: Edit SLA by severity

1. Scroll to Tasks created by this check.

2. Expand the drawer for the required severity:

   • Critical

   • High

   • Moderate

   • Low

3. Locate the SLA breach duration.

4. Click the Edit icon next to the duration.

---

Step 5: Update the SLA

1. In the Manage tasks SLA drawer:

   • Update the number of days for remediation.

   • Review how the task lifecycle is calculated:

     • Due period

     • Escalation timing

     • SLA breach

2. Click Save.

Repeat these steps for each severity level you want to update.

---

Alternate entry path: From the Vulnerabilities context

You can also reach the same SLA configuration from a vulnerability record.

How this works

1. Navigate to Data Library → Vulnerabilities.

2. Open any vulnerability that is linked to an automated SLA-based check.

3. Select the associated check.

1. You are taken to the Check Details page.

2. Repeat the same steps from here.

Both entry paths lead to the same SLA configuration screen.

---

Important notes

• SLA edits affect all tasks generated by that check, not individual vulnerabilities.

• If a check is disabled or has no monitored entities, SLA editing options may not be visible.

• Changes take effect immediately for newly evaluated tasks.