Remote Desktop Protocol (RDP) using an SSL VPN


    Returning to the Lightboard, Peter Silva (back on DevCentral team!) explains why its a bad idea to expose RDP to the internet and how using a SSL VPN like BIG-IP APM is a much safer and better idea.


    Previous articleRealtime Supply and Demand Indicator NT8 Version – Ninjacators FREE Indicator of the Month
    Next articleAWS Lambda Basic Concept In HINDI


    1. 1) create a strong password for your machine 2) setup password lockout after tries 3) adjust firewall rules in windows advanced settings for rdp to allow only connections from remote ip only 4) if you have the option to conveniently enable/disable port forwarding only enable when in use and disable when not. Basically with all 4 setup is virtually impossible for hacker can get to access your computer because of so many layers and just not worth it for them and they'll move to easier targets. and yes you WILL have hackers trying to bruteforce into your computer but they need your exact username and exact password. so don't use a common user name like user or admin lol.

    2. Consider using Review Desktop Gateway. Doesn't put the uncontrolled remote device on your corporate network, doesn't require purchase of extra software (included with Windows), doesn't require help desk to assist users with "complex" VPN configuration on whatever device the user owns. Runs on https port.