Arctera Insight Information Governance Administrator's Guide

Complete the following steps to enable SSL support for Cluster Mode NetApp auditing in Information Governance:

1. Create SSL Certificate for each Information Governance FPolicy Server (Information Governance Collector Node) that will receive events from a NetApp SVM

   Any suitable tool or PKI solution can be used to generate certificates. Example instructions for using the OpenSSL Toolkit are given below. OpenSSL binaries can be downloaded for use on Microsoft Windows or installed on Linux servers. For more details, visit https://www.openssl.org/community/binaries.html

   Create a self-signed certificate for each Information Governance server that will receive FPolicy events from NetApp SVMs. Make a note of the Information Governance Collector Node names that you need to create certificates for. This is normally the Fully Qualified Domain Name (FQDN) of the node but can also be the NetBIOS Hostname if a FQDN is not in use. For example, the FQDN could be something like "DI_collector_1.acme.com".

   Run the following OpenSSL command which will ask you to enter the certificate Subject Name fields and then create two files to be used in steps 2 and 3:

   >> openssl req -x509 -newkey rsa:4096 -sha256 -nodes -days 1000 -outform PEM -keyout <server name>.key 
   -out <server name>.pem

   For example: openssl req -x509 -newkey rsa:4096 -sha256 -nodes -days 1000 -outform PEM -keyout DI_collector_1.acme.com.key -out DI_collector_1.acme.com.pem

   Note the following points:

   • The certificates are valid for 1,000 days but can be changed to fit your certificate expiry policy - simply change the '-days 1000' parameter to increase or decrease the number of days.

   • Entering values for the Subject Name when prompted by the OpenSSL tool:

     The values you enter here do not affect how data is encrypted, but you may have internal policies which say that certificates should have valid Subject Names. Here is an example where the common name is the same as the server name for which the certificate will be used.

     Country Name (2 letter code) [AU]: US

     State or Province Name (full name) [Some-State]: California

     Locality Name (eg, city) []: Santa Clara

     Organization Name (eg, company) [Internet Widgits Pty Ltd]: Veritas

     Organizational Unit Name (eg, section) []: Engineering

     Common Name (e.g. server FQDN or YOUR name) []: DI_collector_1.acme.com

     Email Address []: someone@veritas.com

2. Install the Certificates on the NetApp SVM(s)

   You need to perform this step on each SVM that will be sending audit events to Information Governance Collectors (FPolicy Servers). A Storage Virtual Machine sends audit events to one Information Governance Collector, so you will install the server certificate you created for that Information Governance Collector node into the SVM that is linked to that Information Governance Collector Node. You do not need to install all the certificates generated in Step 1 in all SVMs.

   For example, if you have the following two Information Governance Collector Nodes:

   • Information Governance Collector node '1' is configured to receive events from NetApp SVM 1

   • Information Governance Collector node '2' is configured to receive events from NetApp SVM 2

   You would install the server certificate generated for collector node 1 into SVM 1 and the certificate for collector node 2 into SVM 2 by completing the follow:

   • SSH to NetApp using cluster management IP/hostname.

   • Identify or choose the data SVM to which you want to configure in Information Governance for SSL audit monitoring. Command to view the SVM is:

     >> vserver show

   • Install the certificate of the Information Governance Collector Node that this SVM will send audit events to. You will need the contents of the <server>.pem file created in step 1. Use the following command to install certificate on your data SVM:

     >> security certificate install -type client-ca -vserver <data SVM name>

   • You will be prompted to paste the certificate. Ensure you paste the entire contents of the <server>.pem file including the "-----BEGIN CERTIFICATE-----" and "-----END CERTIFICATE-----" without any spaces or newlines after "-----END CERTIFICATE-----".

   • Verify that the certificate has been installed by showing the list of certificates:

     >> security certificate show -vserver <data SVM name>

   Note:

   You do not need to configure the FPolicy's external-engine on SVMs manually - this is done automatically by Information Governance when you configure or reconfigure the FPolicy Service (see the last step below).

3. Enable SSL support for Cluster Mode NetApp in Information Governance collector node

   Perform the following steps on each Information Governance Collector Node that will receive FPolicy events from a NetApp SVM

   Copy the Information Governance FPolicy Server's certificate files ('<server>.pem' and '<server>.key') to the Information Governance Collector Node. For example, you would copy the certificates generated for Information Governance Collector Node '1' to Information Governance Collector Node '1' and not Information Governance Collector Node '2'.

   We recommend that they are copied to the Information Governance data directory (e.g. 'C:\DataInsight\data') and that you use the same folder on each node for consistency. But the certificate can be placed in any folder on the collector node. In the next step, you will tell Information Governance which folder they are in, so make a note of it.

