Pingdom

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

Connect with an API token

1. In Pingdom:

   1. Generate a Pingdom API token inside My Pingdom.
   2. Set the token's Access level to Read access (only operations that create or modify something need Read/Write).
   3. Copy the token; Safeguard sends it with HTTP Bearer authentication.

   Pingdom's public documentation does not cover every step.

   Pingdom's API reference (the API 3.1 spec behind docs.pingdom.com/api) says the token is generated inside My Pingdom and has an Access level property; it gives no menu path or button labels, and does not say whether the token is shown only once.

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

   The permissions Safeguard needs: read-only.

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

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

3. Click Connect with token.

Frameworks

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