This document explains how to ingest Cisco PIX logs to Google Security Operations
using Bindplane. The parser extracts fields from the firewall syslog messages
using regular expressions (grok patterns) and conditional logic. It then maps
these extracted fields to the Unified Data Model (UDM), categorizing events as
network connections, status updates, or generic events based on the presence of
source and destination IP addresses.
Before you begin
Make sure you have the following prerequisites:
A Google SecOps instance
Windows 2016 or later, or a Linux host with systemd
If running behind a proxy, ensure firewall ports are open
Privileged access to the Cisco PIX Firewall appliance
Get Google SecOps ingestion authentication file
Sign in to the Google SecOps console.
Go to SIEM Settings > Collection Agents.
Download the Ingestion Authentication File.
Save the file securely on the system where Bindplane will be installed.
Get Google SecOps customer ID
Sign in to the Google SecOps console.
Go to SIEM Settings > Profile.
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
Open the Command Prompt or PowerShell as an administrator.
Configure the Bindplane agent to ingest Syslog and send to Google SecOps
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).
Edit the config.yaml file as follows:
receivers:udplog:# Replace the port and IP address as requiredlisten_address:"0.0.0.0:514"exporters:chronicle/chronicle_w_labels:compression:gzip# Adjust the path to the credentials file you downloaded in Step 1creds_file_path:'/path/to/ingestion-authentication-file.json'# Replace with your actual customer ID from Step 2customer_id:<customer_id>
endpoint:malachiteingestion-pa.googleapis.com# Add optional ingestion labels for better organizationlog_type:'CISCO_PIX_FIREWALL'raw_log_field:bodyingestion_labels:service:pipelines:logs/source0__chronicle_w_labels-0:receivers:-udplogexporters:-chronicle/chronicle_w_labels
Replace the port and IP address as required in your infrastructure.
Replace <customer_id> with the actual customer ID.
To restart the Bindplane agent in Linux, run the following command:
sudosystemctlrestartbindplane-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 on Cisco PIX Firewall
Sign in to your Cisco PIX appliance using SSH or a console connection.
Enter the following for privileged mode:
enable
Enter the following command for configuration mode:
conft
Enter the following commands to enable logging and timestamp:
loggingon
loggingtimestamp
Enter the following command to configure log level:
loggingtrapinformation
Enter the following command to configure syslog information:
logginghost<interface><bindplane_IP_address>
Change <interface> to the interface that has access to your Bindplane agent.
Change <bindplane_IP_address> to your actual Bindplane agent IP address.
UDM mapping table
Log Field
UDM Mapping
Logic
datetime
metadata.event_timestamp.seconds
Convert the extracted timestamp to epoch seconds
datetime
metadata.event_timestamp.nanos
Convert the extracted timestamp to epoch nanoseconds
descrip
metadata.description
Directly mapped from the extracted descrip field
observer_ip
observer.ip
Directly mapped from the extracted observer_ip field
proto
network.ip_protocol
Directly mapped from the extracted proto field after converting to uppercase. Only mapped if the value is one of UDP, TCP, or ICMP.
src_ip
principal.ip
Directly mapped from the extracted src_ip field
src_port
principal.port
Directly mapped from the extracted src_port field after converting to integer
facility
principal.resource.type
Directly mapped from the extracted facility field
action
security_result.action_details
Directly mapped from the extracted action field
severity_level
security_result.severity
Mapped based on the value of severity_level: - 7, 6: INFORMATIONAL - 5: LOW - 4: MEDIUM - 3: ERROR - 2: HIGH - Otherwise: CRITICAL
dest_ip
target.ip
Directly mapped from the extracted dest_ip field
dest_port
target.port
Directly mapped from the extracted dest_port field after converting to integer
direction
network.direction
Mapped to INBOUND if the direction field is inbound
metadata.event_timestamp.seconds
Value taken from the top level 'create_time.seconds' field
metadata.event_timestamp.nanos
Value taken from the top level 'create_time.nanos' field
metadata.event_type
Determined based on the presence of src_ip and dest_ip: - Both present: NETWORK_CONNECTION - Only src_ip present: STATUS_UPDATE - Otherwise: GENERIC_EVENT
metadata.product_event_type
Concatenation of facility, -, severity_level, -, and mnemonic fields.
metadata.product_name
Hardcoded value: CISCO_FWSM
metadata.vendor_name
Hardcoded value: CISCO
security_result.action
Mapped to BLOCK if the action field is one of Deny, Teardown, denied, or Denied.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Collect Cisco PIX logs\n======================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nThis document explains how to ingest Cisco PIX logs to Google Security Operations\nusing Bindplane. The parser extracts fields from the firewall syslog messages\nusing regular expressions (grok patterns) and conditional logic. It then maps\nthese extracted fields to the Unified Data Model (UDM), categorizing events as\nnetwork connections, status updates, or generic events based on the presence of\nsource and destination IP addresses.\n\nBefore you begin\n----------------\n\nMake sure you have the following prerequisites:\n\n- A Google SecOps instance\n- Windows 2016 or later, or a Linux host with `systemd`\n- If running behind a proxy, ensure firewall [ports](/chronicle/docs/ingestion/use-bindplane-agent#verify_the_firewall_configuration) are open\n- Privileged access to the **Cisco PIX Firewall** appliance\n\nGet Google SecOps ingestion authentication file\n-----------------------------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Collection Agents**.\n3. Download the **Ingestion Authentication File** .\n - Save the file securely on the system where Bindplane will be installed.\n\nGet Google SecOps customer ID\n-----------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Profile**.\n3. Copy and save the **Customer ID** from the **Organization Details** section.\n\nInstall the Bindplane agent\n---------------------------\n\nInstall the Bindplane agent on your Windows or Linux operating system according\nto the following instructions.\n\n### Windows installation\n\n1. Open the **Command Prompt** or **PowerShell** as an administrator.\n2. Run the following command:\n\n msiexec /i \"https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi\" /quiet\n\n### Linux installation\n\n1. Open a terminal with root or sudo privileges.\n2. Run the following command:\n\n sudo sh -c \"$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)\" install_unix.sh\n\n### Additional installation resources\n\nFor additional installation options, consult the [installation guide](/chronicle/docs/ingestion/use-bindplane-agent#install_the_bindplane_agent).\n\nConfigure the Bindplane agent to ingest Syslog and send to Google SecOps\n------------------------------------------------------------------------\n\n1. Access the configuration file:\n - Locate the `config.yaml` file. Typically, it's in the `/etc/bindplane-agent/` directory on Linux or in the installation directory on Windows.\n - Open the file using a text editor (for example, `nano`, `vi`, or Notepad).\n2. Edit the `config.yaml` file as follows:\n\n receivers:\n udplog:\n # Replace the port and IP address as required\n listen_address: \"0.0.0.0:514\"\n\n exporters:\n chronicle/chronicle_w_labels:\n compression: gzip\n # Adjust the path to the credentials file you downloaded in Step 1\n creds_file_path: '/path/to/ingestion-authentication-file.json'\n # Replace with your actual customer ID from Step 2\n customer_id: \u003ccustomer_id\u003e\n endpoint: malachiteingestion-pa.googleapis.com\n # Add optional ingestion labels for better organization\n log_type: 'CISCO_PIX_FIREWALL'\n raw_log_field: body\n ingestion_labels:\n\n service:\n pipelines:\n logs/source0__chronicle_w_labels-0:\n receivers:\n - udplog\n exporters:\n - chronicle/chronicle_w_labels\n\n - Replace the port and IP address as required in your infrastructure.\n - Replace `\u003ccustomer_id\u003e` with the actual customer ID.\n - Update `/path/to/ingestion-authentication-file.json` to the path where the authentication file was saved in the [Get Google SecOps ingestion authentication file](/chronicle/docs/ingestion/default-parsers/cisco-pix-firewall#get-auth-file) section.\n\nRestart the Bindplane agent to apply the changes\n------------------------------------------------\n\n- To restart the Bindplane agent in **Linux**, run the following command:\n\n sudo systemctl restart bindplane-agent\n\n- To restart the Bindplane agent in **Windows** , you can either use the **Services** console or enter the following command:\n\n net stop BindPlaneAgent && net start BindPlaneAgent\n\nConfigure Syslog on Cisco PIX Firewall\n--------------------------------------\n\n1. Sign in to your Cisco PIX appliance using SSH or a console connection.\n2. Enter the following for **privileged** mode:\n\n enable\n\n3. Enter the following command for configuration mode:\n\n conf t\n\n4. Enter the following commands to enable logging and timestamp:\n\n logging on\n logging timestamp\n\n5. Enter the following command to configure log level:\n\n logging trap information\n\n6. Enter the following command to configure syslog information:\n\n logging host \u003cinterface\u003e \u003cbindplane_IP_address\u003e\n\n - Change `\u003cinterface\u003e` to the interface that has access to your Bindplane agent.\n - Change `\u003cbindplane_IP_address\u003e` to your actual Bindplane agent IP address.\n\nUDM mapping table\n-----------------\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
