Checking Open Ports in Azure | John Morehouse
Let's be honest here, data security is really important to me. Some people probably think that I go to extremes to ensure that my data as well as my customers data is secured. With that, sometime ago, I wrote a blog post on utilizing a VPN server that I built on an Azure Virtual Machine to help facilitate a secure connection whenever I am away from my home network. Using a VPN server is a great way to ensure security and peace of mind. Turns out that the server got hacked. And it was my fault. See, if you leave certain ports open to the outside world like I did, you are just asking for hackers to attack you. And that's exactly what happened. When I first created the virtual machine, I mistakenly left port 3389, which is used to make remote desktop protocol (RDP) connections, open and available to the world. There wasn't any rule in place limiting those connections to a certain IP address or ranges, so it was a free for all for hackers. By the way, hackers will routinely scan