Collect iBoss Web Proxy logs

Supported in:

Google secops SIEM

This document explains how to ingest iBoss Web Proxy logs into Google Security Operations using Bindplane.

iBoss is a cloud-native Zero Trust Secure Access Service Edge (SASE) platform that provides secure internet access, Secure Web Gateway (SWG), CASB, ZTNA, and DLP capabilities. It routes traffic through its cloud infrastructure to enforce consistent security policies and threat protection for users regardless of location.

Before you begin

Make sure you have the following prerequisites:

A Google SecOps instance
Windows Server 2016 or later, or Linux host with systemd
Network connectivity between the Bindplane agent and the iBoss cloud platform
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Administrator access to the iBoss portal with permissions to configure the Integration Marketplace

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 IDfrom the Organization Detailssection.

Install the Bindplane agent

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

Windows installation

Open Command Promptor PowerShellas an administrator.

Run the following command:

  msiexec 
  
 / 
 i 
  
 "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" 
  
 / 
 quiet

Wait for the installation to complete.
Verify the installation by running:
```
 sc query observiq-otel-collector 
```
The service should show as RUNNING.

Linux installation

Open a terminal with root or sudo privileges.

Run the following command:

 sudo  
sh  
-c  
 " 
 $( 
curl  
-fsSlL  
https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh ) 
 " 
  
install_unix.sh

Wait for the installation to complete.
Verify the installation by running:
```
 sudo  
systemctl  
status  
observiq-otel-collector 
```
The service should show as active (running).

Additional installation resources

For additional installation options and troubleshooting, see Bindplane agent installation guide .

Configure Bindplane agent to ingest syslog and send to Google SecOps

Locate the configuration file

Linux:

 sudo  
nano  
/etc/bindplane-agent/config.yaml

Windows:

 notepad "C:\Program Files\observIQ OpenTelemetry Collector\config.yaml"

Edit the configuration file

Replace the entire contents of config.yaml with the following configuration:

  receivers 
 : 
  
 udplog 
 : 
  
 listen_address 
 : 
  
 "0.0.0.0:514" 
 exporters 
 : 
  
 chronicle/iboss_webproxy 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 '<CREDS_FILE_PATH>' 
  
 customer_id 
 : 
  
 '<CUSTOMER_ID>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 IBOSS_WEBPROXY 
  
 raw_log_field 
 : 
  
 body 
  
 ingestion_labels 
 : 
  
 log_source 
 : 
  
 iboss 
 service 
 : 
  
 pipelines 
 : 
  
 logs/iboss_to_chronicle 
 : 
  
 receivers 
 : 
  
 - 
  
 udplog 
  
 exporters 
 : 
  
 - 
  
 chronicle/iboss_webproxy

Configuration parameters

Replace the following placeholders:

Receiver configuration:
- listen_address : The IP address and port the Bindplane agent listens on for incoming syslog messages. Use 0.0.0.0 to listen on all interfaces. The port must match the port configured in the iBoss syslog forwarding settings.
- If iBoss is configured to send logs over TCP, replace the udplog receiver with tcplog :
```
  receivers 
 : 
  
 tcplog 
 : 
  
 listen_address 
 : 
  
 "0.0.0.0:514" 
 
```
Note: Update the receiver reference in the service.pipelines section accordingly.
Exporter configuration:
- <CREDS_FILE_PATH> : Full path to the ingestion authentication file:
  - Linux: /etc/bindplane-agent/ingestion-auth.json
  - Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
- <CUSTOMER_ID> : Google SecOps customer ID copied earlier.
- endpoint : Regional endpoint URL:
  - US: malachiteingestion-pa.googleapis.com
  - Europe: europe-malachiteingestion-pa.googleapis.com
  - Asia: asia-southeast1-malachiteingestion-pa.googleapis.com
  - See Regional Endpoints for complete list.

Save the configuration file

After editing, save the file:

Linux: Press Ctrl+O , then Enter , then Ctrl+X
Windows: Click File > Save

Restart the Bindplane agent to apply the changes

To restart the Bindplane agent in Linux, do the following:

Run the following command:

 sudo  
systemctl  
restart  
observiq-otel-collector

Verify the service is running:

 sudo  
systemctl  
status  
observiq-otel-collector

Check logs for errors:

 sudo  
journalctl  
-u  
observiq-otel-collector  
-f

To restart the Bindplane agent in Windows, do the following:

