Vendor Integration
Overview
The vendor integrations help provide our customers visibility into data stored in external third-party SaaS systems (or data-at-rest). We have several out-of-the-box integrations already available that connect with third-party SaaS systems via REST APIs to create this visibility in Relyance.
Relyance connects with these tools using their public REST APIs. Our integrations query-specific endpoints for these tools, scan the response, process it, and display the data types we detect in the platform. All processing happens “in-flight” and we do not store data from your third-party tools in Relyance.
Why is this integration important?
This Vendor integration helps with:
- Creating visibility for the privacy, legal, and security teams around the data that is stored in external third-party systems.
- Relyance combines this information with what we find from your contracts and from your source code to create a "single source of truth" of the types of data a vendor is processing / storing and displays that in the data inventory and map.
- Data types detected using these vendor integrations are also included in the Records of Processing Activity (ROPA) that Relyance automatically creates.
Integration Details:
Details about how to configure the Vendor Integrations are listed below:
| Stakeholders needed | We typically work with the tool owners (IT Admins) team to connect with the desired tool. |
|---|---|
| Effort | The integration time is a few seconds to a few minutes at best. |
| Integration Configuration Summary | While we have step by step guides, a generic process to configure the infrastructure integration is below: To get started, navigate to Settings > Integrations > Vendor Integrations. Find the desired vendor and click it to open its connections. In the Create Connection section, select the desired connection type. Provide the appropriate connection details such as API Keys, API Tokens, etc. to configure the connection and click Save. Relyance also provides step-by-step guides for the specific integrations. |
| Status | Once a vendor integration is connected, the vendor card will move to the top of the vendor list on the integrations page. The vendor card will also show the current vendor integration status of Connected, or Failure. A connection could fail for a variety of reasons including token expiry, account termination, vendor API changes, etc. Should the connection fail, the best way to resolve this is to re-setup the connection as per the integration guide. |
It is recommended to use a service email/account associated with the vendor application wherever possible when configuring integrations in Relyance.
It is important for a few reasons, such as:
- Maintain the ability to manage the service email login separate from a regular user account
- Prevent integration failure when individual user accounts are disabled due to employee churn
- Avoid confusion in the event logs that are captured
Relyance AI provides integration information, as well as any endpoints used, scopes and permissions, on the integration settings page.
