---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Verify connectivity for LogRhythm

# Verify connectivity for LogRhythm {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Verify your connection to the LogRhythm Client Console by sending curl
requests to test the LogRhythm REST API. The verification process is
optional.

## Before you begin

Role required: sn_si.admin

## About this task

To verify the connection to the LogRhythm Client Console is working properly after you set up the LogRhythm REST APIs, send two curl requests from the computer hosting the MID Server you configured in [Install the plugin and configure LogRhythm](https://servicenow-prod.fluidtopics.net/tleO5XpJYM0z8IO~ygMKsA "Before you run the integration on your instance, complete the installation and configuration steps so the application properly integrates with Security Operations on the ServiceNow AI Platform.").

The LogRhythm REST API uses WSSE for authentication, which requires some outside scripting to work with Curl and Postman.

The LogRhythm REST API uses a token for authentication, so you can make the actual validation call that the integration uses. The "0" at the end of the URL is a LogRhythm Alarm ID. The LogRhythm REST API with a default configuration requires port 8501. This port number should be included in the URL that you plan to use for the test.

## Procedure

Update the URL \<LogRhythm REST url\> and token \<api token\> in the following curl request and send it to validate the LogRhythm REST API: <kbd class="ph userinput">curl -k -i -v --trace-time -o /dev/null -H "Content-Type: text/json" -H "Authorization: Bearer &lt;api token&gt;" "https://&lt;cache drilldown url&gt;/lr-drilldown-cache-api/drilldown/0"</kbd>  
For a successful connection to the LogRhythm REST API, you should receive an HTTP 404, but the response body contains Alarm ID: 0 not found.