Choose one of the following options:
- Command Prompt or PowerShell as administrator:
```
 net stop observiq-otel-collector && net start observiq-otel-collector 
```
- Services console:
  1. Press Win+R , type services.msc , and press Enter.
  2. Locate observIQ OpenTelemetry Collector.
  3. Right-click and select Restart.
Verify the service is running:
```
 sc query observiq-otel-collector 
```

Check logs for errors:

  type 
  
 "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"

Configure iBoss syslog forwarding

Sign in to the iBossportal.
Go to Integration Marketplace, then select Log Forwardingfrom the left-hand menu and click the Configurebutton associated with the Syslog Log Forwardingwidget.
Click the Add Integrationbutton to add the Syslog integration.
Provide the following configuration details:
- Forward From: Select Reporterfrom the dropdown.
- Select Reporting Database: Select the Reporting Database.
- Service Name: Enter a descriptive name for the integration (for example, SecOps-Bindplane ).
- Enable Service: Set this to Enabled.
- Log Type: Select URLfrom the dropdown. This captures web proxy traffic logs (HTTP/HTTPS requests). To forward other event categories such as DLP or DNS, configure separate integrations with the corresponding log type.
- Protocol Type: Select UDPor TCPfrom the dropdown.
  
  Note: The protocol must match the receiver type configured in the Bindplane agent config.yaml file ( udplog for UDP, tcplog for TCP). TCP is recommended for production environments as it provides reliable, ordered delivery.
- Syslog Facility Level: Select Facility Syslogfrom the dropdown.
- Reporting Group: Select Allfrom the dropdown.
- Host Name: Enter the IP address or fully qualified domain name of the Bindplane agent host.
- Port: Enter the port number matching the listen_address port in the Bindplane agent configuration (for example, 514 ).
  
  Note: On Linux, port 514 is a privileged port. If the Bindplane agent runs as a non-root user, use a non-privileged port (for example, 5514 ) and update both the iBoss Portfield and the Bindplane listen_address to match.
- Log Format: Select JSONfrom the dropdown.
- Transfer Interval: Select Continuousfrom the dropdown.
- Field Delimiter: Select SPACEfrom the dropdown.
- Send DLP/Web/DNS/Malware/Audit/ConnectionError Logs: Set to Enablebased on your preference for sending logs.
  
  Note: The Send Connection Error Logstoggle is only visible in the iBoss UI when Send Web Logsis disabled.
- Fields to Forward: Add all fields except DLP Base64 Encoded Meta Data, Base64 Encoded Meta Data, and Chat GPT Message.
Click Add Service.

UDM mapping table

Log field	UDM mapping	Logic
intermediary	intermediary	Information about an intermediary device or service involved in the event.
desc	metadata.description	Additional description of the event.
metadata.event_type	metadata.event_type	Type of event (e.g., USER_LOGIN, NETWORK_CONNECTION).
urlLogId	metadata.product_log_id	Unique identifier for the log entry from the product.
requestMethod	network.http.method	HTTP method used in the request.
ref_url	network.http.referral_url	URL that referred the user to the current page.
response_Code	network.http.response_code	HTTP response code.
user_Agent	network.http.user_agent	User agent string from the HTTP request.
up_stream	network.received_bytes	Number of bytes received in the network connection.
down_stream	network.sent_bytes	Number of bytes sent in the network connection.
computerName	principal.asset.hostname	Hostname of the asset associated with the principal.
computer_Mac_Address	principal.asset.mac	MAC address of the asset associated with the principal.
filtering_Group_Name	principal.group.group_display_name	Display name of the group associated with the principal.
computerName	principal.hostname	Hostname of the principal.
sourceIpAddress	principal.ip	IP address of the principal.
pri_ip	principal.ip
pub_ip	principal.ip
mac_address	principal.mac	MAC address of the principal.
src_port	principal.port	Port number used by the principal.
file_name	principal.process.file.names	Names of files associated with the process.
username	principal.user.userid	User ID of the principal.
sec_res	security_result	Result of security analysis, including actions and categories.
host	target.hostname	Hostname of the target.
ipAddress	target.ip	IP address of the target.
targetPort	target.port	Port number of the target.
uri_path	target.process.file.full_path	Full path of the file or resource on the target.
url	target.url	URL of the target.
metadata.product_name	metadata.product_name	Name of the product that generated the event.
metadata.vendor_name	metadata.vendor_name	Name of the vendor that produced the product.

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