# Glossary

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>
