> 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/data-library/infrastructure/glossary.md).

# Glossary

### Introduction

This glossary defines common terms and concepts related to infrastructure monitoring and compliance within Sprinto. Use this as a reference when navigating the Infra Systems, Monitoring, and Workflow Checks interfaces.

***

<table data-header-hidden><thead><tr><th width="209.06640625"></th><th></th></tr></thead><tbody><tr><td><strong>Term</strong></td><td><strong>Definition</strong></td></tr><tr><td><strong>Infrastructure System</strong></td><td>A connected cloud account or project, such as an AWS account, GCP project, or Azure subscription.</td></tr><tr><td><strong>Infra Owner</strong></td><td>The designated staff member responsible for resolving compliance tasks for a specific infrastructure system.</td></tr><tr><td><strong>Entity</strong></td><td>An individual infrastructure resource retrieved from a connected system (e.g., EC2 instance, Cloud SQL database).</td></tr><tr><td><strong>Classification</strong></td><td>The process of marking an entity as Production, Not Production, or Unclassified to determine the applicable compliance checks.</td></tr><tr><td><strong>Production</strong></td><td>An entity that processes, stores, or transmits sensitive or in-scope data and requires full compliance monitoring.</td></tr><tr><td><strong>Not Production</strong></td><td>An entity that handles test, staging, or non-sensitive data and is excluded from certain compliance checks.</td></tr><tr><td><strong>Unclassified</strong></td><td>The default state for newly synced entities that haven’t been categorised yet.</td></tr><tr><td><strong>Smart Classification</strong></td><td>A system-wide default classification applied to all entities in a given infrastructure system.</td></tr><tr><td><strong>Tag-based Classification</strong></td><td>A method of automatically classifying entities based on tags or labels defined in the cloud platform.</td></tr><tr><td><strong>Parent-based Classification</strong></td><td>A method where a child entity inherits classification from its parent entity.</td></tr><tr><td><strong>System Check</strong></td><td>An automated check that evaluates the security configuration of an integrated infrastructure system.</td></tr><tr><td><strong>Workflow Check</strong></td><td>A manual compliance check that requires evidence uploads at scheduled intervals.</td></tr><tr><td><strong>Monitoring Tab</strong></td><td>A central dashboard within the Infrastructure section that shows the status of all compliance checks.</td></tr><tr><td><strong>Active Checks</strong></td><td>Checks that are currently enforced and require regular review or resolution.</td></tr><tr><td><strong>Available Checks</strong></td><td>Checks that are defined but not yet enabled or actively monitored.</td></tr><tr><td><strong>Evidence Review</strong></td><td>A manual validation process to confirm that uploaded proof meets compliance standards.</td></tr><tr><td><strong>Task Drawer</strong></td><td>A context-specific panel showing resolution instructions and ownership for failing or due checks.</td></tr><tr><td><strong>Special Case</strong></td><td>A status applied to a check when standard resolution is not possible, accompanied by a justification and optional evidence.</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinto.com/data-library/infrastructure/glossary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
