Eyeglass Solutions Publication2

Jitbit Zero Trust Alert to Ticket Integration

Home



 

Overview

Jitbit a digital operation platform that provides reliable notifications, on-call, scheduling automatic escalations, and other functionality to help teams detect and fix problems quickly.

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

Solution Overview

Superna Defender Zero Trust API receives webhook alerts and parses the key data into a HTTPS API payload events that are sent to Jitbit endpoint url.  Jitbit 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

  1. Webhook to native HTTPS collector API case creation
  2. Supports custom ticket category creation of type "Storage Security Event"
  3. Updates to state of an incident will apply a comment to an existing ticket using the event ID to locate existing case that matches the event in Data Security Edition.

What is Jitbit?

Jitbit supports various features for operations teams including incident management, on-call scheduling, automation, and integrations with other tools. It helps manage incidents from detection to resolution, automating responses and providing analytics for continuous improvement. Jitbit also offers features for customer service operations and business response. 


Integration Architecture



Solution Configuration in Jitbit and Data Security Edition 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. Jitbit
    1. Service account for creating tickets 


Configuration in Jitbit

The steps below create the integration,.

  1. Login to Jitbit console
  2. Create a user to be used as a service account and disable email notifications.
    3. Disable email notifications and new ticket notifications
    5. Configure as regular user
    6. Set the password and record for use in the integration
  3. 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 Data Security Edition
  5. Update the main script to customize with Jitbit  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 Jitbit

Configuration Step by Step

Configure the Service start and python integration files
  1. Login 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

    # become SCA user

    sudo -u sca -s

    cd /opt/superna/cgi-bin

    python3 -m venv venv-jitbit

    source venv-jitbit/bin/activate

    pip install flask requests

    deactivate


    # Create required files
    touch jitbit.py
    touch jitbit.sh

    # Make scripts executable
    chmod +x jitbit.py
    chmod +x jitbit.sh

    # Create the jitbit.sh launch script
    nano /opt/superna/cgi-bin/jitbit.sh

    # past contents below into the file 

    #!/bin/bash
    export PATH="/opt/.pyenv/bin:$PATH"
    source /opt/superna/cgi-bin/venv-jitbit/bin/activate
    exec python /opt/superna/cgi-bin/jitbit.py

    # Make the launch script executable
    chmod +x /opt/superna/cgi-bin/jitbit.sh

    ## exit from being SCA user

    exit

    whoami 

    ### make sure you are the root user again for these steps


    # Create the systemd service unit file
    nano /etc/systemd/system/jitbit.service
     

    #Paste the contents below 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/jitbit.sh
    Restart=always
    RestartSec=5

    [Install]
    WantedBy=multi-user.target


    # Reload systemd to recognize the new service
    systemctl daemon-reload

    # Enable the service to start on boot (do NOT start it yet)
    systemctl enable jitbit


Configure the python packages and customize the Jitbit integration python code
  1. Customize the application code by downloading the python code from this link to download (right click save as)
    1. 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
    2. Locate this section in the file and replace the yellow sections to match your Jitbit endpoint URL.   The endpoint url is unique and can be copied from the console into the variable below.
      1. Update the code to cover the domain name for your instance access url, username service account email,  for API Key use the password of the service account user and 
      2. # === Jitbit Configuration ===
        JITBIT_API_URL = "https://xxxxx.jitbit.com/helpdesk/api/tickets"
        JITBIT_USERNAME = "your email here"
        JITBIT_API_KEY = "xxxx" 
      3. To change the category name change the text on this line within the Quotes.
      4. CATEGORY_NAME = "Storage Security Event"
  2. nano /opt/superna/cgi-bin/Jitbit.py
  3. Open the file locally in Windows OS notepad and use control-A or select all the text in the python template
  4. Paste the clipboard into the ssh terminal session with the open nano editor file
  5. save the file
    1. press control+x
    2. Answer yes to save and exit the nano editor 
  6. Start the service and verify it is running
    1. systemctl start Jitbit.py
    2. systemctl status -l Jitbit.py 
    3. Verify the service is started successfully and returns "active and running".
  7. 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.
        1.    
      2. 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 and the content-encoding with value gzip 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 Jitbit 

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


Jitbit SecOps administrators Integration Experience 

Example tickets created by the integration.


  4.   Reply added to ticket based on state of the event change in Data Security edition
    1.  

© Superna Inc