Zabbix

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

Connect with an API token

1. In Zabbix:

   1. In the Zabbix frontend, go to Users › API tokens.
   2. Click Create API token.
   3. Enter a Name (for example Safeguard) and choose the User the token belongs to (a user whose role allows the API methods below). Optionally add a Description and tick Set expiration date and time to set an Expiry date.
   4. Leave Enabled ticked and click Add.
   5. Copy the Auth token value and save it before closing the page.
   6. To limit the token's user to read methods, go to Users › User roles and click Create user role (or edit the user's role).
   7. In the API access section, keep Enabled ticked, set API methods to Allow list and add action.get and user.get.
   8. Assign this role to the user that owns the token.

   Where to find the other values:

   • Server URL: The address of your Zabbix frontend (the URL you sign in to).

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

   Zabbix shows the token value only once; regenerating creates a new one. Users without the Administration menu can manage their own tokens from User profile › API tokens if their role permits Manage API tokens. user.get returns full user lists only to roles with sufficient user type; Zabbix has no narrower grant.

   Source: zabbix.com, zabbix.com, checked 2026-10-07.

   The permissions Safeguard needs: action.get, user.get. Zabbix has no narrower grant for these reads. Safeguard only reads with it.

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

   Field	What to enter
   Server URL	Required. Your own server: an https address reachable from the internet.
   API token	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

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