Remote work and remote access: doing it without leaving the company wide open
Publishing the remote desktop port was for years the quick way to give access from home. Today it is the door most of the attacks we handle come through. There are equally convenient and far safer options.
Why direct remote desktop no longer works
An exposed remote desktop service receives automated login attempts from day one. Nobody needs to target you: bots scan the whole internet.
With a decent password it holds for a while; with a reused one, it does not. And once they are in, they are inside the network.
What we set up instead
Nothing from the company is published to the internet: the user first enters an encrypted tunnel and then works exactly as in the office.
- Managed VPN with certificate or mandatory two-factor authentication
- Remote desktops reachable only from inside the VPN
- Per-user and per-folder permissions, not blanket access
- Connection logs so you know who entered, when and from where
- Remote worker devices with managed antivirus and up-to-date patching
It also has to perform
We measure real latency, size the office line and tune the remote session profile so the experience stays smooth even on modest home connections.
When the bottleneck is the office line, we say so: sometimes the answer is a new connection, not new software.
Support has to reach home too
Our support desk handles the home workstation exactly like the office one, using a remote control tool the user authorises.
And if the device fails physically, our repair and replacement circuit keeps the person working.
Related services
Does your team work from home over remote desktop?
We review how it is set up and propose a secure alternative without changing how people work.
Review my remote access