CrowdStrike Next-Gen SIEM Zero Trust Log Ingestion and Alerting

• Overview
• Limitations
• Solution Overview
• Video Demo
• Advanced Zero Trust Capabilities
• Quick Start from Marketplace
• What is CrowdStrike Next-Gen SIEM?
• Integration Architecture
• Solution Configuration in CrowdStrike Next-Gen SIEM and Defender Zero Trust
• Prerequisites
• Configuration in CrowdStrike Next-Gen SIEM from the Marketplace
• 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 CrowdStrike integration python code
• Configure Defender Zero Trust Webhooks
• How the Integration works CrowdStrike Next-Gen SIEM
• How to test the Integration with CrowdStrike Next-Gen SIEM

Overview

Customers using CrowdStrike Next-Gen SIEM can now leverage a native integration that  ingests root cause Cyber Storage events to show as Security events . See Crowdstrike integration landing page 

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. None

Solution Overview

Superna Defender Zero Trust API receives webhook alerts from Security Edition and maps all relevant data fields into the CrowdStrike Parsing Standard (CPS). 

Video Demo

Advanced Zero Trust Capabilities

1. Webhook to native CrowdStrike SIEM ingestion API and log parsing
2. Superna Security Edition host Containment api integration with CrowdStrike Next-Gen SIEM

Quick Start from Marketplace

1. Follow this link to the martetplace listing and click Configure to get started. https://falcon.us-2.crowdstrike.com/store-v2/ddb610cacfc349e4a75bac253d7df550
2.   Create the connecto and parsing instance and generate an API key can skip to section on configuring Eyeglass VM below.

What is CrowdStrike Next-Gen SIEM?

Integration Architecture

Solution Configuration in CrowdStrike Next-Gen SIEM and Defender Zero Trust

Prerequisites

1. Installed Security Edition
2. Eyeglass OS appliance version 15.5
   1. cat /etc/os-release
3. License key for the Zero Trust API 
4. CrowdStrike Next-Gen SIEM application entitlement

Configuration in CrowdStrike Next-Gen SIEM from the Marketplace

Follow these steps in the Next-Gen SIEM Data Onboarding to install the connector and collect api keys and url to be used with Superna Data Security Edition.

1. Log in to the CrowdStrike Falcon Console Select Data Onboarding

   1.  Type Superna in the Data Source Search box

      1. 
2. Click the connector and fill in the fields 
   1.  
   2. Click Save
3. Click Generate API key when the window appears
   1. 
   2. Save the key for use in later steps
4. Click on Data Sources and click on the new data source and record the API URL
   1.   
   2. Save this url for later steps

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 CrowdStrike Next-Gen SIEM  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 CrowdStrike Next-Gen SIEM

Configuration Step by Step

Configure the Service start and python integration files

1. Login to eyeglass vm using ssh as the admin user to create zero trust application
   1. sudo -s 
   2. mkdir -p /opt/superna/cgi-bin
   3. touch /opt/superna/cgi-bin/crowdstrikesiem.py
   4. touch /opt/superna/cgi-bin/crowdstrikesiem.sh 
   5. chown sca:users /opt/superna/cgi-bin/crowdstrikesiem.*
   6. chmod +x  /opt/superna/cgi-bin/crowdstrikesiem.py 
   7. chmod +x /opt/superna/cgi-bin/crowdstrikesiem.sh 
2. Create systemd configuration
   1. nano  /etc/systemd/system/CrowdStrikeSIEM.service
   2. Copy the values below and Paste these contents into the file opened in nano editor in the step above
   3. Save the file 
      1. press control+x
      2. Answer yes to save and exit
3. Restart systemd
   1. systemctl daemon-reload
4. Set to enabled
   1. systemctl enable CrowdStrike
5. Create CrowdStrike.sh service script
   1. Copy the values below
   2. nano /opt/superna/cgi-bin/crowdstrikesiem.sh
   3. paste the script values below into the nano editor
   4. Save the file
      1. press control+x
      2. Answer yes to save and exit the editor
6. Once the script is created below,  do not start the service at this step.
7. Done

Configure the python packages and customize the CrowdStrike integration python code

1. Now install required python packages for the SCA users that will run the service.  NOTE this is the same user that runs the main eyeglass application code.
   3. su - sca 
   4. pip3 install flask boto3 requests logging
   5. exit 
   6. NOTE: you must type exit to ensure you are the root user for the remaining steps.  Type whoami to make sure you are the root user.
2. Customize the application code by downloading the python code from this link to download
   3. Open the python template file in a text editor. NOTE: make sure to only replace the values and do not delete any of the commas
   4. Locate this section in the file # Define the endpoint and API token as variables to add your CrowdStrike api token and endpoint for API calls . 
      3.  Add the API URL and API token into this section.
      4.  

3. nano /opt/superna/cgi-bin/crowdstrikesiem.py
4. Open the file locally in Windows OS notepad and use control-A or select all the text in the python template
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 
7. Start the service and verify it is running
   1. systemctl start CrowdStrike
   2. systemctl status -l CrowdStrike 
   3. Verify the service is started successfully and returns "active and running".
   4. 
      
8. 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 Ransomware Defender Zero Trust 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 the Integration works CrowdStrike Next-Gen SIEM 

1.  These screenshots show how log messages appear when searching for raw logs and how Detections appear in the Console.
2. Log message in CPS format
   1. 
3. Detections Example
   1.  

How to test the Integration with CrowdStrike Next-Gen SIEM

1. To test the integration follow these steps
2. Prerequisites In CrowdStrike Next-Gen SIEM and Eyeglass:
   1. Download this curl command template and open with a text editor.
   2. ssh to the eyeglass vm as the admin user
   3. Copy and Paste the entire cli command text 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 CrowdStrike Next-Gen SIEM Integration service that is running on the Eyeglass VM.
   4. The output of a successfully processed webhook test will return this text in the ssh terminal
      1. done sending event to CrowdStrike and check for http 200 and success count in response
   5. How to review the process logs from the web application
      1. sudo -s 
      2. journalctl -f -u CrowdStrike 
      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 CrowdStrike  > /tmp/ztwebhook.log
      6. nano /tmp/CrowdStrike.log
      7. In the log below the response code from the CrowdStrike Next-Gen SIEM api call should show http 200 status code and successCount 1 to indicate the Finding was successfully created.
      8.   You can also view CrowdStriked.log for specific error messages.
   6. Login to the CrowdStrike Next-Gen SIEM and verify new incident is raised.
3. Done