Collect F5 BIG-IP ASM logs

This document explains how to ingest F5 BIG-IP Application Security Manager (ASM) logs to Google Security Operations by using Bindplane. The parser handles various log formats (syslog, CSV, CEF, etc.) and normalizes them into UDM. It uses grok patterns and key-value extractions to parse fields, XML filtering for violation details, conditional logic for event categorization and severity mapping, and merges extracted fields into the UDM schema.

Before you begin

• Ensure that you have a Google Security Operations 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 F5 BIG-IP ASM.

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: F5_ASM
               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 Remote Logging on F5 BIG-IP ASM

1. Sign in to the ASM Console Web UI.
2. Go to Security > Event Logs > Logging Profiles.
3. Click Create.

4. Provide the following configuration details:

   • Profile Name: enter a unique name for the profile.
   • Select Application Security.
   • On the Application Security tab, select Advanced (if additional configurations are required).
   • Storage Destination: select Remote Storage.
   • Logging Format: Select Common Event Format (CEF).
   • Clear Local storage.
   • Protocol: select UDP or TCP (depending on your Bindplane agent configuration).
   • Server Addresses: enter the Bindplane agent IP Address.
   • Port: selected by default 514. Update the port setting according to your Bindplane agent configuration.
   • Click Add.
   • Select Guarantee logging.
   • Select Report detected anomalies.
   • Facility: select LOG_LOCAL6 (you can optionally select the facility category of the logged traffic, the possible values are LOG_LOCAL0 through LOG_LOCAL7).

5. Click Finished.

Associate a logging profile with a security policy

1. Click Local Traffic > Virtual Servers.
2. Click the name of the virtual server used by the security policy.
3. From the Security menu, select Policies.
4. Ensure that the Application Security Policy setting is Enabled, and that Policy is set to the security policy you want.
5. Ensure that the Log Profile setting is set to Enabled.
6. From the Available list, select the profile to use for the security policy, and move it into the Selected list.
7. Click Update.

UDM Mapping Table

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