AppDynamics

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

Connect with an API token

1. In AppDynamics:

   1. In the AppDynamics Controller UI, click the settings icon and choose Administration.
   2. Select the API Clients tab and click + Create.
   3. Enter the Client Name and Description, then click Generate Secret to populate the Client Secret. Copy the secret.
   4. Add the Roles to associate with the client, then click Save.

   Where to find the other values:

   • Instance URL: Your Controller address (the host in https://<controller address>/controller/api/oauth/access_token).
   • Client ID: <apiClientName>@<accountName>, for example testclient@accountName.

   AppDynamics docs now live on help.splunk.com (the docs.appdynamics.com link failed TLS verification). The page does not say whether the client secret can be viewed again, and does not name a specific built-in read-only role.

   Source: help.splunk.com, checked 2026-10-07.

   The permissions Safeguard needs: read-only role.

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

   Field	What to enter
   Instance URL	Required. An address under saas.appdynamics.com.
   Client ID	Required.
   Client secret	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

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