> 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/monitoring/glossary.md).

# Glossary

Understand key terms used in Sprinto’s Monitoring dashboard, including checks, task statuses, providers, and compliance mappings.

This glossary defines important terms and labels used in the Monitoring section of Sprinto. Use this as a quick reference to understand the terminology associated with compliance checks, workflows, and system integrations.

***

<table><thead><tr><th width="165.4140625">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Check</strong></td><td>A monitor that tracks a specific compliance task. Can be automated (via integration) or workflow-based (manual).</td></tr><tr><td><strong>Workflow Check</strong></td><td>A check that requires user input, evidence upload, or task completion on a schedule.</td></tr><tr><td><strong>Automated Check</strong></td><td>A check that pulls data from an integration and evaluates compliance automatically.</td></tr><tr><td><strong>Entity</strong></td><td>The system, user, or asset being evaluated (e.g., EC2 instance, staff member).</td></tr><tr><td><strong>Task</strong></td><td>A unit of work that needs to be completed or verified under a check.</td></tr><tr><td><strong>Task Status</strong></td><td>The compliance outcome of a task — Passed, Due, Failing, or Critical.</td></tr><tr><td><strong>Passed</strong></td><td>The task met all compliance requirements; no action is needed.</td></tr><tr><td><strong>Due</strong></td><td>The task has not yet been completed and is approaching its deadline.</td></tr><tr><td><strong>Failing</strong></td><td>The task failed a compliance condition or was not completed in time.</td></tr><tr><td><strong>Critical</strong></td><td>A high-severity failure that poses an immediate compliance risk.</td></tr><tr><td><strong>Check Owner</strong></td><td>The user responsible for completing or overseeing a check.</td></tr><tr><td><strong>Reviewer</strong></td><td>The user assigned to review and approve a workflow check submission.</td></tr><tr><td><strong>Provider</strong></td><td>The integration source for an automated check (e.g., AWS, GitHub, Azure).</td></tr><tr><td><strong>Area</strong></td><td>The compliance domain associated with a check (e.g., People, Infrastructure, Risk).</td></tr><tr><td><strong>Framework</strong></td><td>A compliance standard or model (e.g., SOC 2, ISO 27001) against which checks are mapped.</td></tr><tr><td><strong>Control</strong></td><td>A specific policy or requirement under a framework that the check supports.</td></tr><tr><td><strong>Active Check</strong></td><td>A monitor currently enabled and under evaluation.</td></tr><tr><td><strong>Available Check</strong></td><td>A predefined monitor that can be enabled based on integration or data availability.</td></tr><tr><td><strong>Disabled Check</strong></td><td>A monitor that has been turned off or archived.</td></tr><tr><td><strong>Monitoring Table</strong></td><td>The dashboard view listing all compliance checks along with their status and metadata.</td></tr><tr><td><strong>View &#x26; Fix</strong></td><td>Action button that opens the Check Details page for a failing or due check.</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/monitoring/glossary.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
