Hyperproof
Connect Hyperproof to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Hyperproof connection as compliance as code evidence. Automated collection is not available for this provider yet.
| Category | Compliance As Code |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Hyperproof:
- As a Hyperproof administrator, select Settings › API clients.
- Select the Service account tab, then click New.
- Enter a name below Name, then click the Copy to clipboard icon below Client ID.
- From the Scopes drop-down menu, select only read scopes for the data Safeguard collects.
- From the Role drop-down menu, select the least-privileged role that can read that data (for example User or External auditor rather than Admin or API admin).
- Click the Copy to clipboard icon below Client secret, then click Save. The secret cannot be viewed again once the New API client window is closed.
- Exchange the client ID and secret for an access token using the OAuth client credentials flow, and paste the token into Safeguard.
Hyperproof shows the secret only once, so copy it before you leave the page.
Hyperproof's public documentation does not cover every step.
Hyperproof authenticates with a client ID and secret (machine-to-machine), not a static token; the resulting access token expires, so the connector may need client-credential support. The help article does not list scope names, so the exact read-only scope labels are unverified. Only Hyperproof administrators can create service account API clients; any user can create a personal API client. Client secrets expire six months after creation by default.
Source: help.hyperproof.app, developer.hyperproof.app, checked 2026-10-07.
-
On Compliance › Connectors, open Hyperproof, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
No automated compliance test reads Hyperproof yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- Compliance As Code 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