Upgrade a distributed OEL installation of Splunk UBA

Perform the following steps to upgrade a distributed OEL installation of Splunk UBA.

OEL Leapp regularly updates its base operating system to the latest version of OEL 8.x. If you are a Splunk UBA customer using OEL, refrain from upgrading OEL until you verify the OEL version Leapp will upgrade your environment to is supported by the target UBA version. For information on the latest OEL version, see https://docs.oracle.com/en/operating-systems/oracle-linux/8 /.

Before you begin

Make sure the correct hadoop ports are open. See, Inbound networking port requirements.

Before upgrading Splunk UBA in a distributed deployment, confirm you meet the Upgrade Splunk UBA prerequisites. Make sure that the prerequisites are verified on each server in the distributed deployment.

If you have enabled the integration that sends UBA audit data to Splunk Enterprise Security (ES), preserve the associated certificate before upgrading. For more info on sending audit data to ES see, Send Splunk UBA audit events to Splunk ES. Use the following command to export the certificate:

. /opt/caspida/bin/CaspidaCommonEnv.sh
sudo keytool -exportcert -alias "splunk es" -keystore $JAVA_HOME/lib/security/cacerts -rfc -file ~/splunk-es_cacert.pem

If you have enabled validation of the SSL certificate from Splunk ES, export the SSL certificate used for validating datasources from the Splunk Enterprise platform:

. /opt/caspida/bin/CaspidaCommonEnv.sh
sudo keytool -exportcert -alias "SplunkESRootCA" -keystore $JAVA_HOME/lib/security/cacerts -rfc -file ~/SplunkESRootCA.pem

Stop all UBA services and archive

Switch to the caspida user and perform the following steps to archive the older version of Splunk UBA:

1. On the management node only, stop all the caspida services:

   /opt/caspida/bin/Caspida stop-all

2. On each node, archive the older version of UBA. REPLACE <old-uba-version> with your UBA version:

   sudo mkdir -p /var/vcap/release_archives
   sudo mv /opt/caspida /var/vcap/release_archives/caspida-<old-uba-version>	
   sudo mkdir -p /opt/caspida && sudo chown caspida:caspida /opt/caspida
   sudo chown caspida:caspida /var/vcap/release_archives
   sudo chown caspida:caspida /var/vcap/release_archives/caspida-<old-uba-version>

Perform UBA upgrade

Perform the following tasks to upgrade Splunk UBA in a distributed environment.

1. Switch to caspida user and perform the following steps to archive the older version of UBA.
1. On the management node, download the latest UBA branch build splunk-uba-software-upgrade-package_521.tgz and untar the UBA bits to /home/caspida directory:

   $ tar xvzf /home/caspida/splunk-uba-software-upgrade-package_521.tgz
   Splunk-UBA-Platform-5.2.1-20231013-12401747.tgz
   Splunk-UBA-Platform-5.2.1-20231013-12401747.tgz.md5sum
   uba-ext-pkgs-5.2.1.tgz
   uba-ext-pkgs-5.2.1.tgz.md5sum

2. Untar the UBA 5.2.1 Platform build inside the /opt/caspida/ folder:

   tar xvzf /home/caspida/Splunk-UBA-Platform-5.2.1-20231013-12401747.tgz -C /opt/caspida




2. Run the UBA upgrade script, using the path to your archived UBA from the Stop all UBA services and archive step.

   The path-to-prev-uba-archive might be /var/vcap/release_archives/caspida- depending on your archived UBA version number.

   /opt/caspida/upgrade/utils/upgrade_uba.sh -p 
   /var/vcap/release_archives/caspida-<old-uba-version> -e 
   /home/caspida/uba-ext-pkgs-5.2.1.tgz

   The command installs the new Splunk UBA software, restarts Splunk UBA, and then restarts the data sources.

If you have previously imported an output connector certificate, re-import the certificate. See, Configure the Splunk platform to receive data from the Splunk UBA output connector in the Send and Receive Data from the Splunk Platform manual.

Re-import the certificate used for sending UBA audit events to Splunk ES

If you have enabled the integration that sends UBA audit data to Splunk Enterprise Security (ES), and you preserved the associated certificate in the Before you begin step, you can now re-import that certificate. Use the following command to re-import the certificate:

. /opt/caspida/bin/CaspidaCommonEnv.sh
sudo keytool -import -alias "splunk es" -keystore $JAVA_HOME/lib/security/cacerts -file ~/splunk-es_cacert.pem

Re-import the SSL certificate used for validating datasources from the Splunk Enterprise platform

If you have enabled the integration that sends UBA audit data to Splunk Enterprise Security (ES), use the following command to re-import the SSL certificate:

. /opt/caspida/bin/CaspidaCommonEnv.sh
sudo keytool -import -alias "SplunkESRootCA" -keystore $JAVA_HOME/lib/security/cacerts -file ~/SplunkESRootCA.pem

For more information on SSL certificate validation, see Configure flag to enable or disable Splunk SSL certificate validation.

Apply security patches on your Linux operating system

Perform the following tasks to apply the latest Linux operating system security patches:

1. Log in to the Splunk UBA server as the caspida user.
2. Run the following command to stop Splunk UBA and all services:

   /opt/caspida/bin/Caspida stop-all

3. Run the following commands to check for any available security updates:

   sudo yum updateinfo list security all
   sudo yum updateinfo list sec
   

4. Run the following command to resolve glibc package dependencies:

   sudo yum update glibc-devel

5. Run the following command to update all packages with the available security updates:

   sudo yum update --security -y
   sudo yum --security update-minimal
   

6. Reboot the system:

   sudo reboot

7. Run the following command to start Splunk UBA and all services:

   /opt/caspida/bin/Caspida start-all

Next steps

Verify a successful upgrade of Splunk UBA.