Bitsight Third Party Cyber Risk for Coupa

Bitsight Third Party Cyber Risk is an app built by AcquisLink for Coupa. It displays Bitsight security ratings on Coupa supplier records, so users can view a supplier’s cyber risk in Coupa without logging in to Bitsight. The app matches suppliers to their Bitsight profiles, refreshes overall ratings and risk vector grades once a day, and displays live risk vector grades on demand.

This article covers Bitsight Third Party Cyber Risk for Coupa, including an overview of integration workflows, step-by-step onboarding instructions, and answers to frequently asked questions.

Table of Contents

What is Bitsight Third Party Cyber Risk for Coupa?

AcquisLink connects Coupa supplier records to Bitsight. The integration runs as three separate automated workflows.

How the three integrations work together

The workflows are designed to run in sequence on a schedule:

  • Integration 1 runs first: this integration links any new suppliers in Coupa to their Bitsight company profiles. This only needs to happen once per supplier, but the workflow runs regularly to catch newly added suppliers.
  • Integration 2 refreshes the security scores on every linked supplier's Coupa profile.
  • Integration 3 simultaneously pushes the same Bitsight scores into the structured Risk Aware module for reporting and dashboards.

Integration 1: Subscribe New Suppliers to Bitsight

  Details
Reads from Coupa (supplier list, filtered to those with no Bitsight ID on file)
Searches Bitsight company search API (by website domain or name)
Writes back to Coupa supplier record — Bitsight company ID and/or review note

What it does: This workflow runs periodically and looks for Coupa suppliers that have not yet been linked to a Bitsight company. This is an onboarding step that allows Bitsight scores to flow into Coupa and allows the data in the other two integrations (2 and 3) to keep current automatically. 

For each unlinked subscriber, the integration:

  1. Searches Bitsight using the supplier’s website domain
  2. Compares the Coupa supplier name to the best match in Bitsight using a similarity score
    • If the match has a confidence score >80%, the company is subscribed in Bitsight for continuous monitoring and the unique Bitsight identify is written back to the supplier record in Coupa
    • If the match is below the threshold, the supplier record is flagged in Coupa with a note of top candidates for human review.
    • If Bitsight returns no results at all: the supplier is marked with a “No Potential Match Found” note.

What counts as a confident match? 

The Integration 1 workflow calculates a fuzzy name-match score between the Coupa supplier name and the best Bitsight search result. It is currently configured so that 75% or above defines a match and the supplier is subscribed in Bitsight and linked automatically. Below that, the Bitsight company note is populated instead showing the top three closest matches for manual review.

The match score is configurable

What happens when Bitsight returns more than one possible match? 

When the match score falls below the threshold, Coupa's Bitsight Company Note field is populated with "Manual Review Required" plus the name and GUID of the top two Bitsight search results, so a reviewer can pick the correct company by hand and set the Bitsight Company ID manually.

Integration 2: Sync Security Ratings to Supplier Records

  Details
Reads from Coupa (suppliers with a Bitsight ID) and Bitsight (security rating details)
Writes back to Coupa supplier record — custom security rating fields

What it does: This workflow runs for suppliers that are already linked to Bitsight (i.e., they have a Bitsight company ID stored in Coupa). This integration refreshes the overall Bitsight Risk Rating and the configured risk vector grades on each Coupa supplier record.

For each linked supplier, the integration:

  1. Retrieves the latest security data from Bitsight
  2. Maps each individual risk score to a corresponding risk vector rating on the Coupa supplier record.
  3. Updates the Coupa record so the data is visible to procurement and risk teams.

Custom fields updated in Coupa on each refresh:

  • Overall Bitsight Risk Rating: Numeric score (250–900)
  • Botnet Infections: Grade (A–F)
  • Spam Propagation: Grade (A–F)
  • Malware Servers: Grade (A–F)
  • Unsolicited Communications: Grade (A–F)
  • Potentially Exploited: Grade (A–F)
  • SPF Domains: Grade (A–F)
  • DKIM Records: Grade (A–F)
  • TLS/SSL Certificates: Grade (A–F)
  • TLS/SSL Configurations: Grade (A–F)

The number of risk vectors is customizable.

