DigitalOcean

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

Connect with an API token

1. In DigitalOcean:

   1. Log in to the DigitalOcean Control Panel; in the main menu click Account, then API.
   2. On the Applications & API page, Tokens tab, in the Personal access tokens section, click Generate New Token.
   3. Enter a Token name and choose an Expiration.
   4. Under Scopes, select Read Only (it grants the api:read alias scope).
   5. Generate the token and copy it; for security the secret is only shown once.

   DigitalOcean shows the secret only once, so copy it before you leave the page.

   The scope options available depend on your team role, and the token's permissions follow later changes the team owner makes to that role. Create the token while the right team is selected.

   Source: docs.digitalocean.com, checked 2026-10-07.

   The permissions Safeguard needs: *:read.

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

   Field	What to enter
   Access token	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

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