Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: remote desktop question |
|---|---|
| Date: | Fri, 21 Oct 2005 22:10:11 -0500 |
Well, Remote Desktop is fairly secure by itself. It is encrypted traffic, and using local group policies, you can encrypt it up to 256bit. Only the username is passed in cleartext for transmission. The password and everything else seems to be encrypted. Still, if it is open to the Internet, it can be exploited. I think with an administrator account, you have 6 tries, and then a lockout occurs for 30 minutes, and then you can try again. So, a brute force attack, although slow, could prove effective. You can set this with group policy as well. While you are at it, enforce strong complexity requirements (at least 6 characters, 3 out of 4 conditions must be met [uppercase, lowercase, special character, number]). I have always read that a better method is to tunnel RDP either through VPN, or through SSH. In either case, they provide an additional layer of security that stops everyone from trying to get into the system, and further stops everyone from seeing the remote desktop login. On 10/21/05, cc <cc@belfordhk.com> wrote:
Dear All, The company I work with recently required a remote desktop access and to keep the budget down, I used a XP Pro system to receive only one Remote Desktop user. Since this requires the opening up of a port on the firewall, I'm quite concerned. I have limited the system to only one or two users who can log on. Since this is my initial foray into the remote desktop client (in the past, we used PCAnywhere, but it's getting more and more expensive(hard to justify purchasing a license for each system). In what ways can I protect the remote desktop system from being broken into? (Well, aside from shutting it down.) Any pointers appreciated. Edmund
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Help writing a back up script, Aaron M Dulles-Coelho |
|---|---|
| Next by Date: | RE: VAN, Benjamin Fogel |
| Previous by Thread: | RE: remote desktop question, Richard Parry |
| Next by Thread: | RE: remote desktop question, List Account |
| Indexes: | [Date] [Thread] [Top] [All Lists] |