Collect Imperva CEF logs

This document explains how to ingest Imperva CEF logs to Google Security Operations using Bindplane. The parser extracts the logs in CEF format from syslog messages, converting them into the UDM format. It handles various log formats, extracts key-value pairs from the payload, performs data transformations and enrichments, and maps the extracted fields to the corresponding UDM fields, including network information, user details, geolocation, and security results.

Before you begin

Make sure you have the following prerequisites:

• A Google SecOps instance
• A Windows 2016 or later or Linux host with systemd
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to the Imperva management console or appliance

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 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_file_path: '/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
       log_type: 'IMPERVA_CEF'
       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

• 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 Imperva WAF Gateway (SecureSphere) to send CEF over syslog

1. In the MX console, create an Action Set:

   • Navigate to Policies > Action Sets.
   • Click New and name it (for example, Google SecOps CEF).

2. Add the CEF syslog Action Interface:

   • In Available Action Interfaces, open System Log and add one or more of the following (as needed):
     • Log Security Event to System Log (syslog) using the CEF standard
     • Log Network Security Event to System Log (syslog) using the CEF standard
     • Log System Event to System Log (syslog) using the CEF standard
     • Log Custom Security Event to System Log (syslog) using the CEF standard

3. Configure Action Interface parameters:

   • Syslog Host: Enter your Bindplane agent IP address. To use a non-default port, append :PORT (default is 514 if you don't specify one). Example: 10.0.0.10:514.
   • Facility / Log Level: Set per your policy requirements.
   • Message: Leave vendor defaults for CEF unless you have a custom mapping.

4. Attach the Action Set to policies:

   • For Security / Network Security events: Open the relevant policy(ies) and set Followed Action to your Action Set.
   • For System Events: Create or verify a System Events policy and set Followed Action to your Action Set so those events are also sent via CEF.

5. Optional: Configure gateway-specific targets:

   • If different gateway groups must send to different syslog servers, configure each Gateway Group > External Logger and enable "Use gateway configuration if exists" in the policy.

UDM Mapping Table

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