Source: https://atomic-works-test.docs-staging.pageloop.ai/data-library/incidents/glossary

# Glossary

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

TermDefinitionIncidentAny security, operational, or compliance-related event that could impact data confidentiality, integrity, or availability.Incident Management System (IMS)A system used to detect, log, and resolve incidents. Sprinto can function as an IMS or integrate with third-party tools.Data LossThe unintended or unauthorised exposure, access, or destruction of sensitive information such as personal data, PHI, or cardholder data.Employee-reported IncidentAn incident reported manually by a staff member via the Sprinto portal or a configured email address.Monitoring CheckA system-generated validation that confirms whether an incident has been resolved and compliance actions (such as data loss reporting) are complete.Failing CheckA check that has not been fulfilled due to unresolved tickets, missing evidence, or unacknowledged data loss.Passing CheckA check that has been fulfilled and all related actions have been completed successfully.Incident SeverityThe level of criticality associated with an incident (e.g. Low, Medium, High) as assigned during reporting.Status HistoryA record of changes to a check's state (Failing or Passing), including timestamps and evidence uploaded.Special CaseAn incident or check that is manually marked as out of scope for compliance, and therefore marked as passing.Integration IssueAn error in syncing or retrieving data from a connected third-party incident management system.Incident Source TabA dedicated interface under Incidents for each integrated system (e.g. PagerDuty, Jira), listing its associated incidents.