Skip to content
Connection Guide

Connect Hyperproof Without Breaking the Audit Trail

Use this guide to connect Hyperproof or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryGrc
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Hyperproof and make sure the first collection lands cleanly.

  1. 1
    Enable Hyperproof machine-to-machine API clients for the organization and create a dedicated Aurora service-account client.
  2. 2
    Use the regional base_url that matches the tenant, such as https://api.hyperproof.app/v1, https://api.hyperproof.eu/v1, or https://api.hyperproofgov.app/v1.
  3. 3
    Store base_url, client_id, and client_secret in Aurora and keep the client on the documented read-only scope bundle control.read, user.read, proof.read, and issue.read.
  4. 4
    Prefer the API admin service-account role when Aurora must read full-fidelity controls, proof, and issues across the organization.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

client_secret

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.