Integration 3: Sync Security Ratings to Risk Aware Feed 

  Details
Reads from Coupa (suppliers with a Bitsight ID, existing Risk Aware feed) and Bitsight (overall security rating)
Writes back to Coupa Risk Aware feed — overall security score field

The number of risk aware feeds to sync between Bitsight and Coupa are customizable.

What it does: This workflow mirrors Bitsight data into the Risk Aware module, so no manual data entry is required.. Risk Aware is the structured, reportable home for supplier risk data inside Coupa.

For each linked supplier, the integration:

  1. Checks whether the supplier already has a Risk Aware entry in Coupa and creates a new Risk Aware entry if none exists.
  2. Retrieves the latest security rating from Bitsight.
  3. Updates the Risk Aware entry with the Bitsight overall score so it feeds into any Risk Aware dashboards and reports configured in Coupa.

Onboarding Instructions

Complete these steps once for each client before you set up the integrations. They create the credentials and custom fields that the integrations read from and write to.

Before you begin

  • Acquire the app through the Coupa App Marketplace.
  • An active Bitsight Continuous Monitoring subscription is required.

This integration must be purchased, please contact your Bitsight sales representative.

Step 1: Create Coupa OAuth credentials

AcquisLink authenticates to the client’s Coupa instance with an OAuth 2.0 client. This must be created once per client.

  1. As a Coupa admin, open the Bitsight Third Party Cyber Risk listing in the Coupa App Marketplace.
  2. Click Get Started.
  3. Complete the form.
  4. After you submit the form, click Install Now to obtain the OAuth client and the Panel App in your Coupa instance.
  5. Record the client ID and client secret generated. Send both to AcquisLink through a secure channel.

Step 2: Create a Bitsight API token

A Bitsight API token scoped to the client’s Bitsight organization is required. AcquisLink uses the token to search, subscribe, and pull ratings for suppliers.

  1. Log in to the Bitsight portal as an administrator for the client’s account.
  2. Go to Settings > API Tokens, and generate a new token.
  3. Record the token. Send it to AcquisLink through a secure channel.

Step 3: Create the Bitsight Admin content group

This content group restricts who can view and edit the metadata Bitsight fields in Coupa.

  1. In Coupa, go to Setup > Security > Content Groups.
  2. Create a new content group named Bitsight Admin.
  3. Assign the content group to the roles and users who support the flow of Bitsight data to Coupa (i.e. the integration team and risk/security admins)

Step 4: Create supplier custom fields

Create the following custom fields on the Coupa Supplier object. These fields are populated by Integration 1 (matching) and Integration 2 (rating sync)

  1. In Coupa, go to Setup > Custom Fields.
  2. Create the field listed in the table below:
Field Requirement
Bitsight Company ID Required
Bitsight Company Note Required
Bitsight Risk Rating Optional
Bitsight GUID Updated Date Required
Bitsight Supplier Updated Date Conditional: create this field if you use Coupa supplier custom fields
Bitsight Risk Aware Updated Date Conditional: create this field if you use Risk Aware custom fields
One field per tracked risk vector Create one for each risk vector you track

Step 5: Create supplier Risk Aware custom fields

Risk Aware requires its own feed and field definitions, separate from the supplier custom fields you create in Step 4.

  1. In Coupa, go to Setup > Custom Fields.
  2. Create the Bitsight Risk Score field.

Frequently Asked Questions

How does the app link suppliers to Bitsight?

The app searches Bitsight by supplier domain or name. It matches each supplier to a Bitsight company and subscribes that company to Bitsight continuous monitoring. When a match is uncertain, the app sends it to a reviewer, with the top candidate companies listed.

How often do ratings update on supplier records?

The app refreshes the overall Bitsight Risk Rating and the configured risk vector grades on each supplier profile once a day.

Which risk vectors does the integration track?

Risk vectors are configured for each client. Examples include Botnet Infections, TLS/SSL Certificates, and SPF Domains. 

