Yardstik
Connect Yardstik to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Yardstik to collect background check providers evidence with automated compliance tests, switched on per workspace.
| Category | Background Check Providers |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Yardstik's guide | developer.yardstik.com |
Connect with an API token
-
In Yardstik:
- In the Yardstik dashboard, go to Developer Tools › API Keys (app.yardstik.com/developer/api-keys).
- Enter a descriptive key name and click Create.
- Copy the full key from the popup now; Yardstik says this is the only time you will see the complete API key.
Yardstik shows the secret only once, so copy it before you leave the page.
Source: developer.yardstik.com, checked 2026-10-07.
The permissions Safeguard needs:
reports and candidates: read. -
On Compliance › Connectors, open Yardstik, 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 Yardstik 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 | CC1.4 | 1 |
| ISO/IEC 27001 | Automated tests | A.6.1 | 1 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3) | 1 |
| PCI DSS | Automated tests | 12.7.1 | 1 |
| NIST CSF 2.0 | Automated tests | GV.RR-04 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Background Check Providers 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