NetApp ONTAP FPolicy Add-on for Splunk allows Splunk admins to get File Access Notifications over network port (TCP) as XML Notifications into the Splunk platform for the NetApp ONTAP FPolicy Framework that manages NetApp SVMs.
- Requirements
- Add-on Information
- Setup and Configuration
- File Access Auditing
- FPolicy Framework
- FPolicy Add-on for Splunk
- Overall Topology and Handshake Process
- Authentication Mechanisms
- Integrated Monitoring and Alerting
- Author
- ONTAP FPolicy Framework ready for policy configuration.
- Splunk Enterprise to install the FPolicy Add-on (as an external server).
- Network connection between the end user, ONTAP FPolicy, and Splunk Enterprise.
- Version 0.6.5 (20/10/2023): Initial tests with cloud instance completed.
- Version 0.7.1 (20/12/2023): Logging updates (
splunk/var/log/splunk/server_input.log
). - Version 1.3.3 (28/03/2024): Single SVM node support.
- Version 1.5.6 (11/04/2024): Full cluster support.
- Version 1.7.6 (09/05/2024): Sourcetype selection, support for up to 8 nodes per cluster, resolved intermittent issues.
- Set the external server IP as the device IP (or leave it as
0.0.0.0
); the port number should be any unused port number. - Match the policy name in ONTAP FPolicy for a proper handshake.
-
Download and Install the Add-on:
- Obtain the FPolicy Add-on from Splunkbase or your internal repository.
- Install the Add-on in Splunk Enterprise.
-
Configuration:
- Name: Provide a unique name for the configuration.
- Index: Select or create an appropriate index for storing FPolicy events.
- Account: Use an account with necessary permissions.
- IP: Enter the local instance IP or
0.0.0.0
. - Port: Specify any unused port.
- Policy Name: Ensure it matches the FPolicy configuration for a successful handshake.
Follow the NetApp ONTAP FPolicy guidelines for detailed instructions.
- Create FPolicy Event: Define the events to audit (e.g., create, delete, write) and the protocol (CIFS, NFSv3, NFSv4).
- Create FPolicy External Engine: Provide the IP address and TCP port of the add-on.
- Create FPolicy Policy: Link events with the external engine.
- Create FPolicy Scope: Define the data to audit (e.g., SVM, share, export-policy).
- Enable FPolicy: Activate the policy.
- The node sends supported FPolicy protocol versions to the external server (Splunk).
- Waits for two seconds for a response, and retries as per
max-connection-retries
.
- The external server (Splunk) responds with the selected protocol version.
- The node accepts the first response and discards duplicates.
- If an unsupported protocol version is sent, the node sends an error, alerts the external server, and terminates the connection.
- Verify the external server (Splunk) response.
- Ensure the ONTAP FPolicy node sends a negotiation request.
- Monitor network traffic using tools like Wireshark.
- Confirm successful configuration and handshake on ONTAP FPolicy.
- Ensure the external server (Splunk) receives XML notifications.
Use Wireshark to monitor traffic and run the following commands:
nc <client_ip> <client_port> < response.xml
curl ifconfig.me
nmap -p <port> <ip>
netstat -ant | grep <port>
tcpdump dst port <port>
tcpdump src <ip>
File Access Auditing (FAA) involves monitoring file access via CIFS, NFSv3, or NFSv4.x protocols on NTFS and Unix file systems. It records actions such as creation, modification, deletion, and access of files.
FPolicy is an ONTAP component for real-time monitoring and setting file access permissions, crucial for security and compliance.
The add-on enhances Splunk's capabilities by integrating file event notifications from NetApp, allowing real-time monitoring and analysis of file operations for security and compliance.
A TCP/IP connection is established between each node and the FPolicy Add-on for Splunk. The handshake process ensures secure communication, with the add-on supporting ASYNC Mode and TCP layer acknowledgment.
The handshake is initiated by the policy, requiring admin rights. The policy name in the add-on configuration must match the FPolicy configuration. TCP ensures secure and reliable data transmission, with SSL support for secure data transmission.
Using props.conf
and transforms.conf
, Splunk extracts fields from raw data logs, filters unnecessary parts, and anonymizes certain information. The integration supports automated alerts based on FPolicy events, enhancing security and compliance.
Gurkan Gokdemir (ggokdemir@splunk.com)