Upguard

Upguard Vendor Risk is a third-party risk management tool that delivers instant vendor insights, 360-degree assessments, and time-saving workflows all in a centralized place. For detailed information, please refer to the Upguard’s official documentation.

Integration Method: API

Tables: Vulnerability Finding (2002), Assessment Finding (99402001)

This integration supports the following events.

This integration supports the following versions.

Prerequisites

• The user must have access to the Upguard portal with an account that has the Global Administrator privileges.

• The user should have access to the DataBee console.

Configuration Overview

1. Generate an API token with the required scopes

   1. Create New API Key.

2. Add the Upguard in the DataBee console with the below parameters.

   DataBee Parameter	Upguard Parameter
   Token	API Key

Upguard Configuration

Create New API Key

1. Log on to Upguard portal with an account with Administrator privileges.

2. Navigate to the Settings option at the above Navigation bar.
    

3. Select the API tab. Any existing API keys will be listed, click on the Create new API key button to create the new API key.
    

4. Enter the API Key Name, set the permission to VendorRisk, and click the Create API Key button.
    

5. Get the API key value that you created from as shown below.
    

DataBee Configuration

1. Login to the DataBee UI, navigate to Data > Data Feeds and click the Add New Data Feed button.
    

2. Search for the Upguard and click it as shown below. 

   

3. Click on the API Ingest option for collection method. 

   

4. Enter feed contact information and click Next.

   

5. In the configuration page, enter the following:

   • Authorization Method: Bearer Token

   • Token: paste the API Key generated earlier in the Upguard portal.

   • Event Types: preselected for all the event types that integration pulls.
      

6. Click Submit.

Troubleshooting Tips

• If you receive an Unauthorized error, it may be because the API Key provided in the token might be wrong or expired. Verify that you are using credentials from the application to resolve the issue.