Skip to main content
Version: 2.14.1

Securonix SIEM Zero Trust Alert 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 Securonix SIEM can leverage a native integration that initiates native ingestion API alerts from Security Edition Zero Trust alerts. Customers can augment the capabilities of Securonix SIEM 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 HTTPS API payload events that are sent to the SIEM collector endpoint URL. Securonix SIEM 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 HTTPS collector API alarm integration

What Is Securonix SIEM?

Securonix is a cybersecurity company that specializes in threat detection, investigation, and response (TDIR). They offer a platform called Unified Defense SIEM — a next-generation Security Information and Event Management system.

Integration Architecture

Securonix SIEM integration architecture

Solution Configuration in Securonix SIEM 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
  • Securonix SIEM

Configuration in Securonix SIEM

The steps below create a collector endpoint.

  1. Log in to the Securonix SNYPR application.
  2. Navigate to MenuAdd DataActivity.
  3. Click Add Data for Supported Device Type to set up the ingestion process.
  4. In the Resource Type Information section, configure the following:
    • Vendors: Search for and select Superna
    • Resource Type: Search for and select Superna Eyeglass Zero Trust
    • Parser Name: Select SCNX_SUPERN_SUPERNAEYEGLASSZEROTRUST_ZTS_HTT_JSO
  5. Create a resource group name. Set the timezone, source data name, and configure Authentication to Header based. Enter a header value that is used to authenticate — this is an API key to access the endpoint.
  6. Click Generate Receiver Endpoint.
  7. Record the URL and the header value — you will use both in the integration configuration below.
  8. Leave all other fields at their defaults.
  9. Click Activate Event Receiver.
  10. Click through Save & Next to complete the configuration. Consult with Securonix support for any non-default tab configurations.
  11. On the summary page, set the job interval to 300 seconds.

Once test events are generated with the steps below, you should be able to see parsed messages in the Securonix console.

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 Securonix SIEM 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 Securonix SIEM.

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-securonix

source venv-securonix/bin/activate

Install required Python packages:

pip install flask boto3 requests logging

deactivate

Create integration script files:

touch securonix.py

touch securonix.sh

chmod +x securonix.py

chmod +x securonix.sh

Create the securonix.sh launch script:

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

Paste the following content into the file:

#!/bin/bash

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

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

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

Make the script executable:

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

Exit back to root:

exit

whoami # confirm you are root

Create the systemd service unit file:

nano /etc/systemd/system/securonix.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/securonix.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 securonix

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 Securonix endpoint URL and API key recorded from the configuration steps above:

    # Securonix HTTP Collector Endpoint
    Securonix_URL = "xxxxxxxx"
    Securonix_key = "yyyyyyy"
  4. Open the production file on the Eyeglass VM:

    nano /opt/superna/cgi-bin/securonix.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 securonix

    systemctl status -l securonix

    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 following headers to complete the webhook configuration:

    • Content-Type: application/json
    • content-encoding: gzip
  4. Click Save to commit the configuration.

  5. Click Save on the main Webhook configuration page.

How to Test the Integration with Securonix SIEM

  1. Install the Securonix SIEM 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.
  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.

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

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

To review the process logs from the web application:

sudo -s

journalctl -f -u securonix

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

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

nano /tmp/securonix.log

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

Securonix SIEM SecOps Administrators Integration Experience

Once the integration is complete, parsed results appear in the Securonix SIEM console after an alert is sent to the collector endpoint URL and processed through the parser.