Coupa allows a maximum of 20 custom fields per object.

  • The six non-vector Bitsight fields (Bitsight Company ID, Bitsight Company Note, Bitsight Risk Rating, Bitsight GUID Updated Date, Bitsight Supplier Updated Date, Bitsight Risk Aware Updated Date) use 6 of those 20 slots, leaving at most 14 for risk vectors
  • Fewer slots may be available if there are already other custom fields in use on the Supplier object for unrelated purposes. 
  • During onboarding, check how many Supplier custom field slots the client has free before agreeing which vectors to track.
  • Prioritize the vectors that matter most if the full set will not fit.
Where do supplier ratings appear in Coupa?

The app writes the Bitsight company ID, the overall Bitsight Risk Rating, and the configured risk vector grades to Coupa custom fields on the supplier record. Coupa allows 20 custom fields, and the app refreshes these values once a day.

The live panel on each supplier record shows live risk vector grades from Bitsight, on demand. It is read-only and can display more risk vectors than the custom fields allow.

How do Bitsight scores appear in the Coupa Risk Aware module?

The app feeds Bitsight scores into Coupa Risk Aware. Risk Aware uses these scores for trend tracking, reporting, dashboards, and automated risk workflows. No manual entry is required.

How often do the integrations run, and will a supplier be processed more than once a day?

Each workflow filters out suppliers it has already touched today: 

  • Integration 1 excludes suppliers whose Bitsight GUID update date already equals today and already has a GUID populated.
  • Integration 2 excludes suppliers whose supplier-record update date already equals today.
  • Integration 3 does the same for the Risk Aware update date. 

So even if a workflow is scheduled to run several times a day, each supplier is only processed once per day per workflow.

Which risk vectors get synced to the supplier record today?

Integration 2 updates the Bitsight Risk Rating and the configured risk vectors. The number of risk vectors tracked is restricted by the amount of custom field space remaining on the Coupa Supplier object. 

Coupa allows a maximum of 20 custom fields per object.

  • The six non-vector Bitsight fields (Bitsight Company ID, Bitsight Company Note, Bitsight Risk Rating, Bitsight GUID Updated Date, Bitsight Supplier Updated Date, Bitsight Risk Aware Updated Date) already use 6 of those 20 slots, leaving at most 14 for risk vectors or fewer still if the client already has other custom fields in use on the Supplier object for unrelated purposes. 
  • During onboarding, check how many Supplier custom field slots the client has free before agreeing which vectors to track.
  • Prioritize the vectors that matter most if the full set will not fit.
What happens if a supplier doesn't have a Risk Aware entry yet?

Integration 3 checks for an existing Risk Aware entry for the supplier. If none exists, it creates one first, then updates it with the Bitsight score - so no manual Risk Aware setup is needed per supplier.

What happens with the client who isn’t subscribed to the company in Bitsight?

If a matched company is not yet subscribed in Bitsight, the integration subscribes to it automatically as part of the normal workflow. 

The one edge case is if the client's Bitsight subscription quota has been reached. In that case, a note is written to the supplier's Bitsight Company Note field indicating the quota was hit.

What is the importance of Bitsight Company ID?

The Bitsight Company ID links a Coupa supplier record to its Bitsight company profile and every other part of the integration depends on it. 

  • Integration 2 uses it to look up the supplier's rating details in Bitsight and refresh the supplier's custom fields.
  • Integration 3 uses it to pull the overall score into the Risk Aware feed; and the Bitsight Panel App uses it to fetch live data on demand. 
  • Integrations 2 and 3 both filter for suppliers where this field is populated, so a supplier with no Bitsight Company ID is invisible to those workflows. No rating data will ever sync for it until the ID is set.
Can the number of tracked risk vectors be changed per client?

Yes, the set of vectors is customizable. 

To add or remove a vector for a client:

  1. Create/remove the corresponding custom field on the Coupa Supplier object (Step 4 of onboarding)
  2. Update the Integration 2 field mapping to read that vector's grade from Bitsight's rating_details response. Acquis will support updating the Integration 2 field mapping.
Does the Bitsight Panel App write any data back to Bitsight?

No, the panel app is read-only. It calls Bitsight live and displays the results on the supplier record for the user viewing it. All writes to the supplier's custom fields and the Risk Aware feed come from the scheduled Integration 2 and Integration 3 runs.

Publish Date or Recent Edits
  • October 21, 2026: Published.
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.