An ingestion label identifies the parser which normalizes raw log data to structured
UDM format. The information in this document applies to the parser with the
KEMP_LOADBALANCER ingestion label.
Configure Kemp Load Balancer
Sign in to the Kemp Load Balancer console.
Select Logging options>Syslog options.
In the Syslog options section, in any of the available fields specify the
IP address of the Google Security Operations forwarder.
It is recommended to specify the IP address in the Info host field.
Click Change syslog parameters.
Configure Google Security Operations forwarder to ingest Kemp Load Balancer logs
Select SIEM Settings>Forwarders.
Click Add new forwarder.
In the Forwarder name field, enter a unique name for the forwarder.
Click Submit and then click Confirm. The forwarder is added and the Add collector configuration window appears.
In the Collector name field, type a unique name for the collector.
Select Kemp Load Balancer as the Log type.
Select Syslog as the Collector type.
Configure the following mandatory input parameters:
Protocol: specify the connection protocol that the collector uses to listen to syslog data.
Address: specify the target IP address or hostname where the collector resides and listens to syslog data.
Port: specify the target port where the collector resides and listens to syslog data.
This parser extracts fields from Kemp Load Balancer syslog messages based on the log_number field, mapping them to the UDM. It handles various log formats using grok patterns and conditional logic, converting data types and enriching events with metadata like event type, application protocol, and security results.
UDM mapping table
Log Field
UDM Mapping
Logic
collection_time.seconds
metadata.event_timestamp.seconds
Log collection time is used as event timestamp if timestamp is not present. Nanoseconds are truncated.
Key-value pairs from CEF formatted logs. Used to extract various fields.
log_event
metadata.product_event_type
Event type from CEF formatted logs.
log_time
metadata.event_timestamp.seconds
Log timestamp. Converted to Chronicle format and used as event timestamp. Nanoseconds are truncated.
msg/message
See data
Contains the main log message. See data for UDM mapping details.
pid
target.process.pid
Process ID.
resource
target.url
Resource accessed.
srcip
principal.ip
Source IP address.
src_ip
principal.ip
Source IP address.
srcport
principal.port
Source port.
src_port
principal.port
Source port.
sshd
target.application
SSH daemon name.
summary
security_result.summary
Summary of the security result.
timestamp.seconds
events.timestamp.seconds
Log entry timestamp. Used as event timestamp if present.
user
target.user.userid
Username.
vs
target.ip | target.port
Virtual server IP and port. IP is mapped to target.ip. Port is mapped to target.port if dstport is not present.
vs_port
target.port
Virtual server port. Determined by logic based on log_number, dest_port, login_status, and log_event. Possible values include GENERIC_EVENT, NETWORK_HTTP, NETWORK_CONNECTION, USER_LOGIN, and USER_UNCATEGORIZED. Hardcoded to "KEMP_LOADBALANCER". Hardcoded to "KEMP_LOADBALANCER". Hardcoded to "KEMP". Determined by dest_port. Possible values are HTTP (port 80) and HTTPS (port 443). Determined by login_status and audit_msg. Possible values are ALLOW and BLOCK. Determined by audit_msg. Possible value is ERROR. Set to "AUTHTYPE_UNSPECIFIED" for USER_LOGIN events.
[[["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."],[[["\u003cp\u003eThis document explains how to collect Kemp Load Balancer logs using a Google Security Operations forwarder, which supports parsing logs with the \u003ccode\u003eKEMP_LOADBALANCER\u003c/code\u003e ingestion label.\u003c/p\u003e\n"],["\u003cp\u003eTo configure Kemp Load Balancer, you must specify the IP address of the Google Security Operations forwarder in the Syslog options, and then add a new forwarder and collector in SIEM Settings with specific details including protocol, address, and port.\u003c/p\u003e\n"],["\u003cp\u003eThe parser extracts various fields from Kemp Load Balancer syslog messages, based on the log number, mapping them to the UDM, and includes fields such as \u003ccode\u003eprincipal.ip\u003c/code\u003e, \u003ccode\u003etarget.ip\u003c/code\u003e, \u003ccode\u003enetwork.http.method\u003c/code\u003e, and \u003ccode\u003esecurity_result.summary\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe document provides a detailed UDM mapping table showing how Kemp Load Balancer log fields are mapped to UDM fields, along with the logic used for data conversion and enrichment.\u003c/p\u003e\n"],["\u003cp\u003eRecent updates include improvements to the parsers that now includes events like "connected", "slave accept", and "block access to host", alongside mapping of additional fields like source and destination IPs and ports.\u003c/p\u003e\n"]]],[],null,["# Collect Kemp Load Balancer 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 describes how you can collect Kemp Load Balancer logs by using a\nGoogle Security Operations forwarder.\n\nFor more information, see [Data ingestion to Google Security Operations](/chronicle/docs/data-ingestion-flow).\n\nAn ingestion label identifies the parser which normalizes raw log data to structured\nUDM format. The information in this document applies to the parser with the\n`KEMP_LOADBALANCER` ingestion label.\n\nConfigure Kemp Load Balancer\n----------------------------\n\n1. Sign in to the **Kemp Load Balancer** console.\n2. Select **Logging options** \\\u003e **Syslog options**.\n3. In the **Syslog options** section, in any of the available fields specify the\n IP address of the Google Security Operations forwarder.\n\n It is recommended to specify the IP address in the **Info host** field.\n4. Click **Change syslog parameters**.\n\nConfigure Google Security Operations forwarder to ingest Kemp Load Balancer logs\n--------------------------------------------------------------------------------\n\n1. Select **SIEM Settings** \\\u003e **Forwarders**.\n2. Click **Add new forwarder**.\n3. In the **Forwarder name** field, enter a unique name for the forwarder.\n4. Click **Submit** and then click **Confirm** . The forwarder is added and the **Add collector configuration** window appears.\n5. In the **Collector name** field, type a unique name for the collector.\n6. Select **Kemp Load Balancer** as the **Log type**.\n7. Select **Syslog** as the **Collector type**.\n8. Configure the following mandatory input parameters:\n - **Protocol**: specify the connection protocol that the collector uses to listen to syslog data.\n - **Address**: specify the target IP address or hostname where the collector resides and listens to syslog data.\n - **Port**: specify the target port where the collector resides and listens to syslog data.\n9. Click **Submit**.\n\nFor more information about the Google Security Operations forwarders, see [Manage forwarder configurations through the Google Security Operations UI](/chronicle/docs/install/forwarder-management-configurations).\n\nIf you encounter issues when you create forwarders, contact [Google Security Operations support](/chronicle/docs/getting-support).\n\nField mapping reference\n-----------------------\n\nThis parser extracts fields from Kemp Load Balancer syslog messages based on the `log_number` field, mapping them to the UDM. It handles various log formats using `grok` patterns and conditional logic, converting data types and enriching events with metadata like event type, application protocol, and security results.\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)"]]