We are having a discussion as to the best and most secure way to connect to a Microsoft Terminal Server. My feeling is to have a user open VPN session using the Cisco VPN client and access the Terminal Server through the VPN tunnel. A colleague would rather use Microsoft's Terminal Server encryption and have me open a port in the firewall. Any opinions either way?
Well, from your description the obvious answer depends on how much security you want or how much configuration you want to do?
If you want to have simpler configuration, forwarding a port in firewall would be a good option, but then you will have to rely on Terminal Server's encryption for security. And if there is a vulnerability in Terminal Server (the chances of which are more) you might be in trouble.
On the other hand if you want to use Cisco VPN which I believe is more secure, you will need to invest a bit more time in configuring Cisco VPN. But obviously this will provide more granular control over the user's connection.
Infact, you can configure both Cisco VPN and Terminal Services Encryption if you are a seriously paranoid about the security...But in the end it all depends on what your requirements are.
I would prefer Cisco VPN in most cases, unless I dont have much time or I want to keep things simpler.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...