CrowdStrike Endpoint Protection Zero Trust Host Containment Integration

• Overview
• Limitations
• Solution Overview
• Video Demo
• Advanced Zero Trust Capabilities
• What is CrowdStrike Endpoint Protection?
• Integration Architecture
• Solution Configuration in CrowdStrike Endpoint Protection and Defender Zero Trust
• Prerequisites
• Configuration in CrowdStrike Endpoint Protection
• 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 with Host Containment Automaton
• How to test the Integration with CrowdStrike Endpoint Protection
• CrowdStrike Endpoint Protection SecOps administrators Integration Experience
• How to Configure Data Security Essentials
• Overview
• Requirements
• Features
• Steps to Configure Event Sync to Crowdstrike Host Containment Integration

Overview

Customers using CrowdStrike Endpoint Protection solution can now leverage a native integration that initiates native API integration to isolate hosts where flagged as compromised by Superna Security Edition.  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 takes account against the endpoint host that is flagged in a security incident of type critical.  This integration with endpoint protection helps protect the customers infrastructure from a host that  could launch additional attacks on IT infrastructure.

Video Demo

Advanced Zero Trust Capabilities

1. Webhook to native CrowdStrike API
2. Superna Security Edition host Containment api integration with Falcon Endpoint protection

What is CrowdStrike Endpoint Protection?

Integration Architecture

Solution Configuration in CrowdStrike Endpoint Protection 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 Endpoint Protection

Configuration in CrowdStrike Endpoint Protection

To generate an API token in CrowdStrike Falcon, you'll need to follow these steps.

1. Log in to the CrowdStrike Falcon Console:

   • Open your web browser and navigate to the CrowdStrike Falcon console login page.
   • Enter your credentials and log in.

2. Navigate to the API Clients and Keys Section:

   • Once logged in, go to the “Support” section on the left-hand menu.
   • Select “API Clients and Keys.”
   • 
     

3. Create a New API Client:

   • Click on the “Add new API client” button.
   • Fill in the necessary details for the new API client:
     • Name: Provide a name for the API client.
     • Description: Optionally, provide a description for the API client.

4. Assign Permissions:

   • Select the permissions that the API client will need. This depends on the level of access required for your use case.
   • Permissions can be granted for various functionalities like sensor download, device management, event streams, etc.
   • Superna Zero Trust Integration requires: 
     • Host and asset  scope with Read and Write permissions
     • 
       

5. Generate the API Key:

   • After assigning the necessary permissions, click on the “Create” button.
   • The API client credentials, including the Client ID and Secret, will be displayed. Make sure to copy and securely store these credentials, as they will not be shown again. Record the endpoint as well.
   • 
     

6. Once you have generated the API token (Client ID and Secret), you can use these credentials to authenticate your API requests to CrowdStrike Falcon and update the provided integration code in this guide.

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 Endpoint Protection  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 Endpoint Protection

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/CrowdStrike.py
   4. touch /opt/superna/cgi-bin/CrowdStrike.sh 
   5. chown sca:users /opt/superna/cgi-bin/CrowdStrike.*
   6. chmod +x  /opt/superna/cgi-bin/CrowdStrike.py 
   7. chmod +x /opt/superna/cgi-bin/CrowdStrike.sh 
2. Create systemd configuration
   1. nano  /etc/systemd/system/CrowdStrike.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/CrowdStrike.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 and replace the yellow sections to match your CrowdStrike api token and endpoint for API calls . 
      3.  
         # Your CrowdStrike API credentials
         client_id = 'xxxxxxxxx'
         client_secret = 'yyyyyyyyyyyy'
         
         
         # The API base URL for CrowdStrike
         base_url = "https://api.us-2.crowdstrike.com"

3. nano /opt/superna/cgi-bin/crowdstrike.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 with Host Containment Automaton 

1.  These screenshots show what a host will look like when Security Edition contains the host from the network after a NAS security detection.
   1. 
      
   2. The Actions menu can be used to change the containment status to allow the client to rejoin the network.
      1.   
      2.  
2. Done

How to test the Integration with CrowdStrike Endpoint Protection

1. To test the integration follow these steps
2. Prerequisites In CrowdStrike Endpoint Protection and Eyeglass:
   1. install the CrowdStrike Endpoint Protection agent on a test machine.  Record the ip address of this test machine.
   2. Get the ip address of the Eyeglass vm
   3. download this curl command template and open with a text editor and locate the ip address of eyeglass at the very end of text and replace the ip address with the IP address of your eyeglass vm.
      1. Also edit the client ip section of the curl command by searching the text clientIPs":["172.31.1.45"] and replace only the ip address with the IP of the test machine running the CrowdStrike Endpoint Protection agent. 
      2. Edit the section below and add the client_id and client_secret with values from the Crowdstrike Console.
      3. # Your CrowdStrike API credentials
         client_id = 'xxxxx'
         client_secret = 'yyyyyy'
      4. Update the base url if needed.
         1. # The API base URL for CrowdStrike
            base_url = "https://api.us-2.crowdstrike.com"
      5. This will now simulate a zero trust alert on this host when the curl command sends the webhook payload to the integration python code to process. 
         
   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 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 Endpoint Protection Integration service that is running on the Eyeglass VM.
   7. 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
   8. 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 Endpoint Protection 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.
   9. Login to the CrowdStrike Endpoint Protection and verify new incident is raised.