4. Configure the Information Governance FPolicy Server to support SSL Communication with NetApp SVMs

   Perform the following steps only on the Information Governance Management Server. Make sure that you have the ID of each Information Governance collector node and ID of each monitored Cluster Mode NetApp's SVM/filer that you need to configure. The collector node ID and SVM/filer ID are numbers that you can be find in the Information Governance Management Portal UI. To find the IDs:

   For collector node id:

   • Navigate to Settings

   • Click Information Governance Servers under Inventory

   • Click top bar and click down arrow

   • Select columns and check box next to the ID field.

   • Note down the collector IDs for which you want to configure Cluster Mode NetApp's SSL auditing

   For SVM/filer id:

   • Navigate to Settings

   • Click Filers under Inventory

   • Click top bar and click down arrow

   • Select columns and check box next to the ID field.

   • Note down the monitored SVM/filer IDs for which you want to configure Cluster Mode NetApp's SSL auditing.

   Now, add some new configuration properties to the Information Governance Configuration database. The properties will control the behavior of the FPolicy Service which are:

   - fpolicydcmod.ssl

   Node level obj attribute. Integer value - set to 1 to enable SSL auditing support for Cluster Mode NetApp.

   - fpolicydcmod.ssl.srv.cert

   Node level obj attribute. String value - the absolute file path for the FPolicy server's PEM certificate file ('<server>.pem file') The certificate must be in PEM format, the one generated in step 1, above. File extension must be ".pem".

   - fpolicydcmod.ssl.srv.cert.key

   Node level obj attribute. String value, absolute file path for the SSL server certificate's key file ('<server>.key'). - vserver.sec.adt.conn Device/filer level obj attribute. Integer value, default value is 0, 1 to configure secure auditing communication at filer/device/vserver level. This obj attribute need to be configured for every SVM device/filer for which you need SSL auditing support.

   Optional properties:

   - fpolicydcmod.ssl.port (optional)

   Optional attribute. Node level obj attribute. Integer value. Port number for SSL server, default value is 20249 from backend side. Value can be a valid port number for FPolicy SSL/secured Server.

   - fpolicydcmod.ssl.ciphers (optional)

   Optional attribute. Node level obj attribute. String value. Default value is "ECDHE". Value can be a valid preferred ciphers string.

   • On the Information Governance Management Server open a command-line prompt and change to the '<DI install directory>\bin' folder. Run the following commands to add the new configuration properties. You will need to substitute the Information Governance Collector Node ID or Device id for monitored SVM in the --obj-id property and the path to the certificates from each collector node.

     >> configdb.exe --add-obj-attribute --type "node" 
     --obj-id <DI collector node id> --attr-name "fpolicydcmod.ssl" 
     --attr-value 1
     e.g. >> configdb.exe --add-obj-attribute --type "node" --obj-id 1 
     --attr-name "fpolicydcmod.ssl" --attr-value 1
                        
     >> configdb.exe --add-obj-attribute --type "node" 
     --obj-id <DI collector node id> --attr-name "fpolicydcmod.ssl.srv.cert" 
     --attr-value "<Server certificate file path>"                
     e.g. >> configdb.exe --add-obj-attribute --type "node" --obj-id 1 
     --attr-name "fpolicydcmod.ssl.srv.cert" --attr-value 
     "C:\DataInsight\data\DI_collector_1.acme.com.pem"
                         
     >> configdb.exe --add-obj-attribute --type "node" --obj-id 
     <DI collector node id> --attr-name "fpolicydcmod.ssl.srv.cert.key" 
     --attr-value "<Server certificate key file path>"
     e.g. >> configdb.exe --add-obj-attribute --type "node" 
     --obj-id 1 --attr-name "fpolicydcmod.ssl.srv.cert.key" 
     --attr-value "C:\DataInsight\data\DI_collector_1.acme.com.key"
     
     >> configdb.exe --add-obj-attribute --type "filer" --obj-id 
     <Device id for monitored SVM> --attr-name "vserver.sec.adt.conn" 
     --attr-value 1
     e.g. >> configdb.exe --add-obj-attribute --type "filer" --obj-id 2 
     --attr-name "vserver.sec.adt.conn" --attr-value 1
     - Note: Repeat this command for every configured SVM device/filer for 
     which you need to enable SSL auditing support.
     
     -> optional commands:
     >> configdb.exe --add-obj-attribute --type "node" --obj-id 
     <DI collector node id> --attr-name "fpolicydcmod.ssl.port" 
     --attr-value <Valid port number>
     e.g. >> configdb.exe --add-obj-attribute --type "node" 
     --obj-id 1 --attr-name "fpolicydcmod.ssl.port" --attr-value 8788
     
     >> configdb.exe --add-obj-attribute --type "node" 
     --obj-id <DI collector node id> --attr-name "fpolicydcmod.ssl.ciphers" 
     --attr-value "<Valid preferred ciphers string>"
     e.g. >> configdb.exe --add-obj-attribute --type "node" 
     --obj-id 1 --attr-name "fpolicydcmod.ssl.ciphers" 
     --attr-value "ECDHE"

5. Restart the Information Governance FPolicy services and validate events are received

   In the last step, you will reconfigure the Information Governance FPolicy Service which will then be able to receive events from the NetApp SVMs over SSL/TLS.

   • Login to the Information Governance Management Server Portal UI

   • Configure/start "DataInsightFPolicyCMod" service from the collector node's services page

     Note:

     This step is necessary to automatically configure the monitored NetApp SVM external-engine configuration to use 'server-auth' (SSL/TLS).

   This step is necessary to automatically configure the monitored NetApp SVM external-engine configuration to use 'server-auth' (SSL/TLS).

   You can now perform audit events in the monitored shares and validate that events are processed by Information Governance. You can do that by multiple ways like

   • wait for at least 2 minutes OR restart the 'DataInsightFPolicyCMod' service from Windows services panel on Information Governance collector node machine. You can also check for the presence of temporary audit output files on the Information Governance Collector Node folder '<DI data dir>\collector'. For cluster mode NetApp the filenames start with "fpolicy_".

   • Wait for the default scheduled Jobs to execute which will ingest the audit events. You can also manually run the Information Governance ingest jobs in the following sequence which will speed up the process:

     CollectorJob - Run on Collector Node on which the monitored share is configured.

     FileTransferJob - Run on Collector Node on which the monitored share is configured.

     IndexWriterJob - Run on Indexer Node on which the monitored share is configured.

     Jobs can be found and run from:

     Settings -> Information Governance Servers >> select the Collector node from list >> Jobs >> Select the required Job >> Select action >> Run

   Once the jobs are successful, you can view audit events in Information Governance Workspace by going to Workspace >> Data Sources >> select and expand filer >> select share name >> Expand Profile >> Audit logs >> configure different filter values and clicking GO.