Cronitor

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

Connect with an API token

1. In Cronitor:

   1. Create a custom API key with only read scopes. Cronitor documents this as an API call: POST https://cronitor.io/api/keys with a name, kind set to custom, and scopes such as monitor:read (read monitor configurations and status) and integration:read.
   2. Store the key securely: the full API key is only returned once when created.

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

   Cronitor's public documentation does not cover every step.

   The fetched page documents key creation through the API, not a dashboard path. Cronitor describes integration:read as "List and retrieve notification integrations".

   Source: cronitor.io, checked 2026-10-07.

   The permissions Safeguard needs: monitors and notification lists: read.

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

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

3. Click Connect with token.

Frameworks

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