Collect Trellix Network Security Audit (formerly FireEye NX Audit) logs

Parser Version: 1.0

This document explains how to ingest Trellix Network Security Audit (formerly known as FireEye NX Audit) logs to Google Security Operations using Bindplane.

Trellix Network Security is a network security appliance that detects and blocks attacks from the web, protecting against drive-by malware and highly targeted zero-day exploits. It leverages the Multi-Vector Virtual Execution (MVX) engine to identify malicious activity and command-and-control callbacks with extremely low false positive rates.

Before you begin

Make sure you have the following prerequisites:

• A Google SecOps instance.
• A Windows Server 2016 or later, or a Linux host with systemd.
• Network connectivity between the Bindplane agent and the FireEye NX Audit appliance.
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements.
• Privileged access to the FireEye NX Audit management console or appliance.

Get Google SecOps credentials for the Bindplane agent

To authenticate the Bindplane agent to Google SecOps, choose one of the following methods:

• New deployments: Use the Chronicle API (Option 1).
• Legacy deployments: Continue using the ingestion authentication file (Option 2) until the Ingestion API is discontinued on July 20, 2027.

Option 1: Create a service account for the Chronicle API (recommended)

1. Sign in to the Google Cloud console and select the Google Cloud project that is linked to your Google SecOps instance.
2. Go to IAM & Admin > Service Accounts.
3. Click Create service account.
4. Provide the following configuration details:
   • Service account name: Enter a name for the account (for example, bindplane-ingest).
   • Service account description: Enter a description (for example, Bindplane agent log ingestion).
5. Click Create and continue.
6. In the Grant this service account access to project section, click Select a role and select Chronicle Editor.
7. Click Continue, and then click Done.
8. Click the service account you created, and then go to the Keys tab.
9. Click Add key > Create new key.
10. Select JSON and click Create. The key file is downloaded to your computer.
11. Save the key file as ingestion-auth.json in the Bindplane collector directory (/opt/observiq-otel-collector/ingestion-auth.json on Linux or C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json on Windows), or update creds_file_path in config.yaml to match the path where you save it.
12. Go to IAM & Admin > Settings and copy the Project number. You'll need it for the exporter configuration.

Option 2: Download the ingestion authentication file (legacy)

1. Sign in to the Google SecOps console.
2. Go to SIEM Settings > Collection Agents.
3. Download the ingestion authentication file.
4. Save the file securely on the system where the Bindplane agent 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

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

Windows installation

1. Open 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](https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi)" /quiet
   

3. Wait for the installation to complete.

4. Verify the installation by running:

   sc query observiq-otel-collector
   

The service should show as RUNNING.

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](https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh))" install_unix.sh
   

3. Wait for the installation to complete.

4. 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 the Bindplane agent installation guide.

Configure the Bindplane agent to ingest syslog and send to Google SecOps

Locate the configuration file

• Linux: /opt/observiq-otel-collector/config.yaml
• Windows: 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/fireeye_nx:
      protocol: https
      # Region of your instance, for example us, europe, asia-southeast1
      location: <LOCATION>
      # Project number of the Google Cloud project linked to the instance
      project: '<PROJECT_NUMBER>'
      compression: gzip
      creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
      customer_id: 'YOUR_CUSTOMER_ID'
      endpoint: chronicle.googleapis.com
      log_type: FIREEYE_NX_AUDIT
      raw_log_field: body
      ingestion_labels:
        env: production
        source: trellix_nx
  
  service:
    pipelines:
      logs/fireeye_nx_to_chronicle:
        receivers:
          - udplog
        exporters:
          - chronicle/fireeye_nx
  

Configuration parameters

Replace the following placeholders:

• Receiver configuration:

  • listen_address: IP address and port to listen on. * 0.0.0.0:514 (requires root/admin privileges). * 0.0.0.0:1514 for unprivileged port (recommended for Linux non-root).

• Exporter configuration:

  • creds_file_path: Full path to the service account JSON key file (Option 1).
  • customer_id: Your Google SecOps customer ID.
  • location: Replace <LOCATION> with the region of your Google SecOps instance (for example, us, europe, or asia-southeast1). The exporter prefixes chronicle.googleapis.com with this value. See Regional Endpoints for the complete list.
  • project: Replace <PROJECT_NUMBER> with the project number from IAM & Admin > Settings.
  • endpoint: Keep set to chronicle.googleapis.com.
  • log_type: Set to FIREEYE_NX_AUDIT.
  • ingestion_labels: Optional labels for categorizing logs.

Legacy ingestion API exporter

• If you use the ingestion authentication file from Option 2, replace the exporters block with the following. Set creds_file_path to the path to the ingestion authentication file, and if your instance is outside the US, replace malachiteingestion-pa.googleapis.com with your regional endpoint (for example, europe-malachiteingestion-pa.googleapis.com).

  exporters:
    chronicle/fireeye_nx:
      compression: gzip
      creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
      customer_id: 'YOUR_CUSTOMER_ID'
      endpoint: malachiteingestion-pa.googleapis.com
      log_type: FIREEYE_NX_AUDIT
      raw_log_field: body
      ingestion_labels:
        env: production
        source: trellix_nx
  

Save the configuration 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:

1. Run the following command:

   sudo systemctl restart observiq-otel-collector
   

2. Verify the service is running:

   sudo systemctl status observiq-otel-collector
   

3. Check logs for errors:

   sudo journalctl -u observiq-otel-collector -f
   

To restart the Bindplane agent in Windows:

1. 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.

2. Verify the service is running:

   sc query observiq-otel-collector
   

3. Check logs for errors:

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

Configure FireEye NX Audit syslog forwarding

1. Sign in to the FireEye NX Audit console.
2. Go to Settings > Notifications.
3. Click the rsyslog tab.
4. Select the Event type checkbox.

5. In the Settings panel, select CEF (Common Event Format) as the Default format.

6. In the Rsyslog Server Listing section:

   1. Add a new server (e.g., Google SecOps Bindplane).
   2. IP Address: Enter the IP address of the Bindplane agent host.
   3. Port: Enter the Bindplane agent port number (e.g., 514).
   4. Protocol: Select UDP or TCP based on your Bindplane receiver configuration.
   5. Delivery: Select Per Event.
   6. Notifications: Select All Events.

7. Click Update to save.

UDM mapping table

Log field	UDM mapping	Logic
alert.dst.ip	target.ip	Direct mapping.
alert.dst.port	target.port	Direct mapping.
alert.src.ip	principal.ip	Direct mapping.
alert.occurred	metadata.event_timestamp	Direct mapping.
alert.name	metadata.product_event_type	Direct mapping.
security_result.action	security_result.action	ALLOW if "notified", BLOCK if "blocked".
metadata.log_type	metadata.log_type	Set to FIREEYE_NX_AUDIT.
metadata.vendor_name	metadata.vendor_name	Set to FireEye.

Change Log

View the Change Log for this parser

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