Collect AlgoSec Security Management logs

This document explains how to ingest AlgoSec Security Management logs to Google Security Operations using a Bindplane Agent. The parser extracts the fields, handling both CEF and non-CEF formatted logs. It parses common fields like timestamps, IP addresses, and event details, then maps them to the UDM based on the product (Suite, Firewall Analyzer, FireFlow) and event ID, setting appropriate metadata and security result fields. It also handles specific event types like login/logout, administrative alerts, and analysis reports, extracting relevant details and setting severity levels.

Before you begin

• Ensure that you have a Google SecOps instance.
• Ensure that you are using Windows 2016 or later, or a Linux host with systemd.
• If running behind a proxy, ensure firewall ports are open.
• Ensure that you have privileged access to AlgoSec Firewall Analyzer, FireFlow and AppViz.

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

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 this installation guide.

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

1. Access the configuration file:

   1. Locate the config.yaml file. Typically, it's in the /etc/bindplane-agent/ directory on Linux or in the installation directory on Windows.
   2. 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: '/path/to/ingestion-authentication-file.json'
           # Replace with your actual customer ID from Step 2
           customer_id: <customer_id>
           endpoint: malachiteingestion-pa.googleapis.com
           # Add optional ingestion labels for better organization
           ingestion_labels:
               log_type: ALGOSEC
               raw_log_field: body
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - udplog
               exporters:
                   - chronicle/chronicle_w_labels
   

3. Replace the port and IP address as required in your infrastructure.

4. Replace <customer_id> with the actual customer ID.

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

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

  sudo systemctl restart bindplane-agent
  

• 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
  

Configure Syslog for Firewall Analyzer

1. Sign in to the AFA appliance using SSH.

2. Go to the syslog-ng configuration directory:

   cd /etc/syslog-ng
   

3. Backup the existing configuration:

   cp syslog-ng.conf syslog-ng.conf.orig
   

4. Edit the syslog-ng configuration file:

   vi syslog-ng.conf
   

5. Add the following lines to define the remote syslog server:

   destination d_remote {
       udp("<bindplane-server-ip>" port(514));
   };
   
   log {
       source(s_sys);
       destination(d_remote);
   };
   

   • Replace <bindplane-server-ip> with the IP address of the Bindplane agent.

6. Save and exit the editor.

7. Restart the syslog-ng service to apply changes:

   service syslog-ng restart
   

8. Optional: Verify Syslog Configuration:

   1. Go to Administration > Syslog Server Settings.
   2. Click Test Connectivity.

Configure Syslog for FireFlow

1. Sign in to the FireFlow machine as root.

2. Open the /etc/syslog.conf file for editing.

   vi /etc/syslog.conf
   

3. Add the following line to the file: local0.*@<BindplaneAgent>.

   • Replace <BindplaneAgent> with the IP address of the Bindplane agent server.

Configure Syslog for AppViz

1. Sign in to the AppViz appliance via SSH.

2. Go to the syslog-ng configuration directory:

   cd /etc/syslog-ng
   

3. Backup the existing configuration:

   cp syslog-ng.conf syslog-ng.conf.orig
   

4. Edit the syslog-ng configuration file:

   vi syslog-ng.conf
   

5. Add the following to define the remote syslog server:

   destination d_remote {
       udp("<bindplane-server-ip>" port(514));
   };
   
   log {
       source(s_sys);
       destination(d_remote);
   };
   

   • Replace <bindplane-server-ip> with the IP address of the Bindplane agent.

6. Save and exit the editor.

7. Restart the syslog-ng service to apply changes:

   service syslog-ng restart
   

8. Verify Syslog Configuration:

   1. In the AppViz interface, go to Administration > Syslog Server Settings.
   2. Click Test Connectivity.

Configure Syslog for Login and Logout Events

1. Sign in to the ASMS appliance via SSH.

2. Go to the syslog-ng configuration directory:

   cd /etc/syslog-ng
   

3. Backup the existing configuration:

   cp syslog-ng.conf syslog-ng.conf.orig
   

4. Edit the syslog-ng configuration file:

   vi syslog-ng.conf
   

5. Add the following to define the remote syslog server:

   destination d_remote {
       udp("<bindplane-server-ip>" port(514));
   };
   
   log {
       source(s_sys);
       destination(d_remote);
   };
   

   • Replace <bindplane-server-ip> with the IP address of your syslog server.

6. Save and exit the editor.

7. Restart the syslog-ng service to apply changes:

   service syslog-ng restart
   

UDM Mapping Table

Changes

2022-11-27

Enhancement:

• Parsed CEF format and grok related unparsed logs by adding event specific conditional block to handle them.
• Also added a drop tag to drop malformed logs.

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