UpCloud

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

Connect with an API token

1. In UpCloud:

   1. Create a dedicated API sub-account: in the UpCloud Control Panel go to People › Accounts and click Create subaccount.
   2. Enter the contact details and set the API password (this is the Username and Password for Safeguard's form).
   3. In the permissions section, enable API access and turn off Control Panel access. Grant access to the servers, storage and tags Safeguard should see through the server, storage and tag access options.
   4. Click Create subaccount.
   5. Optional, instead of the password: in the Control Panel go to Account › API Tokens and click Add new API token. Enter a Name and Expiration (maximum validity is 365 days), leave Allow token to create tokens off, set the allowed IP ranges, and copy the token: the full token is only shown once.

   Where to find the other values:

   • Username: The username you set when creating the sub-account under People › Accounts.

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

   A new API sub-account has full permissions on resources it creates but no access to existing servers or storage until you grant it. The sub-account's API access flag has no effect on API tokens. The exact label for read-only server/storage access in the permissions section was not quoted in the docs read. The password is not shown once; the API token is.

   Source: upcloud.com, upcloud.com, developers.upcloud.com, checked 2026-10-07.

   The permissions Safeguard needs: API sub-account, read access.

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

   Field	What to enter
   Username	Optional.
   Password	Optional. Stored encrypted and never shown again.

   Or, instead: API token (optional).

3. Click Connect with token.

Frameworks

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