Complete the following tasks to prepare for the upgrade to NetWitness Platform 11.3. These tasks are organized by the following categories.
- Event Stream Analysis (ESA)
- Reporting Engine
- Warehouse Connector
Go to the Master Table of Contents to find all NetWitness Platform Logs & Network 11.x documents.
Task 1 - Review Core Ports and Open Firewall Ports
The following tables list new ports in 11.3.
NW Server Host
Endpoint Log Hybrid
All NetWitness Platform core ports are listed in the "Network Architecture and Ports" topic in the Deployment Guide in case you need to reconfigure NetWitness Platform services and firewalls.
Task 2 - Record Your 10.6.6.x admin user Password
Record your 10.6.6.x admin user password. You will need it to complete the upgrade.
Task 3 - Create a Backup of the /etc/fstab File
Copy the /etc/fstab file from all the physical hosts and into your local machine (backup host or remote machine).
Task 4 - Make Sure Password Strength Settings Check Boxes Are Set in 10.6.6.x
The check box to the left of the Password Strength Settings in the Administration > Security > Settings tab must be set in 10.6.6.x or these settings will not be migrated to 11.3.
If you do not require a setting (for example, Non-Latin Alphabetic Characters) in your password for 11.3, you do not need to check this box. The Minimum Password Length is 3 or larger in version 10.6.6.x and 4 in version 11.3. This means that if you set the Minimum Password Length to 3 (default) in 10.6.6.x, you must set it 4 or larger for 11.3.
Complete the following task to make sure that the Password Strength Settings check boxes are set in 10.6.6.x.
- In Security Analytics 10.6.6.x, go to the Administration > Security > Settings tab.
- Check the boxes to the left of the Password Strength Settings that you want to migrate and click Apply.
The following example migrates all the setting except Non-Latin Alphabetic Characters and specifies a Minimum Password Length of 8 characters.
Task 5 (Conditional) - Extract 10.6.x Public Key Infrastructure (PKI) Certificates
Before you upgrade to from 10.6.6.x to 11.3, complete the following procedure to extract the existing 10.6.x PKI keystores that contain server certificates with private keys, and the truststores that contain the trusted CA certificates.
- Download the rsa-nw-pki-migration-10.6.6.zip file from RSA Link > RSA NetWitness Platform > Downloads > RSA NetWitness LOGS & NETWORK > Version 11.3.
- Extract the pki-migration-1.0.jar file from the rsa-nw-pki-migration-10.6.6.zip file.
- SSH to the 10.6.6.x Security Analytics Server host and log in with the root credentials.
- Copy the pki-migration-1.0.jar file into /tmp folder.
- Run the following command strings to extract the certificates.
java -jar pki-migration-1.0.jar
- Creates the rsa-pki-migration-tool-<yyyy-MM-dd-hh-mm> directory under the tmp directory.
- Extracts output files into the /tmp/rsa-pki-migration-<yyyy-MM-dd-hh-mm> directory.
- Creates a keystore (for example, <keystore-x>.p12) for each server certificate.
The keystore is encrypted with netwitness as the password.
- Creates a certificate file (for example, <certificate-X>.cer) for each trusted CA certificate in truststore.
- Open any keystore and display its contents to verify that the extracted keystores and the trusted CA certificates are correct.
Openssl x509 -in <certificate-X>.cer -inform DER
The certificate in displayed in PEM (Base64) format. For example:
keytool -list -keystore <keystore-X>.p12 -storetype PKCS12 – storepass netwitness
The following is an example of the output.
Keystore type: PKCS12
Keystore provider: <XXXXX>
- Exit the keystore.
You can use:
- One of the .p12 keystore files as a server certificate. Refer to the command output to find .p12 file that corresponds to the server certificate you must use.
- The extracted certificate files (.cer) as trusted CA certificates.
For instructions on how to configure PKI authentication, see the “System Security and User Management Guide”.
Task 6 (Conditional) - Record Any String Array Type Meta Keys on the Event Stream Analysis Service
If you added any string array type meta keys to the Event Stream Analysis service for your ESA correlation rules in 10.6.6.x or earlier, record these meta keys so you can verify that they exist after upgrade to 11.3.
To record your 10.6.6.x string array type meta keys before the 11.3 upgrade:
- In Security Analytics 10.6.6.x:
- In the Explore view node list, select Workflow > Source > netgenAggregationSource.
- In the ArrayFieldNames list, make a note of any string array type meta keys added to the Event Stream Analysis service so you can verify that they are on the ESA Correlation service after the upgrade.
Make a note of any Incident Management aggregation rules that have match conditions using Domain or Domain for Suspected C&C in the drop-down list in the rule builder. You will need to add back these conditions after you upgrade to 11.3 as described in the "Respond" Post Upgrade Tasks later in this document.
Complete the task for each aggregation rule.
- In Security Analytics 10.6.6.x, go to Incidents > Configure > Aggregation Rules tab and edit the rules to view the matching conditions.
- In the Match Conditions section, look for Domain or Domain for Suspected C&C listed in the drop-down lists for the conditions.
- Make a note of the rule name and the entire condition that uses Domain or Domain for Suspected C&C, including operators and values.
Task 8 - Set Data Retention Run Interval to ≥ 24 Hours
In Security Analytics 10.6.6.x, the Data Retention run interval does not have any minimum value check. In 11.3, RSA added a validation check to make sure that it is run at least every 24 hours. When you upgrade to 11.3, if this value is less than 24 hours, the Respond service will not start.
Complete the following task to ensure that the Respond service starts after upgrading to 11.3.
- In Security Analytics 10.6.6.x, go to ADMIN > Services.
- Select the Incident Management service, and then select > View > Explore.
In the Incident Management Explore view, go to Service > Configuration > dataRetentionConfiguration.
- Make sure that the FrequencyInHours parameter is ≥ 24.
(Conditional) Task 9 - Unlink External Storage
If the Reporting Engine has external storage, such as Storage Area Network (SAN) or Network Attached Storage (NAS) for storing reports, complete the following task to unlink the storage.
- SSH to the Reporting Engine host and log in with your root credentials.
- Stop the Reporting Engine service.
- Switch to rsasoc user.
- Change to the Reporting Engine the home directory.
- Unlink the resultstore directory mounted to external storage.
- Unlink the formattedReports directory mounted to external storage.
(Conditional) Task 10 - Copy keytab files in root or etc Directory Stored in Other Directory
Complete the following task to copy the keytab files in the root or etc directory if it is stored in another directory.
- Record the absolute path of NFS mount directory and the keytab file.
You need this information to restore the Warehouse Connector after upgrade.
- Unmount the NFS directory.
- SSH to the Warehouse Connector and log in with root credentials.
- Submit the following command to unmount the NFS directory.
Task 11 - Hardware - Check for BAD-INDEX BIOS Error before Upgrading
Complete the following steps to detect a BAD-INDEX BIOS error before you upgrade to 11.3.
- SSH to each host appliance.
- Run the following command.
- If you receive a BAD-INDEX error in the output, contact RSA Customer Support (https://community.rsa.com/docs/DOC-1294).