Upgrade a single node RHEL installation of Splunk UBA
Perform the following steps to upgrade a single node RHEL installation of Splunk UBA.
Before you begin
Make sure the correct hadoop ports are open. See, Inbound networking port requirements.
Before upgrading Splunk UBA on a single server, confirm you meet the Upgrade Splunk UBA prerequisites
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
Download the Splunk UBA upgrade software
Perform the following steps to find and download the Splunk UBA upgrade software:
- Obtain the Splunk UBA Software Update and download the file to the
/home/caspida
directory. Select version 5.2.1 from the drop-down list. The downloadable archive file is namedtar xfz /home/caspida/splunk-uba-software-upgrade-package_521.tgz -C /home/caspida
. - Extract the archive with the following command:
tar xfz /home/caspida/splunk-uba-software-upgrade-package_521.tgz -C /home/caspida
The following files are extracted:
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
Stop all UBA services and archive
Switch to caspida user and perform the following steps to archive the older version of UBA.
- On the management node, stop all the caspida services:
/opt/caspida/bin/Caspida stop-all
- 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 on a single server as the caspida user.
- Untar the UBA 5.2.1 Platform build inside the /opt/caspida/ folder:
tar xvzf Splunk-UBA-Platform-5.2.1-20231013-12401747.tgz -C /opt/caspida
- 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:
- Log in to the Splunk UBA server as the caspida user.
- Run the following command to stop Splunk UBA and all services:
/opt/caspida/bin/Caspida stop-all
- Run the following commands to check for any available security updates:
sudo yum updateinfo list security all sudo yum updateinfo list sec
- Run the following command to update all packages with the available security updates:
sudo yum update --security -y sudo yum --security update-minimal
- Reboot the system:
sudo reboot
- Run the following command to start Splunk UBA and all services:
/opt/caspida/bin/Caspida start-all
Next steps
Upgrade a single node AMI or OVA installation of Splunk UBA | Upgrade a single node OEL installation of Splunk UBA |
This documentation applies to the following versions of Splunk® User Behavior Analytics: 5.2.1
Feedback submitted, thanks!