Security

Remote Desktop

A way to view and control another computer over a network with the owner’s permission. Access should be time-limited, authenticated and closed when the support session ends.

How it works

Remote desktop lets a person use another computer’s graphical environment through a network connection. The remote computer runs the applications while the client carries display and input. Hosting support, account permissions and connection methods vary between products; having a client application does not automatically make a computer an eligible host.

A practical example

An authorized worker might open an office computer from another location to use software installed there. The host still needs power, network availability and permission for that account. A local internet outage or sleeping host can prevent access even if the client itself works normally.

What to check

Check supported operating system editions, approved users and the organization’s intended secure access method. Keep the host updated and use strong authentication where supported. Verify any clipboard or file-sharing settings against the task. Plan how to disconnect and obtain local help if the host becomes unavailable. Do not open a public network port as a substitute for a security plan.

Limits and safe use

Remote desktop is not the same as unrestricted permission to access every file, and it does not replace backups. Direct exposure of remote administration to the internet needs careful protection. Use only systems you own or are authorized to administer; unsolicited callers asking for remote access should be verified independently before any session is allowed.

Technical sources

← All glossary terms