> 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/dashboard-actions/advanced-infrastructure-checks-in-sprinto.md).

# Advanced Infrastructure Checks in Sprinto

Sprinto has introduced a new set of **in-depth system checks** to enhance cloud infrastructure monitoring. These checks provide more granular visibility into your cloud configurations and expand the scope of automated compliance detection.

The checks are currently available for **Google Cloud Platform (GCP)** and are applied automatically to eligible infrastructure services when enabled.

***

### What Happens When You Enable These Checks

When the new checks are activated, Sprinto performs the following actions:

#### 1. Configuration Analysis

Sprinto fetches the current configuration details of your integrated infrastructure accounts and analyses them against the latest check definitions.

#### 2. Check Activation

If any configuration does not meet the required security standard, Sprinto activates the relevant check against the affected resource.

#### 3. Continuous Monitoring

Once you fix the flagged configuration (for example, by enabling encryption or disabling a risky feature), Sprinto automatically detects the update and marks the check as **Passing**.

***

### How to Enable the New Checks

You can enable the advanced checks using either of the following methods:

* Navigate to the **Data Library > Infrastructure** page in the Sprinto admin portal and click **Enable Now** on the banner.

<figure><img src="/files/H0goElY3G6OxtBD6lF4N" alt="" width="563"><figcaption></figcaption></figure>

* Alternatively, click **Enable** from the notification email sent to your organisation’s administrators.

For assistance, contact [Sprinto Support](mailto:www.support@sprinto.com).

***

### Newly Introduced Checks for GCP

| **Sprinto Check**                                                    | **Description**                                            |
| -------------------------------------------------------------------- | ---------------------------------------------------------- |
| Ensure GKE Kubernetes Web UI (Dashboard) is disabled                 | Prevents exposure of the web UI interface for GKE clusters |
| Ensure GKE Metadata Server is enabled                                | Validates the use of metadata server for GKE workloads     |
| Ensure Kubernetes clusters have logging and cloud monitoring enabled | Enforces observability for clusters                        |
| Ensure Bigtable Instances are encrypted                              | Verifies that Bigtable data is encrypted at rest           |
| Ensure Bigtable cluster CPU load is monitored                        | Tracks CPU usage to detect resource bottlenecks            |
| Ensure Bigtable cluster storage utilisation is monitored             | Ensures storage growth is being tracked                    |
| Ensure user data is encrypted at rest                                | Validates encryption for all GCP-hosted user data          |

***

Let me know if you’d like to:

* Add this to the “What’s New” index for Infrastructure
* Link this under the Monitoring or Dashboard Actions section
* Draft a similar announcement for other providers (e.g., AWS, Azure) once new checks are introduced for them


---

# 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/dashboard-actions/advanced-infrastructure-checks-in-sprinto.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.