Collect Skyhigh Security logs

This document explains how to ingest Skyhigh Security (formerly McAfee Skyhigh CASB) logs to Google Security Operations using Bindplane. The parser transforms logs from a SYSLOG + KV format into a Unified Data Model (UDM). It first normalizes the log message into key-value pairs and then maps the extracted fields to corresponding UDM attributes within the event.idm.read_only_udm object, categorizing the event type based on the presence and values of specific fields.

Before you begin

Make sure you have the following prerequisites:

• Google SecOps instance
• A Windows 2016 or later, or a Linux host with systemd
• If running behind a proxy, firewall ports are open
• Installed and configured Skyhigh Cloud Connector
• Privileged access to Skyhigh Security Cloud Connector

Get Google SecOps ingestion authentication file

1. Sign in to the Google SecOps console.
2. Go to SIEM Settings > Collection Agents.
3. Download the Ingestion Authentication File. Save the file securely on the system where Bindplane will be installed.

Get Google SecOps customer ID

1. Sign in to the Google SecOps console.
2. Go to SIEM Settings > Profile.
3. Copy and save the Customer ID from the Organization Details section.

Install the Bindplane agent

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

Windows installation

1. Open the Command Prompt or PowerShell as an administrator.

2. Run the following command:

   msiexec /i "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" /quiet
   

Linux installation

1. Open a terminal with root or sudo privileges.

2. Run the following command:

   sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)" install_unix.sh
   

Additional installation resources

For additional installation options, consult the installation guide.

Configure the Bindplane agent to ingest Syslog and send to Google SecOps

1. Access the configuration file:
   • Locate the config.yaml file. Typically, it's in the /etc/bindplane-agent/ directory on Linux or in the installation directory on Windows.
   • Open the file using a text editor (for example, nano, vi, or Notepad).

2. Edit the config.yaml file as follows:

   receivers:
       udplog:
           # Replace the port and IP address as required
           listen_address: "0.0.0.0:514"
   
   exporters:
       chronicle/chronicle_w_labels:
           compression: gzip
           # Adjust the path to the credentials file you downloaded in Step 1
           creds_file_path: '/path/to/ingestion-authentication-file.json'
           # Replace with your actual customer ID from Step 2
      <     custom>er_id: customer_id
           endpoint: malachiteingestion-pa.googleapis.com
           # Add optional ingestion labels for better organization
           log_type: 'MCAFEE_SKYHIGH_CASB'
           raw_log_field: body
           ingestion_labels:
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - udplog
               exporters:
                   - chronicle/chronicle_w_labels
   

   • Replace the port and IP address as required in your infrastructure.
   • Replace <customer_id> with the actual customer ID.
   • Update /path/to/ingestion-authentication-file.json to the path where the authentication file was saved in the Get Google SecOps ingestion authentication file section.

Restart the Bindplane agent to apply the changes

1. To restart the Bindplane agent in Linux, run the following command:

   sudo systemctl restart bindplane-agent
   

2. To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:

   net stop BindPlaneAgent && net start BindPlaneAgent
   

Prerequisites before downloading the Logging Client

Make sure you have the following details:

1. Usage Analytics User privilege: Your account must have the Usage Analytics Users role.
2. Customer ID: Perform the following steps to find your Customer ID in Skyhigh CASB:
   • Sign in to Skyhigh CASB.
   • Go to Settings > Infrastructure > Client Proxy Management.
   • Click Global Configuration > Tenant Authentication.
   • Under Global Settings, find your Customer ID displayed.
3. Email address and password: Your (or dedicated service account) log-on credentials (If you sign in using SAML without submitting a password, you can't install the Logging Client).

Download and install Skyhigh Logging Client

1. Download the Logging Client to a dedicated instance.
2. Install the Logging Client (unzip the downloaded EXE file if required).
3. After installation is completed, open the Logging Client.
4. On the Configuration page, provide the following configurations details:
   1. Customer ID: Enter you Skyhigh CASB customer ID obtained in the previous step.
   2. Service: Select SSE if you are using Skyhigh SSE, or WGCS if you are using this product together with Trellix ePO.
   3. Region: Choose a regional or country code depending on where your data is stored:
      • EU — European Union
      • IN — India
      • SG — Singapore
      • UE — United Arab Emirates
      • UK — United Kingdom
      • US — United States
   4. Name: Enter the username, which is most commonly the email address used to sign in to Secure Web Gateway, or a dedicated instance.
   5. Password: Enter the password you use to log on to Secure Web Gateway. If you log on with SAML, you can't use the Logging Client.
   6. API version: Enter version 13.
   7. Log Type: You can download different types of logs, including logs with data originating from the Web, Remote Browser Isolation (RBI), Private Access, and Cloud Firewall.
   8. Select Send as Syslogs and provide the following configuration details:
      • Syslog-Client Host: Enter the Bindplane agent IP address.
      • Syslog-Client Port: Enter the Bindplane agent port number.
      • Transport: Select UDP or TCP, depending on your Bindplane agent configuration.

UDM mapping table

Need more help? Get answers from Community members and Google SecOps professionals.