> 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/manage-non-integrating-infrastructure-providers.md).

# Manage Non-Integrating Infrastructure Providers

### Introduction

Not all infrastructure providers support direct integration with Sprinto. For such cases, Sprinto enables you to manage compliance using **workflow checks**. These checks mimic the behaviour of system checks by requiring periodic evidence uploads to validate your security posture.

You can manually configure workflow checks for encryption, backups, access controls, disaster recovery, and more.

***

### Common Use Cases

You should use workflow checks when:

* Your infrastructure provider is not listed in Sprinto’s supported integrations.
* You want to verify controls that require human review or manual evidence.
* You manage infrastructure externally and want to track compliance centrally.

***

### Steps to Create Workflow Checks

1. Navigate to **Data Library → Infrastructure**.
2. Go to the **Infra systems** tab.
3. Click **Add workflow check**.
4. Choose one of the following options:
   * **From Template** – Prebuilt checks like “Database backup is done regularly”
   * **Single workflow check** – Add a custom check for one system
   * **Bulk upload** – Add multiple checks at once using CSV

***

### Configure Workflow Check Details

For each check, provide the following information:

<table data-header-hidden><thead><tr><th width="187.12890625"></th><th></th></tr></thead><tbody><tr><td><strong>Field</strong></td><td><strong>Description</strong></td></tr><tr><td><strong>Title</strong></td><td>Name of the compliance check</td></tr><tr><td><strong>Description</strong></td><td>Why the check is required; what it verifies</td></tr><tr><td><strong>Instructions</strong></td><td>Steps to perform the check or generate the evidence</td></tr><tr><td><strong>Area</strong></td><td>Relevant compliance category (e.g., Infrastructure, Access)</td></tr><tr><td><strong>Activates on</strong></td><td>The date from which the check should begin</td></tr><tr><td><strong>Runs on</strong></td><td>Frequency of the check (e.g., Monthly, Quarterly)</td></tr><tr><td><strong>Assigned to</strong></td><td>Person responsible for performing the check</td></tr><tr><td><strong>Evidence review</strong></td><td>Toggle ON if evidence must be reviewed before passing the check</td></tr></tbody></table>

Once complete, click **Add Check**.

***

### Example Workflow Checks

<table data-header-hidden><thead><tr><th width="253.0625"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Check</strong></td><td><strong>Purpose</strong></td><td><strong>Evidence Required</strong></td></tr><tr><td>Database backup is done regularly</td><td>Ensure critical data is backed up</td><td>Screenshot of backup schedule</td></tr><tr><td>Database encryption is enabled</td><td>Verify encryption is turned on</td><td>Screenshot of encryption setting</td></tr><tr><td>Data backup restoration tested</td><td>Validate that recovery works</td><td>Report from test or exercise</td></tr><tr><td>Disaster recovery plan in place</td><td>Confirm DR preparedness</td><td>Copy of policy and test results</td></tr><tr><td>Production server CPUs are monitored</td><td>Ensure availability monitoring is enabled</td><td>Screenshot of monitoring dashboard</td></tr></tbody></table>

***

### After Adding the Check

* The check appears under the **Monitoring** tab → **Active checks**.
* Assigned owners receive email reminders when the check is due.
* Owners must **upload evidence** or mark the check as a **special case** to move it to “Passing.”

{% hint style="info" %}
Sprinto resets the check status on the next run date, enforcing ongoing compliance.
{% endhint %}


---

# 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/manage-non-integrating-infrastructure-providers.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.
