> 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-infra-entity-should-be-classified.md).

# How to resolve Infra entity should be classified

One of the most common compliance requirements is to have an inventory of all your infra-assets & to classify these assets based on the kind of information they hold. 

*\<This is usually mentioned as a part of the organization's Data-Classification policy>*

In Sprinto, all your infra-assets are listed under the **Infrastructure** section. As an organization undergoing compliance, you are required to classify these assets as Production / Not Production.

Based on the asset type & classification provided, Sprinto will check for additional compliance-related requirements such as encryption for storage assets & alarms for computing assets.

You can use **tags** to automatically classify assets on **AWS** and **Azure**, and **labels** to do the same on **GCP**.

Use these Key / Value pairs:\
\-------------------------------------

**Key**: sprinto **Value**: prod       *\<For Production assets>*

**Key**: sprinto **Value**: notprod  *\<For Not-Production assets>*

*Apart from the above Sprinto will also recognize whether an asset is prod or non-prod if the tag is set as env or environment.*

For eg: Key: env and Value: prod

For eg: Key: environment and Value: prod

Thank you for reading. You can write to <support@sprinto.com> for any additional queries.


---

# 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-infra-entity-should-be-classified.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.