ManageEngine SIEM Log360 Zero Trust Alarm Integration

Free integration setupWe’ll install and validate this for you.

Book a setup call

Support Statement

DISCLAIMER

This documentation is provided "as is" without support for 3rd party software. The level of support for this integration guide is best effort without any SLA on response time. No 3rd party product support can be provided by Superna directly. 3rd party components require support contracts. See EULA for more details.

---

Overview

Customers using ManageEngine SIEM Log360 can leverage a native integration that initiates native ingestion API alerts from Security Edition Zero Trust alerts. Customers can augment the capabilities of ManageEngine SIEM Log360 with threat intelligence and Cyber Storage capabilities of Superna Security Edition.

Solution Overview

Superna Defender Zero Trust API receives webhook alerts and parses the key data into a syslog UDP or TCP event that is sent to Log360. ManageEngine SIEM Log360 is a modular architecture that provides real-time visibility of your IT infrastructure, which you can use for threat detection and prioritization.

Advanced Zero Trust Capabilities

• Webhook to native syslog alarm integration

What Is ManageEngine SIEM Log360?

ManageEngine SIEM Log360 is a modular architecture that provides real-time visibility of your IT infrastructure, which you can use for threat detection and prioritization.

Integration Architecture

Solution Configuration in ManageEngine SIEM Log360 and Defender Zero Trust

Prerequisites

• Installed Security Edition
• Eyeglass OS appliance version 15.5 — verify with cat /etc/os-release
• License key for the Zero Trust API
• ManageEngine SIEM Log360

Configuration in ManageEngine SIEM Log360

The steps below create a custom log parsing rule and configure the syslog device.

1. Log in to the Log360 UI and navigate to SIEM → Settings → Custom log Format.

2. Click Add log format and type Superna.

3. Click Manage Parse Rules.

4. Click Add parser rule and configure as follows:

   • Rule name: Superna
   • Method: Delimiter
   • Delimiter: comma

5. Download the sample syslog text file (right-click, save as). Open the file, copy all the text, and paste it into the left-hand box under the Log heading field.

   note

   The parsing and delimiter values must be set correctly for auto field extraction to work correctly.

6. Assign field names as shown in the Log360 console. Enter the field names exactly as shown.

7. Click Save rule. The custom parsing rule step is now complete.

8. Navigate to SIEM → Settings → Device Management → Syslog devices.

9. Either send test UDP events to leverage auto device discovery, or manually add the Eyeglass device:

   • Click Add Device for syslog devices.
   • Enter the Eyeglass IP address and click Add.

10. Edit the device and set the log type to the custom Superna parsing format to ensure log parsing is applied to all logs from the Eyeglass VM.

11. Click Update to save the device configuration.

Log parsing configuration is now complete. Logs sent from the integration will be parsed correctly.

Configuration Steps on Eyeglass Virtual Machine

High-Level Steps

1. Create the Python location to run the application on the Eyeglass VM.
2. Create the Python main application script.
3. Create the Linux systemd service and set it to auto-start.
4. Create the Zero Trust configuration in Defender.
5. Update the main script to customize it with the ManageEngine SIEM Log360 Python code.
6. Test the script is running as a service.
7. Create a test event in Defender to validate alerts appear as indexed parsed events in ManageEngine SIEM Log360.

Configure the Service Start and Python Integration Files

Log in to the Eyeglass VM via SSH as the admin user:

ssh admin@<your-vm-ip>

Become root:

sudo -s

mkdir -p /opt/superna/cgi-bin

chown -R sca:users /opt/superna/cgi-bin

chmod -R u+rwX,g+rwX /opt/superna/cgi-bin

Switch to the SCA user:

sudo -u sca -s

cd /opt/superna/cgi-bin

Create a Python virtual environment for the integration:

python3 -m venv venv-log360

source venv-log360/bin/activate

Install required Python packages:

pip install flask boto3 requests logging

deactivate

Create integration script files:

touch log360.py

touch log360.sh

chmod +x log360.py

chmod +x log360.sh

Create the log360.sh launch script:

nano /opt/superna/cgi-bin/log360.sh

Paste the following content into the file:

#!/bin/bash

export PATH="/opt/.pyenv/bin:$PATH"

source /opt/superna/cgi-bin/venv-log360/bin/activate

exec python /opt/superna/cgi-bin/log360.py

Make the script executable:

chmod +x /opt/superna/cgi-bin/log360.sh

