Dynatrace

Connect Dynatrace to collect observability evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Dynatrace:

   1. API token: in your Dynatrace environment, open Access Tokens and select Generate new token.
   2. Enter a descriptive name, choose the scope Read settings (settings.read), and select Generate token.
   3. Copy the token now. You can only access your token once upon creation.
   4. Optional OAuth client for user reads: go to Account Management › Identity & access management › OAuth clients › Create client. Choose Client credentials, enter the subject (service) user email and an optional description, select the required permissions, and select Create client.
   5. Copy the client ID and client secret immediately; you can only access the client secret once upon creation.

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

   Dynatrace's public documentation does not cover every step.

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

   The permissions Safeguard needs: settings.read, account-idm-read.

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

   Field	What to enter
   Instance URL	Required. An address under live.dynatrace.com.
   API token	Required. Stored encrypted and never shown again.
   Account ID (optional)	—
   Client ID (optional)	—
   Client secret (optional)	Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

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

• Observability 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