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

# Glossary

Definitions of key terms used in the Frameworks section of Sprinto.

This glossary explains the key terms used in the Frameworks section to help you understand and use the feature effectively.

<table><thead><tr><th width="143.26171875">Term</th><th>Definition</th></tr></thead><tbody><tr><td><strong>Framework</strong></td><td>A structured set of compliance requirements, such as SOC 2, ISO 27001, PCI DSS, or a custom framework. Used to guide and measure compliance readiness.</td></tr><tr><td><strong>Criterion (Criteria)</strong></td><td>An individual compliance requirement within a framework. Criteria are linked to controls for evidence collection and monitoring.</td></tr><tr><td><strong>Enabled Frameworks</strong></td><td>Frameworks that are currently active in your account and contribute to compliance tracking.</td></tr><tr><td><strong>Available Frameworks</strong></td><td>Frameworks that are not yet enabled but can be added to your compliance setup.</td></tr><tr><td><strong>Control</strong></td><td>A specific action, process, or configuration that satisfies a compliance requirement. Can be automated or workflow-based.</td></tr><tr><td><strong>Automated Check</strong></td><td>A system-run validation to confirm compliance (for example, checking if encryption is enabled).</td></tr><tr><td><strong>Workflow Check</strong></td><td>A manual verification process requiring evidence submission or review by assigned staff.</td></tr><tr><td><strong>Scope</strong></td><td>Indicates whether a criterion is applicable (<em>In scope</em>) or not applicable (<em>Not in scope</em>) to your organisation.</td></tr><tr><td><strong>Readiness</strong></td><td>The percentage indicating how much of a framework’s in-scope criteria are satisfied by mapped controls and passing checks.</td></tr><tr><td><strong>Map Controls</strong></td><td>The process of linking relevant controls to a framework’s criteria to satisfy compliance requirements.</td></tr><tr><td><strong>Unmap Controls</strong></td><td>The process of removing linked controls from a criterion.</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/frameworks/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.