Nagios

Record your Nagios connection as observability evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Nagios:

   1. In Nagios XI, sign in as an administrator and go to Admin › Users › Manage Users.
   2. Click Add New User (or click the edit icon on an existing dedicated user).
   3. Under Security Settings, leave Authorization Level at User (the most restrictive level), select Can see all objects so the user can read every host and service, select Read-only access, and select REST API access. A User-level account with REST API access can only read the Objects API endpoint.
   4. Save the user, then sign in to Nagios XI as that user.
   5. Go to Help › API Docs › Introduction; the user's API key is shown in the Authentication section. Copy it.

   Where to find the other values:

   • API token / Personal access token: Help › API Docs › Introduction, Authentication section, while signed in as the API user. Each Nagios XI user has their own API key.
   • Base URL (optional): Your Nagios XI server address; the API lives at http://<XI.Server.IP>/nagiosxi/api/v1/ (for example /nagiosxi/api/v1/system/status?apikey=<your-API-key>). The example calls in Help › API Docs are pre-filled with your XI server URL.
   • Account / Org / Workspace (optional): Nagios XI is self-hosted and has no account or workspace identifier; leave blank.

   Applies to Nagios XI 2024 and 2026 (commercial). Nagios XI's REST API has three sections: Objects (read-only, available to normal users with REST API access), Config and System (Admin only). The API key stays visible under Help › API Docs, so it is not a one-time display. Nagios Core (the open-source edition on nagios.org) is not covered by these guides; no official source for a Nagios Core API token was found. Verification: the User Rights guide's Add New User screenshot labels these options 'Can see all hosts and services' and 'API access', while its settings table uses 'Can see all objects' and 'REST API access'. That guide also says Nagios XI 2026R2+ users should refer to an updated guide.

   Source: assets.nagios.com, assets.nagios.com, checked 2026-10-07.

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

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

Nagios publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.

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