Collect NetApp ONTAP SAN logs

Supported in:

This document explains how to ingest NetApp ONTAP SAN logs to Google Security Operations using Bindplane. NetApp ONTAP is a data management software platform for storage systems that provides SAN (Storage Area Network) services including block-level storage using iSCSI, Fibre Channel, and NVMe over Fabrics protocols. ONTAP SAN logs capture events related to LUN operations, initiator group management, port status changes, and storage access activities.

For more information, see Collect NetApp SAN logs.

Before you begin

Make sure you have the following prerequisites:

  • A Google SecOps instance.
  • A Windows 2016 or later or Linux host with systemd.
  • Network connectivity: If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements.
  • Privileged access to the NetApp ONTAP cluster management interface (ONTAP System Manager or CLI).
  • ONTAP 9.x or later running on the storage system.

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.
  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 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](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](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 is in the /opt/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:
  udplog:
    listen_address: "0.0.0.0:514"

exporters:
  chronicle/netapp_san:
    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: '/path/to/ingestion-authentication-file.json'
    customer_id: '<CUSTOMER_ID>'
    endpoint: chronicle.googleapis.com
    log_type: NETAPP_SAN
    raw_log_field: body
    ingestion_labels:

service:
  pipelines:
    logs/netapp_san_to_chronicle:
      receivers:
        - udplog
      exporters:
        - chronicle/netapp_san
  • Replace the port and IP address as required in your infrastructure.
  • 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.
  • Replace <PROJECT_NUMBER> with the project number from IAM & Admin > Settings.
  • Replace <CUSTOMER_ID> with the actual customer ID.
  • Update /path/to/ingestion-authentication-file.json to the path where the service account key file (Option 1) was saved.

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/netapp_san:
    compression: gzip
    creds_file_path: '/path/to/ingestion-authentication-file.json'
    customer_id: '<CUSTOMER_ID>'
    endpoint: malachiteingestion-pa.googleapis.com
    log_type: NETAPP_SAN
    raw_log_field: body
    ingestion_labels:

Restart the Bindplane agent to apply the changes

  1. To restart the Bindplane agent in Linux, run the following command:

    sudo systemctl restart observiq-otel-collector

  2. To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:

    net stop observiq-otel-collector && net start observiq-otel-collector

Configure syslog forwarding on NetApp ONTAP

Configure syslog using ONTAP CLI

  1. Connect to the NetApp ONTAP cluster management LIF using SSH.

  2. Enter the following command to view the current event notification destinations:

    cluster1::> event notification destination show

  3. Create a syslog notification destination pointing to the Bindplane agent:

    cluster1::> event notification destination create -name bindplane-syslog -syslog <BINDPLANE_IP_ADDRESS> -syslog-port 514 -syslog-transport udp-unencrypted
    • Replace <BINDPLANE_IP_ADDRESS> with the IP address of the Bindplane agent host.

  4. Create an event notification to forward EMS events to the syslog destination:

    cluster1::> event notification create -filter-name default-trap-events -destinations bindplane-syslog

  5. (Optional) Create a custom filter to include all events:

    cluster1::> event filter create -filter-name all-events
cluster1::> event filter rule add -filter-name all-events -type include -message-name * -severity <=NOTICE
cluster1::> event notification create -filter-name all-events -destinations bindplane-syslog

  6. Verify the configuration:

    cluster1::> event notification destination show
cluster1::> event notification show

Configure syslog using ONTAP System Manager

  1. Sign in to ONTAP System Manager.
  2. Go to Events & Jobs > Events > EMS Event Notifications.
  3. Click Add to create a notification destination.
  4. Provide the following configuration details:
    • Name: Enter bindplane-syslog.
    • Type: Select Syslog.
    • Syslog Server: Enter the IP address of the Bindplane agent host.
    • Port: Enter 514.
    • Transport Protocol: Select UDP.
  5. Click Save.
  6. Create an event notification rule and associate it with the bindplane-syslog destination.
  7. Select the event filter (for example, default-trap-events or a custom filter).
  8. Click Save.

For more information, see NetApp ONTAP EMS configuration documentation.

UDM mapping table

Log Field UDM Mapping Logic
desc metadata.description Directly mapped
datetime metadata.event_timestamp Parsed as MMM d HH:mm:ss
ip principal.ip Merged
port principal.port Directly mapped
userid principal.user.userid Directly mapped
sr security_result Merged
N/A metadata.event_type Constant: STATUS_UPDATE
N/A metadata.product_name Constant: Storage Area Network
N/A metadata.vendor_name Constant: NetApp

Change Log

View the Change Log for this parser

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