Secure the default account after installing Splunk UBA

Use the caspida user account to manage and administer your Splunk UBA deployment. Perform the following tasks after installing Splunk UBA:

• Change the default password for this account.
• Limit the sudo access for this account.

Change the default password for the caspida account

Change the default password for the server management account to secure your installation.

The default account username is caspida and the default password is caspida123.

After you install Splunk UBA, change the password of the caspida account with the passwd command.

1. Log in to the Splunk UBA management server as the caspida user.
2. Change the password to a new one.
   passwd

Change the default password to log in to Splunk UBA

Splunk UBA also includes a default admin account that you can use to log in to Splunk UBA. The default username for Splunk UBA is admin and the default password is changeme.

• To change the password of the admin account for Splunk UBA, see Change user profile settings in Splunk UBA.
• To manage accounts and access to Splunk UBA, see Manage user accounts and account roles in Splunk UBA.

Restrict sudo access for the caspida account

By default, the caspida user is given ALL access in /etc/sudoers during Splunk UBA installation and upgrade. Follow the procedures in this section if you want to restrict sudo access for the caspida user after Splunk UBA is installed or upgraded.

Make sure to set the root password before enabling restricted sudo access.

1. Use SSH to login as the caspida user to the management node of Splunk UBA.
2. Stop all services:

   /opt/caspida/bin/Caspida stop-all

3. On the Splunk UBA management node, login as root.
4. Save a copy of /opt/caspida/etc/sudoers.d/ubasudoers:

   cp -p /opt/caspida/etc/sudoers.d/ubasudoers /opt/caspida/etc/sudoers.d/ubasudoers.backup

5. Modify the /opt/caspida/etc/sudoers.d/ubasudoers file by running the following commands:

   sed -i '24i\           /bin/chmod * /etc/cron.monthly/remove_pg_logs, \\' /opt/caspida/etc/sudoers.d/ubasudoers
   sed -i '24i\           /bin/chmod * /etc/cron.monthly/remove_pg_walarchives, \\' /opt/caspida/etc/sudoers.d/ubasudoers
   sed -i '50i\           /bin/cp * /etc/cron.monthly, \\' /opt/caspida/etc/sudoers.d/ubasudoers
   sed -i '120i\           /usr/sbin/service cri-docker *, \\' /opt/caspida/etc/sudoers.d/ubasudoers
   sed -i '130i\           /sbin/service cri-docker *, \\' /opt/caspida/etc/sudoers.d/ubasudoers
   sed -i '135i\           /bin/systemctl start kubelet.service, /usr/bin/systemctl start kubelet.service, \\' /opt/caspida/etc/sudoers.d/ubasudoers
   sed -i '135i\           /bin/systemctl restart kubelet.service, /usr/bin/systemctl restart kubelet.service, \\' /opt/caspida/etc/sudoers.d/ubasudoers
   sed -i '135i\           /bin/systemctl start docker.service, /usr/bin/systemctl start docker.service, \\' /opt/caspida/etc/sudoers.d/ubasudoers
   sed -i '135i\           /bin/systemctl restart docker.service, /usr/bin/systemctl restart docker.service, \\' /opt/caspida/etc/sudoers.d/ubasudoers
   

6. Check to see if a ubasudoers file already exists in /etc/sudoers.d. If there is no existing file, or you want to overwrite the existing file, and don't mind overwriting previous customizations, skip to step 7.
1. If there is an existing ubasudoers file you want to merge, then merge any customizations from the /etc/sudoers.d/ubasudoers file to /opt/caspida/etc/sudoers.d/ubasudoers.
7. Run the following command as the root user:

   visudo -c -f /opt/caspida/etc/sudoers.d/ubasudoers

   The expected output is:
   /opt/caspida/etc/sudoers.d/ubasudoers: parsed OK

   1. If the file does not parse correctly do not proceed further; exit the root prompt and go to step 10 to start all services. Contact Splunk Support for assistance with fixing the ubasudoers file.
   2. If the file does parse correctly:
      1. Run the following commands:

         cp -f /opt/caspida/etc/sudoers.d/ubasudoers /etc/sudoers.d/ubasudoers
         chmod 440 /etc/sudoers.d/ubasudoers
         chown root:root /etc/sudoers.d/ubasudoers
         

      2. Remove the following line from the /etc/sudoers file, if it exists:
         caspida ALL=(ALL) NOPASSWD: ALL
      3. Remove the following line from the /etc/sudoers.d/ubasudoers file, if it exists:
         caspida ALL=(ALL) NOPASSWD: ALL
      4. Exit the root prompt.
8. Become the caspida user on the management node and perform a sync-cluster:

   /opt/caspida/bin/Caspida sync-cluster /opt/caspida/etc/sudoers.d/

9. Repeat step 7 on all Splunk UBA nodes before moving to next step.
10. Login to the Splunk UBA management node and start all services.

    /opt/caspida/bin/Caspida start-all

Enable ALL sudo access for the caspida account

To enable the caspida user to have full sudo permissions on the system, perform the following on all nodes in the cluster:

1. Login as the root user.
2. Add the following line to the /etc/sudoers.d/ubasudoers file:

   caspida ALL=(ALL) NOPASSWD: ALL

3. Exit the root prompt.