Collect Nasuni File Data Services logs

Supported in:

This document explains how you can ingest Nasuni File Data Services logs to Google Security Operations using Bindplane. Nasuni File Data Services is a cloud-native file data platform that replaces traditional file storage infrastructure with a scalable, cloud-based solution. It provides file access, file sharing, protection, and global file locking capabilities across edge locations. Nasuni generates audit logs for file operations, access events, and administrative actions that can be forwarded via syslog for security monitoring.

Before you begin

Make sure you have the following prerequisites:

  • A Google SecOps instance.
  • A Windows 2016 or later or Linux host with systemd.
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements.
  • Privileged access to the Nasuni Management Console (NMC) with administrative privileges.
  • Nasuni Edge Appliance firmware version 9.0 or later.

Get Google SecOps ingestion authentication file

  1. Sign in to the Google SecOps console.
  2. Go to SIEM Settings > Collection Agent.
  3. Download the Ingestion Authentication File.
    • Save the file securely on the system where Bindplane 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 the 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" /quiet

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)" install_unix.sh

Additional installation resources

For additional installation options, consult this installation guide.

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

  1. Access the Configuration File:

    • Locate the config.yaml file. Typically, it's in the /observiq-otel-collector/ directory on Linux or in the installation directory on Windows.
    • Open the file using a text editor (for example, nano, vi, or Notepad).

  2. Edit the config.yaml file as follows:

    receivers:
    tcplog:
        # Replace the port and IP address as required
        listen_address: "0.0.0.0:514"

exporters:
    chronicle/chronicle_w_labels:
        compression: gzip
        # Adjust the path to the credentials file you downloaded in Step 1
        creds_file_path: '/path/to/ingestion-authentication-file.json'
        # Replace with your actual customer ID from Step 2
        customer_id: <PLACEHOLDER_CUSTOMER_ID>
        endpoint: malachiteingestion-pa.googleapis.com
        # Add optional ingestion labels for better organization
        log_type: 'NASUNI_FILE_SERVICES'
        raw_log_field: body
        ingestion_labels:

service:
    pipelines:
        logs/source0__chronicle_w_labels-0:
            receivers:
                - tcplog
            exporters:
                - chronicle/chronicle_w_labels
  • Replace the port and IP address as required in your infrastructure.
  • Replace <PLACEHOLDER_CUSTOMER_ID> with the actual Customer ID.
  • Update /path/to/ingestion-authentication-file.json to the file path where the authentication file was saved in the Get Google SecOps ingestion authentication file section.

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 Nasuni syslog forwarding

Configure syslog on the Nasuni Edge Appliance

  1. Sign in to the Nasuni Management Console (NMC).
  2. Go to Filers > Filer Settings.
  3. Select the Nasuni Edge Appliance that you want to configure.
  4. Go to the Syslog section.
  5. Click Add Syslog Server.
  6. Provide the following configuration details:
    • Server Address: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100).
    • Port: Enter 514 (or the port configured in Bindplane).
    • Protocol: Select TCP.
    • Format: Select Syslog (RFC 5424) if available, or Syslog (RFC 3164).

  7. In the Log Categories section, enable the following log types:

    • Audit Logs: File access, create, delete, and rename operations.
    • Authentication Logs: User authentication events.
    • System Logs: Appliance health, sync, and administrative events.
    • Snapshot Logs: Snapshot creation and deletion events.

  8. Click Save to apply the syslog configuration.

Repeat for additional Edge Appliances

  1. If you have multiple Nasuni Edge Appliances, repeat the syslog configuration for each appliance.
  2. In the NMC, go to Filers > All Filers to see a list of all managed appliances.
  3. Configure each appliance to forward logs to the same Bindplane agent host and port.

Verify syslog forwarding

  1. On the Bindplane agent host, verify that logs are being received by checking the agent logs:

    sudo journalctl -u observiq-otel-collector -f

  2. In the NMC, go to Filers > Filer Settings > Syslog for the configured appliance.

  3. Verify the syslog server status shows Connected or Active.

For additional details, refer to the Nasuni documentation on syslog configuration.

UDM mapping table

Log Field UDM Mapping Logic
additional_label additional.fields Merged
is_dir_label additional.fields Merged
offset_label additional.fields Merged
sequence_label additional.fields Merged
uid_label additional.fields Merged
volume_label additional.fields Merged
msg metadata.description Directly mapped
proto metadata.description Directly mapped
event_timestamp metadata.event_timestamp Parsed as ISO8601
when metadata.event_timestamp Parsed as yyyy-MM-dd HH:mm:ss
event_type metadata.event_type Mapped: "AUDIT_READDIR", "AUDIT_READ","Read" → FILE_READ, "AUDIT_WRITE","Write" → `FIL...
has_principal metadata.event_type Mapped: true → FILE_READ, true → FILE_MODIFICATION, true → FILE_UNCATEGORIZED, `...
event_type metadata.product_event_type Directly mapped
product_log_id metadata.product_log_id Directly mapped
host principal.asset.hostname Directly mapped
ipaddr principal.asset.ip Merged
host principal.hostname Directly mapped
ipaddr principal.ip Merged
prin_port principal.port Directly mapped
proc_id principal.process.pid Directly mapped
username principal.user.user_display_name Directly mapped
sid principal.user.windows_sid Directly mapped
action security_result.action_details Directly mapped
application target.application Directly mapped
path target.file.full_path Directly mapped
groupname target.group.group_display_name Directly mapped
gid target.group.product_object_id Directly mapped
pid target.process.pid Directly mapped
tid target.resource.product_object_id Directly mapped
resource target.resource.resource_subtype Directly mapped
grp target.user.group_identifiers Merged
N/A metadata.event_type Constant: FILE_READ
N/A metadata.product_name Constant: Nasuni File Services Platform
N/A metadata.vendor_name Constant: Nasuni

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