EMZETT.Remote Maintenance
In short: Remote access to a computer or system over the network in order to fix problems or carry out maintenance work without being physically on site.
In more detail: Technically this usually runs via remote desktop protocols or SSH/shell access, often additionally secured via VPN. In everyday IT support (see help desks), one of the most common ways to solve problems for customers or employees without needing an on-site appointment.
In Depth
Text-based vs. graphical
Roughly two types of remote maintenance can be distinguished: text-based access via a shell/command line (classically via SSH, the standard method for server and network administration) and graphical remote access, in which the entire screen content of the target device is transmitted as an image or video stream (Remote Desktop Protocol/RDP on Windows, VNC across platforms, or commercial tools such as TeamViewer/AnyDesk for supporting end users without technical knowledge). Graphical access is much more intuitive for laypeople who want to follow instructions visually, whereas text-based access is considerably easier on bandwidth (plain text instead of continuous screen transmission) and easier to automate, because scripts can be run directly and repeatably via a shell instead of reproducing every click manually.
Securing it in professional environments
From a security point of view, remote maintenance is a particularly sensitive area, because by definition it allows full or at least far-reaching access to someone else’s system from outside — a compromised remote maintenance access is therefore a particularly attractive target for attackers. That’s why in professional environments access is almost always secured in several ways: via a VPN (the actual remote maintenance port isn’t even reachable from the open internet, only after a VPN has been established successfully); via authentication with public-key methods instead of a plain password (see SSH, much more resistant to brute-force attacks); via two-factor authentication as an additional hurdle; and via complete logging (audit log) of who accessed what and when — both for troubleshooting afterwards and for detecting misuse.
Jump hosts and zero-trust approaches
In larger infrastructures, remote maintenance is often additionally routed via a central “jump host” (also called a bastion host): instead of accessing every individual server directly, the administrator first connects to a single, particularly hardened and monitored intermediate system, from which the actual access to internal systems then takes place — this reduces the attack surface to a single, well-controllable entry point instead of making many systems individually reachable from outside. Modern zero-trust architectures go even further and verify identity and authorisation again on every single access, instead of permanently trusting a VPN tunnel once it’s been established.
Everyday IT support
In everyday IT support (see help desks), remote maintenance is the standard way to solve problems for customers or employees without needing a time-consuming on-site appointment — often with the user’s explicit consent before every single session (instead of permanently open access), to prevent misuse and data protection concerns from the outset. With commercial support tools such as TeamViewer, the user typically generates a temporary, one-off access code for this, instead of handing the support employee permanent credentials.
See also: SSH, VPN, Help desks, Authentication