> 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/frequently-asked-questions.md).

# Frequently Asked Questions

### Introduction

This page addresses common questions related to infrastructure integration, classification, monitoring, and check resolution in Sprinto.

***

#### 1. What is an infrastructure system in Sprinto?

An infrastructure system refers to a cloud provider account integrated with Sprinto. For example, an AWS account, Azure subscription, or GCP project is treated as an infrastructure system.

***

#### 2. What happens after I integrate an infrastructure provider?

Once integrated, Sprinto starts syncing metadata from your cloud account. You can then classify the retrieved entities and monitor them using system and workflow checks.

***

#### 3. How do I assign ownership for a specific infrastructure system?

Click **Configure** from the Infra systems tab, then select **Change** under the Infra Owner field. Choose a staff member with appropriate privileges and click **Save**.

***

#### 4. What types of classification are supported for infrastructure entities?

Sprinto supports the following classification methods:

* Manual classification
* Tag-based classification
* Parent-based classification
* System-level default classification (Smart Classification)

***

#### 5. What happens if an entity remains unclassified?

Unclassified entities are excluded from compliance checks. You must classify them manually, through tags, or via parent relationship to enable monitoring.

***

#### 6. How can I monitor compliance for systems that don’t integrate with Sprinto?

Use workflow checks to manually validate compliance. These checks allow you to submit evidence on a defined schedule. You can add them via the **Add workflow check** option.

***

#### 7. What is the difference between system checks and workflow checks?

<table><thead><tr><th width="177.25390625">Check Type</th><th>Description</th></tr></thead><tbody><tr><td>System checks</td><td>Automatically triggered based on configurations in your cloud provider.</td></tr><tr><td>Workflow checks</td><td>Manually triggered and require evidence upload to validate compliance.</td></tr></tbody></table>

***

#### 8. Can I update API keys for integrated cloud services?

Yes. For supported providers like Azure and GCP, go to **Settings → Integrations → Active**, click **Manage**, and update the credentials without affecting the connection.

***

#### 9. How do I know which checks are failing?

Go to the **Monitoring** tab to view all checks and their statuses (e.g., Passing, Failing, Due). Click any check to see more details and resolution steps.

***

#### 10. What if a Sprinto check cannot be resolved directly?

If the check cannot be resolved due to provider limitations, you can:

* Upload manual evidence
* Mark the check as a special case with a justification


---

# 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/frequently-asked-questions.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.