3. Done

CrowdStrike Endpoint Protection SecOps administrators Integration Experience 

Overview:  Once configured, Superna Endpoint protection integration with CrowdStrike enables real time host isolation for critical ransomware events detected at the storage layer.   This ensures the compromised host cannot launch attacks on other IT infrastructure by leveraging the host api with CrowdStrikes API.

How to Configure Data Security Essentials

Overview

Data Security Essentials saves alerts to the Windows Event log to a custom application log.   This integration will extract the log entries and the json payload contained within them and format as webhook data to send to Crowdstrike to issue the host containment to the endpoint provided by Crowdstrike.

Requirements

1. Follow the Crowdstrike integration steps above to configure the Scripted REST API endpoint integration.
2. Install python for Windows on the Data Security Essentials host and allow the installation to add python to the path variable. https://www.python.org/downloads/windows/
   1. NOTE: Ensure it's installed for all users so service accounts have access, by enabling for all users during installation.
3. The integration code matches event log entries from Custom trigger BOT policies and File management policies
   1. The event log source names are below 
      1. Superna Data Security Essentials BOT Service
      2. Superna Data Security Policy Engine 

Features

1. Logs for each execution are stored in the path below along with the python code. 
   1.  
2. Each execution will store the event log record ID and date time and event number of the last processed event in a file called last_processed_record.txt.  This file is read on each execution to continue processing from last record.  The record number is not visible in Event Viewer, the date time and event number can be used to understand where in the log the last processing occurred.
3. The schedule sync runs every minute and only processes events since the last record and logs all processing as well as event matches in the log file for debugging.
4. Only events that match the severity filter will be processed for client ip address.   The sample code defaults to Major and Critical severity events all other severities will be ignored. 

Steps to Configure Event Sync to Crowdstrike Host Containment Integration

1. Download the integration code from here.
2. Modify the python and update the Crowdstrike integration settings highlighted in yellow to match your environment.
   1. # CrowdStrike API credentials
      client_id = 'xxxxxx'
      client_secret = 'yyyyyyy'
      base_url = "https://api.us-2.crowdstrike.com"
      
      
      # Configuration
      server = 'localhost'
      log_name = 'Data Security Essentials'
      source_names = ['Superna Data Security Essentials BOT Service', 'Superna Data Security Policy Engine']
      trigger_severities = ['MAJOR', 'CRITICAL','WARNING'] # Configure severities that should trigger containment
      enable_isolation = True # Set to False to disable isolation actions
3. Copy the Python code into C:\Program Files\Superna\cgi-bin on the Data Security Essentials host and name the file crowdstrike-dse.py
4. Install python dependancies
   1. MANDATORY Step: Open a command prompt as the service account (hold down shift and right click the command prompt icon) run as  option to login as the service account dse-service.  This is required to install the python packages under the correct user account.
   2. Install the dependencies with this command
      1. pip install pywin32 requests
   3. This command installs the windows API python libraries needed to read the event log.
5. Test the script can correctly reach your Crowdstrike instance from a dos prompt
   1. cd C:\Program Files\Superna\cgi-bin
   2. python  crowdstrike-dse.py
      
   3. The output should display event log entries that match  and  will ignore severities that do not match script settings .  It will display the event payload details in json format and will show the data that was sent to the Crowdstrike endpoint.   
   4. Example output
      1.   
   5. You can also review this file last_processed_record.txt to see the last date and time within the event log and event id that was last processed.  This file can be deleted to have the script start reading from the oldest windows event log entry.  This can be done for testing puposes.
   6. The above examples shows the output when a client ip address is successfully located and the host containment api returns success.
   7. The example below is logged when event data is processed and inspected for client ip and matching severity.
      1. Right Click here to download and save and open. 
6. Steps to Schedule sync alerts into Crowdstrike Security Incidents 
   1. Open secpol.msc, Local policies
   2. Give the Data security essentials AD service account the  "Logon as a batch job"  OS permission.
   3.   
   4. Create a file 
7. Right click this link to save to a file. The task scheduler XML file to import into Task Scheduler
   1. You can rename the xml from Servicenow alert sync.xml to Crowdstrike integration.xml. 
8. Open Task Scheduler
   1. Run taskschd.msc, right click task schedule library 
   2.   
   3. Import the xml file
   4. You will be prompted with the task definition, you will need to change the service account to match your service account name and domain and re-enter the password to save the task scheduler.  All other settings are configured and match the path and settings used above.  Adjust any parameters that you changed if you did not use all the steps above. 
      1. Edit the name "Crowdstrike Containment integration"
      2. Click the Actions tab and browse to select the file C:\Program Files\Superna\cgi-bin\crowdstrike-dse.py
      3. Click ok to save 
      4.   
   5. done.