Cribl Zero Trust Incident Ingestion

• Overview
• Support Statement
• Limitations
• Solution Overview
• What is Cribl?
• Integration Architecture
• Solution Configuration in Cribl and Defender Zero Trust
• Prerequisites
• Features
• Configuration in Cribl Json endpoint ECS format
• Configuration in Cribl Json endpoint HEC format
• Configuration Steps on Eyeglass Virtual Machine
• High Level steps
• Configuration Step by Step
• Configure the Service start and python integration files
• Configure the python packages and customize the Cribl integration python code
• Configure Defender Zero Trust Webhooks
• How to test the Integration with cribl
• Cribl Administrator Integration Experience

Overview

Customers using Cribl can leverage this integration to send real time zero trust alerts using webhooks and maintain full payload parsing using json defined fields.   The Cribl Alert Ingestion Connector capability within the platform allows inbound webhook json payload to be parsed and turned into host status updates.  Customers can then use Cribl to use the transformation and multiple destination sync to various security tools.   

Support Statement

1. NOTE:  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

Limitations

1. NOTE: This guide does not provide any configuration for routes, pipelines or destinations.  It is assumed customers will configure where the alert data should be routed and sent to destinations.
   

Solution Overview

Superna Data Security Edition  Zero Trust API is the cornerstone technology used to integrate with SIEM and SOAR platforms.    This integration offers alerts mapped to ECS format (Elastic Cloud Schema)  or HEC format and sent to Cribl HTTPS json endpoint stream.

What is Cribl?

Provides a data engine and platform for IT and security teams to manage machine data like logs, metrics, and traces. Its core function is to collect, process, and route this data from any source to any destination, helping organizations control costs, reduce risk, and gain better visibility. Key products like Cribl Stream and Cribl Edge allow users to filter, enrich, and route data in real-time. 

Integration Architecture

Solution Configuration in Cribl and Defender Zero Trust

Prerequisites

1. Installed Data Security Edition subscription product
2. Eyeglass OS appliance version 15.5
   1. cat /etc/os-release
3. License key for the Zero Trust API  
4. Cribl or Cribl Enterprise

Features

1. Sends native Incident api calls and severity mapped from Superna to Cribl
2. Fields are mapped to Cribl ECS format
3. Optional setting to format has HEC format (Splunk HEC) and send to the splunk HEC endpoint

Configuration in Cribl Json endpoint ECS format

1. Login to the console
   1. Edit the http data source in your workspace to add an API token
   2.  
   3. 
   4. Record the token value
2. Record the endpoint url for the bulk json input endpoint.
3. Done.

Configuration in Cribl Json endpoint HEC format

Note: Only follow these steps if you plan to use the Splunk HEC endpoint with Cribl and HEC format = true. 

1. Login to console
2. Locate Data sources 
3. Edit the in_splunk_hec data source
   1. Add an authentication token
   2.  
4. Record the endpoint url and token value for the steps below
5. Done

Configuration Steps on Eyeglass Virtual Machine

High Level steps

1. Create python location to run the application on the Eyeglass vm
2. Create python main application script
3. Create linux systemd service and set to auto start
4. Create Zero Trust configuration in Defender
5. Update the main script to customize with Cribl  python code
6. Test the script is running as a service
7. Create a test event in Defender to validate the alerts appear as indexed parsed events in Cribl

Configuration Step by Step

1. Login to the eyeglass VM as admin user
2. Follow the steps below

Configure the Service start and python integration files

Configure the python packages and customize the Cribl integration python code

1. Customize the application code by downloading the python code from this link to download (right click download as)
   3. Open the python template file in a text editor. NOTE: make sure to only replace the yellow values (endpoint url for http ingestion of your Cribl instance, the api token)
   4. Locate this section in the file, replace yellow highlights.    Change the port if different from below.  Comment out ECS endpoint and uncomment Splunk HEC if using HEC format and set the hec_format = True to enable HEC format.
      3. # === Cribl Configuration ===

         # Use your Cribl Stream Cloud HTTP Bulk API input endpoint

         CRIBL_URL = "https://default.main.goofy-shamir-iqst5ne.cribl.cloud:10080/cribl/_bulk" # Use this for ECS format JSON payload

         #CRIBL_URL = "https://default.main.goofy-shamir-iqst5ne.cribl.cloud:8088/services/collector" # Use this for Splunk HEC format

         CRIBL_TOKEN = "xxxxxxxxxx" # for ecs or HEC format authentication

         
         

         
         

         # === Format Toggle ===

         # Set to True when sending to HEC input (port 8088)

         # Set to False when sending to ECS /bulk input (port 10080)

         hec_format = False

         
         
         
         
   5. Paste the updated script into the production file
      3. nano /opt/superna/cgi-bin/cribl.py
      4. Open the file locally in Windows OS notepad and use control-A or select all the text.
      5. Paste the clipboard into the ssh terminal session with the open nano editor file
      6. save the file
         3. press control+x
         4. Answer yes to save and exit the nano editor 
2. Start the service and verify it is running
   1. systemctl start cribl
   2. systemctl status -l cribl 
   3. Verify the service is started successfully and returns "active and running".
3. If the service does not start do not proceed and double check the steps above are completed. 

Configure Defender Zero Trust Webhooks

1. The next step creates an Zero Trust Webhook URL.    
   
   1. Configure Zero Trust endpoint in Integrations icon, Webhooks tab.
      1. Recommended Configuration: Only Critical and Major events and only the webhooks that set lockout or delayed lockout.   Customers can customize based on specific requirements. The goal is to send findings versus a list of alarms that do not pinpoint a security incident.
      2.    
      3. The endpoint url above will use localhost and will send Webhooks to the application service listening on port 5000. URL to use in the configuration
         1. http://localhost:5000/webhook
         2. Add the Content-Type header with value of application/json as shown above to complete the webhook configuration.
         3. Click save to commit the configuration.
         4. Click save on the main Webhook configuration page
2. Test the configuration is working following the next section

How to test the Integration with cribl

1. To test the integration follow these steps
   1. download this curl command template and open with a text editor
   2. Copy all the text
   3. ssh to the eyeglass vm as the admin user
   4. paste the entire cli command to the ssh prompt to send sample data to the running Zero Trust application.  This will send test data directly to the application to be processed and sent to cribl.
   5. The output of a successfully processed webhook test will return this text in the ssh terminal
      1. done sending event to abssiem and check for http 200 and success count in response
   6. How to review the process logs from the web application
      1. sudo -s 
      2. journalctl -f -u cribl 
      3. This allows you to view the logs generated by the application.
      4. To log to a file and review with nano showing only the most recent 250 lines.
      5. journalctl -f -n 250 -u   > /tmp/ztwebhook.log
      6. nano /tmp/.log
      7. In the log below the response code from the cribl api call should show http 200 status code and successCount 1 to indicate the Finding was successfully created.
      8.   You can also view .log for specific error messages.
   7. Login to the cribl Main Dashboard to run a search for all supernaZT source messages.  enter a search with sourcetype="supernaZT" to locate events sent from testing.
2. Done

Cribl Administrator Integration Experience

1.  
2. 
3. HEC formatted event data
   1.