Collect Netscout OCI logs

Supported in:

Google secops SIEM

This document explains how to ingest NETSCOUT nGeniusONE logs to Google Security Operations using Bindplane.

NETSCOUT nGeniusONE (Observer Infrastructure) is a network performance monitoring and traffic analysis platform that provides deep packet inspection, real-time visibility into network traffic, and security threat detection. The platform supports forwarding security events and alerts via syslog, including CEF format for SIEM integration.

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 NETSCOUT nGeniusONE server
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the NETSCOUT nGeniusONE management console with administrator permissions

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.

Note: This JSON file contains credentials for authenticating the Bindplane agent to Google SecOps.

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.

Note: The customer ID is required for configuring the Bindplane agent exporter.

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 the Bindplane agent to ingest syslog and send to Google SecOps

Locate the configuration file

Linux:

 sudo  
systemctl  
status  
observiq-otel-collector

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/netscout_oci 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 '/etc/bindplane-agent/ingestion-auth.json' 
  
 customer_id 
 : 
  
 '<customer_id>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 NETSCOUT_OCI 
  
 raw_log_field 
 : 
  
 body 
  
 ingestion_labels 
 : 
  
 env 
 : 
  
 production 
 service 
 : 
  
 pipelines 
 : 
  
 logs/netscout_to_chronicle 
 : 
  
 receivers 
 : 
  
 - 
  
 udplog 
  
 exporters 
 : 
  
 - 
  
 chronicle/netscout_oci

Configuration parameters

Replace the following placeholders:

Receiver configuration:
- udplog : The receiver type based on protocol:
  - udplog for UDP syslog
  - tcplog for TCP syslog
- 0.0.0.0 : IP address to listen on:
  - 0.0.0.0 to listen on all interfaces (recommended)
  - Specific IP address to listen on one interface
- 514 : Port number to listen on (for example, 514 , 1514 , 6514 )
Exporter configuration:
- netscout_oci : Descriptive name for the exporter
- creds_file_path : Full path to ingestion authentication file:
  - Linux: /etc/bindplane-agent/ingestion-auth.json
  - Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
- <customer_id> : Customer ID from the previous step
- 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
- NETSCOUT_OCI : Log type exactly as it appears in Chronicle
- ingestion_labels : Optional labels in YAML format (for example, env: production )
Pipeline configuration:
- netscout_to_chronicle : Descriptive name for the pipeline

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:

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:

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 NETSCOUT nGeniusONE syslog forwarding

Sign in to the nGeniusONEmanagement console with administrator privileges.
Go to Settings > Global Settings > Notification Settings.
In the Syslogsection, configure the following:
- Syslog Server Address: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100 ).
- Syslog Port: Enter 514 (must match the Bindplane agent receiver port).
- Protocol: Select UDP(must match the Bindplane agent receiver type).
Select the event types and severity levels to forward.
Click Saveto apply the configuration.
Verify that syslog messages are being received by checking the Bindplane agent logs.

UDM mapping table

Log Field	UDM Mapping	Logic
Policy,Classification	additional.fields	Additional custom fields
vuln	extensions.vulns.vulnerabilities	List of vulnerabilities
desc	metadata.description	Description of the event
event_type	metadata.event_type	Type of the event
type	metadata.product_event_type	Product-specific event type
device_version	metadata.product_version	Version of the product
dvchost,dvc,shost,src,src_iporhost	principal.asset.hostname	Hostname of the asset associated with the principal
dvchost,dvc,shost,src,src_iporhost	principal.asset.ip	IP address of the asset associated with the principal
dvchost,dvc,shost,src,src_iporhost	principal.hostname	Hostname associated with the principal
dvchost,dvc,shost,src,src_iporhost	principal.ip	IP address associated with the principal
serverPort	principal.port	Port number associated with the principal
event_name,Category	security_result.category_details	Additional details about the category
iocDescription	security_result.description	Description of the security result
OmnisSecurityHostType,HostGroupCount,HostGroup,IOCSeverity,IOCConfidence,OmnisSecurityHostCount,OmnisSecurityInterfaceCount,OmnisSecurityViolationCount,App,UserIdentity,mitreTactic,mitreTechnique,srcCount,dstCount,srcHostGroupCount,dstHostGroupCount,interfaceCount,violationCount,dstHostGroup,srcHostGroup	security_result.detection_fields	Fields used for detection
security_rule_name	security_result.rule_name	Name of the rule that triggered the event
severity	security_result.severity	Severity level of the security result
App	target.application	Application associated with the target
target_host	target.asset.hostname	Hostname of the asset associated with the target
target_ip	target.asset.ip	IP address of the asset associated with the target
dhost,dst,target_host	target.hostname	Hostname associated with the target
dhost,dst,target_ip	target.ip	IP address associated with the target
remoteGeolocation	target.location.name	Name of the location associated with the target
target_port	target.port	Port number associated with the target
OmnisSecurityUrl	target.url	URL associated with the target
end	vuln.scan_end_time	End time of the vulnerability scan
start	vuln.scan_start_time	Start time of the vulnerability scan
	metadata.vendor_name	Name of the vendor
device_product	metadata.product_name	Name of the product

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