UpGuard Vendor Risk
Connect UpGuard Vendor Risk to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect UpGuard Vendor Risk to collect vendor procurement evidence with automated compliance tests, switched on per workspace.
| Category | Vendor Procurement |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| UpGuard Vendor Risk's guide | help.upguard.com |
Connect with an API token
-
In UpGuard Vendor Risk:
- Sign in to UpGuard as an administrator (only administrators can access the API token).
- Click the Settings icon in UpGuard's top-right corner.
- Click the API tab.
- Copy an existing key or click Create new API key.
The doc does not describe per-key scopes, so the BreachRisk grant depends on the account's UpGuard modules rather than a key setting. Whether the key is shown only once is not stated.
Source: help.upguard.com, checked 2026-10-07.
The permissions Safeguard needs:
BreachRisk. -
On Compliance › Connectors, open UpGuard Vendor Risk, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read UpGuard Vendor Risk and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC7.1 | 2 |
| ISO/IEC 27001 | Automated tests | A.8.8 | 2 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1) | 2 |
| PCI DSS | Automated tests | 6.3.3, 11.3.1 | 2 |
| NIST CSF 2.0 | Automated tests | ID.RA-01, ID.RA-06 | 2 |
These tests are switched on per workspace by the Safeguard team.
Related
- Vendor Procurement connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks