Resolve Integration Errors

Integrations play a crucial role in Sprinto's operations, as our continuous monitoring checks rely on data flows through these integrations. This guide will help you review and resolve integration errors in your Sprinto account.

Reasons for Integration Errors

Integration errors can occur in the following two scenarios:

1. Building a New Integration

You may encounter an integration error while integrating a new service provider on Sprinto due to the following reasons:

• Permissions Grants: Sprinto requires permissions from multiple resources from the integrating service provider for its operations. Often, these are read-only permissions to monitor security configurations and ensure compliance. Failure to grant any required permissions may lead to an integration error. Refer to Sprinto’s permission utilization for more details.

• Invalid Access: You need certain platform-specific privileges to grant resource permissions or access to Sprinto while integrating the service on your Sprinto account. Lacking these privileges may lead to an integration error.

• Expired Credentials: Many service providers have predefined credential expiry periods for better security. Using expired credentials during the integration process can result in an integration error.

For any encountered error during building a new integration, Sprinto showcases the following error message with possible scenarios that lead to the error.

We recommend referring to our detailed integration guides or contacting our Support team for assistance while performing integrations on your Sprinto account.

2. Issues with Existing Integrations

Integration errors can also occur with existing active integrations due to the following reasons:

• Outdated Credentials: If the credentials used for integration expire or become invalid, it can cause integration errors.

• Change in Permissions Structure: If the service provider changes the required permissions or access structure, it may lead to integration errors for existing integrations.

Sprinto shows the following error message on the integration page for any error encountered on an existing integration. Refer to the “Resolving errors” section below for detailed steps.

Reviewing Integration Errors

Follow these steps to review integration errors:

1. Log in to the Sprinto admin portal using your credentials.

2. Navigate to Security Hub > Settings > Integrations, and select the Active tab.

3. The number of errors is highlighted at the top of the integrations page. Expand the dropdown button for a detailed view. Note: Your current integrations are healthy if you don't see any error notifications.

   
4. Click View & Fix next to any service provider to review the detailed integration error.

5. On the Error details page, you'll find the following sections:

   • Error Details: This section describes the HTTP error code encountered and briefly describes the error. For example, an HTTP 500 error code indicates an internal server error that may be resolved by refreshing the connection.

   • Troubleshooting: We provide detailed troubleshooting steps for the integration error based on the HTTP code encountered. Follow these steps to resolve the current error. We also provide a helpful article to help you better understand integration requirements and processes. Note: Troubleshooting steps are currently available for limited integrations. We are continuously working to improve our customer experience and expand support by providing troubleshooting steps for every integrated service provider. Refer to the supported integrations list at the end of this article.

   • Reconnect: If the provided troubleshooting steps don't resolve the current errors, you can reconnect your integration to fix them.

     

You can always contact Sprinto Support for assistance.

Resolving Errors

You can resolve integration errors by following one of these methods:

1. Troubleshooting Steps:

Note: Troubleshooting steps are currently available for limited integrations. We are constantly working to support more services. The supported services are listed at the end of this article.

• Follow the instructions provided under the Troubleshoot section of the Error Details page for the service provider. For example, the troubleshooting steps may ask you to ensure the user performing the integration has admin access. After performing the troubleshooting steps, click Refresh to validate the connection. If the integration error persists, consider reconnecting the integration.

2. Reconnecting:

• If your service provider doesn't support troubleshooting steps or the provided troubleshooting steps didn't resolve the existing error, you can reconnect the integration by following the integration process for the service provider on Sprinto.

• Refer to the integration guide for the service provider for detailed instructions.

Troubleshoot Supported Services:

• Amazon Web Services (AWS)

• Microsoft Azure

• Google Cloud Platform (GCP)

• GSuite

• Microsoft Office365

• GitHub

• Bitbucket

• GitLab

• Kandji

• Microsoft Azure DevOps

• Intune

• PagerDuty

• SonarQube

• MongoDB Atlas

• Datadog

• OpsGenie

• Okta

• Checkr

• KnowBe4

• Zoho (IDP)

• Oracle Cloud

• Jenkins

• All Merge-based integrations (HRMS and Ticketing tools)

• All Truto-based integrations (Access control services for Critical systems)