> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/incidents/glossary.md).

# Glossary

This glossary defines key terms and concepts used in the *Incidents* section of Sprinto. Use it as a reference to understand the terminology related to incident tracking, data loss, and compliance monitoring.

<table data-header-hidden><thead><tr><th width="159.37890625"></th><th></th></tr></thead><tbody><tr><td><strong>Term</strong></td><td><strong>Definition</strong></td></tr><tr><td><strong>Incident</strong></td><td>Any security, operational, or compliance-related event that could impact data confidentiality, integrity, or availability.</td></tr><tr><td><strong>Incident Management System (IMS)</strong></td><td>A system used to detect, log, and resolve incidents. Sprinto can function as an IMS or integrate with third-party tools.</td></tr><tr><td><strong>Data Loss</strong></td><td>The unintended or unauthorised exposure, access, or destruction of sensitive information such as personal data, PHI, or cardholder data.</td></tr><tr><td><strong>Employee-reported Incident</strong></td><td>An incident reported manually by a staff member via the Sprinto portal or a configured email address.</td></tr><tr><td><strong>Monitoring Check</strong></td><td>A system-generated validation that confirms whether an incident has been resolved and compliance actions (such as data loss reporting) are complete.</td></tr><tr><td><strong>Failing Check</strong></td><td>A check that has not been fulfilled due to unresolved tickets, missing evidence, or unacknowledged data loss.</td></tr><tr><td><strong>Passing Check</strong></td><td>A check that has been fulfilled and all related actions have been completed successfully.</td></tr><tr><td><strong>Incident Severity</strong></td><td>The level of criticality associated with an incident (e.g. Low, Medium, High) as assigned during reporting.</td></tr><tr><td><strong>Status History</strong></td><td>A record of changes to a check's state (Failing or Passing), including timestamps and evidence uploaded.</td></tr><tr><td><strong>Special Case</strong></td><td>An incident or check that is manually marked as out of scope for compliance, and therefore marked as passing.</td></tr><tr><td><strong>Integration Issue</strong></td><td>An error in syncing or retrieving data from a connected third-party incident management system.</td></tr><tr><td><strong>Incident Source Tab</strong></td><td>A dedicated interface under <em>Incidents</em> for each integrated system (e.g. PagerDuty, Jira), listing its associated incidents.</td></tr></tbody></table>


---

# 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:

```
GET https://docs.sprinto.com/data-library/incidents/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.