> 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/monitors/governance-and-compliance-monitors/how-to-resolve-sprinto-check-for-classifying-infra-entities.md).

# How to resolve Sprinto check for classifying infra entities

### About

Sprinto check: Infra Entity Classification Required

The above Sprinto check fails for any unclassified infra entity added from the integrated infrastructure service providers.

### Purpose

The primary purpose behind infra-entities classification is to identify the critical infra-entities that store and process critical data that directly impact an organization’s operations and map the required security controls to evaluate their compliance posture. 

You can classify an infra entity as “Production” or “Non-production” using one of the available methods. Sprinto maps the automated Sprinto checks against any production-marked infra entity and helps you determine their compliance posture against your enabled frameworks. 

### Resolving the Check

To resolve the above Sprinto check, classify infra entities added from each integrated infrastructure service provider on the[ Infrastructure](https://app.sprinto.com/app/admin/infraStructure/infraSystems) module.

You can use one of the following methods to classify infra entities:

* [Classify infra entities by tags](https://docs.sprinto.com/monitors/governance-and-compliance-monitors/pages/etBFr5hW9KjowB9qlP57#id-3.-tag-based-classification)
* [Classify infra entity manually](https://docs.sprinto.com/monitors/governance-and-compliance-monitors/pages/etBFr5hW9KjowB9qlP57#id-2.-manual-classification-per-entity)

Please contact [Sprinto Support](mailto:www.suppport@sprinto.com) if you have queries related to the Sprinto check or need any assistance.


---

# 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/monitors/governance-and-compliance-monitors/how-to-resolve-sprinto-check-for-classifying-infra-entities.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.