There are many screen sharing alternatives that you can potentially use. RDP just happens to be built in and frankly it works pretty well for what it does.

If you can lock down permissions to domain or local accounts your chance of getting hacked is virtually nil as you need to be on the network in order to get in. If you are really security sensitive a VPN is will keep out all external traffic.

That said many of the screen sharing solutions can also work. Zoom and TeamViewer work really well as well and can be run as services on a remote machine for sharing or single access, but at the end of the day you have the same security issues as RDP - in the end you're accessing a remote machine and there's potential for password attacks with any of these approaches. So tooling isn't really going to help - the only thing that will is network infrastructure to ensure your environment is secure.

+++ Rick ---

>Hi all,
>
>Working on security stuff again today. I use RDC to log into one of my customer's servers to upload changes/source code etc and test. In discussion with them, they had talked about closing down their RDC server because it "opens a security hole because [they say] when the RDC session is open, then anything from your desktop could find its way to our servers".
>
>In a way, I can see this (I have not yet checked if AD group policy has options to prevent drive mapping etc - I will look into that later).
>
>If RDC is not that secure, are there other programs that allow an RDC-like connection where the only thing going back and forth are keyboard/mouse and video? In a sense, the program would open screen into their RDC server but nothing can really pass between my PC and their server other than what I type. I would have to transfer updates via another mechanism but I could tell them that nothing else can move across the wire.
>
>Albert