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

# Glossary

Glossary of key terms used in the Controls section of Sprinto’s Compliance module.

This glossary explains key terms used in the Controls section of Sprinto.

<table><thead><tr><th width="162.57421875">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Control</strong></td><td>A specific measure or safeguard implemented to meet a compliance, security, or operational requirement. Controls can be mapped to monitoring checks and compliance frameworks.</td></tr><tr><td><strong>Control Number</strong></td><td>A unique identifier assigned to a control for tracking and reference purposes.</td></tr><tr><td><strong>Control Owner</strong></td><td>The person responsible for implementing, maintaining, and ensuring the effectiveness of a control.</td></tr><tr><td><strong>Domain</strong></td><td>A compliance category or area (for example, Personnel Security, Access Control) under which a control is classified.</td></tr><tr><td><strong>Enabled Controls</strong></td><td>Controls that are active and linked to applicable monitoring checks and frameworks.</td></tr><tr><td><strong>Disabled Controls</strong></td><td>Controls that are inactive and excluded from compliance monitoring, but retained for reference or audit purposes.</td></tr><tr><td><strong>Monitoring</strong></td><td>The process of linking automated or workflow checks to a control to verify its effectiveness.</td></tr><tr><td><strong>Mapped Checks</strong></td><td>Monitoring checks currently linked to a control for compliance validation.</td></tr><tr><td><strong>All Checks</strong></td><td>The complete list of monitoring checks available in the system that can be linked to controls.</td></tr><tr><td><strong>Mapped Frameworks</strong></td><td>Compliance frameworks associated with a control to demonstrate alignment with specific standards or regulations.</td></tr><tr><td><strong>Framework Criteria</strong></td><td>Specific clauses or requirements from a compliance framework that can be mapped to a control.</td></tr><tr><td><strong>Bulk Import Controls</strong></td><td>A method to add multiple controls at once by uploading a pre-formatted CSV file.</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/compliance/controls/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.