Teramind delivers updates for its server and web interface through Teramind server updates. To learn more, see How to Update the Teramind Server. The operating system that the server runs on is not updated by Teramind. On On-Premises and Private Cloud deployments, you are responsible for applying operating system security updates and patches to keep your server secure.
This article applies to Teramind servers running Debian 12 (bookworm). It does not apply to Teramind Cloud, where Teramind manages the operating system. If your server runs Ubuntu, RHEL, or Amazon Linux, use that distribution's own update tools.
Before You Begin
Snapshot: Take a snapshot or backup of the server VM so you can roll back if something goes wrong.
SSH Access: Make sure Enable SSH access is turned on under Configurations > Settings > Server > Security settings. You can also use the hypervisor console.
Internet Access: The server must be able to reach the Debian update servers (
deb.debian.organdsecurity.debian.org). If your server has no internet access, contact Teramind Support for help with an offline update.Maintenance Window: Some updates require a reboot, which makes the dashboard unavailable until the server is back online. Plan the update during a maintenance window.
Install Security Updates
1. Connect to the server via SSH or the hypervisor console and switch to the root user:
sudo -i
2. Check the Debian version. The VERSION line should show 12 (bookworm):
cat /etc/os-release
3. Create a source list that contains only the Debian security repository:
mkdir -p /etc/apt/security-only
awk -v RS= -v ORS='\n\n' '/-security/' /etc/apt/sources.list.d/debian.sources > /etc/apt/security-only/security.sources
4. Confirm that the new file contains only the bookworm-security entry:
cat /etc/apt/security-only/security.sources
5. Refresh the package lists:
apt-get update
6. Install the security updates. When prompted, press Y and Enter:
apt-get upgrade -o Dir::Etc::SourceList=/dev/null -o Dir::Etc::SourceParts=/etc/apt/security-only
7. If the update installed a new kernel (packages starting with linux-image), reboot the server:
reboot
8. After the server is back online, sign in to the dashboard and check System > System Health for any issues.
Note: Docker is installed from Docker's own repository, so these commands do not update it. Contact Teramind Support before updating Docker.
Apply Updates Later
You only need to create the security source list (steps 3 and 4) once. To install new security updates later, connect to the server as root and run:
apt-get update
apt-get upgrade -o Dir::Etc::SourceList=/dev/null -o Dir::Etc::SourceParts=/etc/apt/security-only
If a new kernel was installed, reboot the server.
Outdated Debian Versions
If your server runs a Debian version older than 12, upgrade it before applying security updates. Contact Teramind Support for help with an in-place upgrade from Debian 9, 10, or 11, including offline upgrades. On Debian 8 or earlier, these commands no longer work. Deploy a new Teramind server and migrate your data instead.
Best Practices
Apply Updates Regularly: Install Debian security updates as they become available.
Limit Access: Keep the server isolated from the internet except for what updates require, and turn off SSH access when you don't need it.
Monitor System Security: Regularly review your server's security posture and address any vulnerabilities promptly.
Get Help: Contact Teramind Support if you run into problems during an update or upgrade.