Monitor Incident Checks

Track incident resolution and data loss reporting using Sprinto’s automated monitoring checks for complete compliance visibility.

Sprinto automatically generates and tracks monitoring checks for all integrated incident sources to ensure timely incident resolution and compliance with security frameworks. These checks validate whether incident tickets have been closed and if associated data loss has been reported to the appropriate stakeholders.

All active and failing checks are displayed in the Monitoring tab within the Incidents section.

---

View Monitoring Checks

1. Go to Data Library > Incidents > Monitoring.

2. The interface displays:

   • Check name

   • Source system (e.g. Jira, Microsoft Defender, PagerDuty)

   • Current status (Passing, Failing, Not active)

   • Days to fail/critical

   • Associated zones

   • Status history

Monitoring is consistent across all incident source tabs and follows the same filtering and action logic.

---

Filter and Sort Checks

Use the filters at the top to narrow down your view:

• Check Status: Passing, Failing, Not active

• Severity Tags: Due, Critical

• Zones: Filter by business unit or functional area

• Time-based: Days until check becomes failing or critical

You can also use the Search bar to locate checks by name or source.

---

Add New Checks

You can define additional incident checks based on workflows and team-specific requirements.

1. Click Add check at the top right.

2. Choose one of the following methods:

   • From template: Use predefined compliance workflows.

   • Add single check: Manually define a specific incident check.

   • Bulk upload: Import multiple checks using the provided spreadsheet format.

3. Fill in the necessary details and assign the check to a zone or control group.

4. Click Create to activate the check.

---

View Status History

To review historical changes in a check’s status:

1. Click the Status history icon next to any check.

2. A side panel opens showing:

   • Timestamps of status changes (Failing/Passing)

   • Associated actions taken

   • Evidence (if any)

3. Click Download history to export this log for audits.