LogicMonitor

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

Connect with an API token

1. In LogicMonitor:

   1. In LogicMonitor, create an API Only User for Safeguard.
   2. The user that owns the token must not have the out-of-the-box Administrator role (LogicMonitor rejects REST API requests made with tokens created by such users); check Allow Creation of API Token under Settings › User Profile.

   LogicMonitor's public documentation does not cover every step.

   The fetched API Tokens page now documents only LMv1 tokens (Access ID and Access Key); the bearer token steps and the 'shown only once' claim were not on it, so they were removed. Bearer token creation is documented on LogicMonitor's separate 'Adding a Bearer Token' page, which was not in this entry's sources. Where the portal name for the Account field is shown was not confirmed.

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

   The permissions Safeguard needs: view-only API user.

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

   Field	What to enter
   Account	Required. The part before .logicmonitor.com in your address.
   Bearer token	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

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