Exit back to root:

exit

whoami # confirm you are root

Create the systemd service unit file:

nano /etc/systemd/system/log360.service

Paste the following content into the file:

[Unit]
Description=Webhook listener for Zero Trust API translations and integrations
After=network.target

[Service]
Type=simple
User=sca
Group=users
WorkingDirectory=/opt/superna/cgi-bin
ExecStart=/bin/bash /opt/superna/cgi-bin/log360.sh
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

Reload systemd to register the new service:

systemctl daemon-reload

Enable the service to start on boot (do not start it yet):

systemctl enable log360

Configure Python Packages and Customize the Integration Code

1. Download the Python template code from the link to download (right-click, save as).

2. Open the Python template file in a text editor. Only replace the placeholder values — do not delete any commas.

3. Locate the following section and replace the placeholder values with your Log360 endpoint IP address, port, and TCP flag:

   SYSLOG_SERVER = 'x.x.x.x'  # Replace with your syslog server address
   SYSLOG_PORT = 514            # Replace with your syslog server port
   FACILITY = 13                # Facility code for security audit log
   SEVERITY = 2                 # Severity level for critical messages
   USE_TCP = False              # Set to True for TCP, False for UDP

4. Open the production file on the Eyeglass VM:

   nano /opt/superna/cgi-bin/log360.py

5. Open the template file locally in Notepad, select all (Ctrl+A), and copy.

6. Paste the clipboard into the SSH terminal session with the open nano editor.

7. Save the file:

   • Press Ctrl+X
   • Answer Yes to save and exit

8. Start the service and verify it is running:

   systemctl start log360
   
   systemctl status -l log360

   Verify the service returns "active and running". If the service does not start, do not proceed — double-check the steps above.

Configure Defender Zero Trust Webhooks

1. Configure the Zero Trust endpoint in the Ransomware Defender Zero Trust tab.

   Recommended Configuration

   Send only Critical and Major events, and only webhooks that set lockout or delayed lockout. The goal is to send findings rather than a list of alarms that do not pinpoint a security incident. Customers can customize based on specific requirements.

2. The endpoint URL uses localhost and sends webhooks to the application service listening on port 5000:

   http://localhost:5000/webhook

3. Add the Content-Type header with value application/json to complete the webhook configuration.

4. Click Save to commit the configuration.

5. Click Save on the main Webhook configuration page.

How to Test the Integration with ManageEngine SIEM Log360

1. Install the ManageEngine SIEM Log360 agent on a test machine and record its IP address.
2. Get the IP address of the Eyeglass VM.
3. Download the curl command template and open it with a text editor:
   • Locate the IP address of Eyeglass at the very end of the text and replace it with the IP address of your Eyeglass VM.
   • Search for clientIPs":["172.31.1.45"] and replace only the IP address with the IP of the test machine running the ManageEngine SIEM Log360 agent. This simulates a Zero Trust alert on that host.
4. Copy all the text in the text editor.
5. SSH to the Eyeglass VM as the admin user.
6. Paste the entire CLI command to the SSH prompt to send sample data to the running Zero Trust application. This sends test data directly to the application to be processed and sent to ManageEngine SIEM Log360.

A successfully processed webhook test returns the following text in the SSH terminal:

done sending event to log360 and check for http 200 and success count in response

To review the process logs from the web application:

sudo -s

journalctl -f -u log360

To log to a file and review with nano, showing only the most recent 250 lines:

journalctl -f -n 250 -u log360 > /tmp/log360.log

nano /tmp/log360.log

The response code from the ManageEngine SIEM Log360 API call should show HTTP 200 status code and successCount 1 to indicate the event was successfully created.

Log in to ManageEngine SIEM Log360 and verify that new log events appear in the log event viewer.

ManageEngine SIEM Log360 SecOps Administrators Integration Experience

Once the custom parsing rules and device configuration are updated, any new messages are parsed and all fields can be extracted for trigger correlation rules.

To search for Superna events, set the log type to Superna_custom.

Create an Alert Rule for Superna Zero Trust Events

Use the following search criteria when creating an alert rule:

(incident_type:event_type=threat_detection) AND (vendor:device_vendor=Superna) AND (LogType:Superna_custom)

1. Enter an alert rule name — for example, Superna Zero Trust Alert.
2. Set the notification rules.
3. Set the log source to the IP address or hostname of the Eyeglass VM device.
4. Configure alert actions and notifications as needed.