Heroku

Connect Heroku to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Heroku:

   1. Install the Heroku CLI and sign in with heroku login as a member of the team Safeguard should read.

   Heroku's public documentation does not cover every step.

   The fetched page covers heroku login and showing the current CLI token with heroku auth:token (a full-account token), but not heroku authorizations:create, token scopes (read, global, identity) or one-time display, so those steps were removed. A sourced least-privilege token path is still missing. Where the dashboard shows team names was not covered.

   Source: devcenter.heroku.com, checked 2026-10-07.

   The permissions Safeguard needs: read.

2. On Compliance › Connectors, open Heroku, click Connect, choose API token and fill in:

   Field	What to enter
   API key	Required. Stored encrypted and never shown again.
   Team (optional)	—

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Heroku 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.

These tests are switched on per workspace by the Safeguard team.

Related

• Cloud Infrastructure 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