Security Risk in Cloud Server?

Check out: <br> <br>1.) <a href=“https://www.digitalocean.com/community/articles/initial-server-setup-with-ubuntu-12-04”>Initial Server Setup with Ubuntu 12.04</a>; <br> <br>2.) <a href=“https://www.digitalocean.com/community/articles/how-to-setup-a-firewall-with-ufw-on-an-ubuntu-and-debian-cloud-server”>How to Setup a Firewall with UFW on an Ubuntu and Debian Cloud Server</a>; <br> <br>3.) <a href=“https://www.digitalocean.com/community/articles/how-to-use-filezilla-to-transfer-and-manage-files-securely-on-your-vps”>How To Use Filezilla to Transfer and Manage Files Securely on your VPS</a>; <br> <br>4.) <a href=“https://www.digitalocean.com/community/articles/how-to-create-ssh-keys-with-putty-to-connect-to-a-vps”>How To Create SSH Keys with PuTTY to Connect to a VPS</a> (even if you don’t use PuTTY, this article contains a good section on <code>password-less logins</code>).

You may wish to consider using a panel, either Cpanel or one of the others, if you do not previously have experience with maintaining your own server. Cpanel is unfortunately not free, but having worked with it at a prior job, it comes with a few features that could be useful including cphulkd that blocks brute force attempts, and provides a fairly easy to use interface. <br> <br>However, without a panel, I would suggest minimizing the amount of services that you may be running, and the services being exposed on the outside internet. What those panels do well, at least Cpanel, is that it bundles all the usual services for DNS, mail, http servers, into one coherent package. If you are not fully familiar with exim or postfix, for example, you would probably want to ensure that those services are off when you are not using them, in case the configuration may be allowing open relay access or something similar. Familiarizing with iptables, and other utilities such as fail2ban (https://www.digitalocean.com/community/articles/how-to-protect-ssh-with-fail2ban-on-ubuntu-12-04) may also be helpful. <br> <br>From my own experience, it is generally “learn-as-you-go”. On my own setup, I had actually setup most of it on a local VM at home, unexposed to the outside, before transferring the configuration to my server. <br>

@mist1024, <br> <br>Great point re: testing things out locally (or, at a minimum, on a different cloud server) b/f deploying something to your production server. As a recent shared-hosting-convert myself, I learned this all-important principle the hard way. <br> <br>On that front, I highly recommend a <a href=“http://www.vagrantup.com/”>Vagrant</a> box inside of <a href=“http://www.virtualbox.org/”>VirtualBox</a> (both of which are free). <br> <br>For an overview on how Vagrant can be used to develop your WordPress site, locally, check out: <a href=“https://www.digitalocean.com/community/articles/why-how-to-set-up-a-wordpress-local-development-environment-with-vagrant”>Why & How-To Set Up a WordPress Local-Development Environment With Vagrant</a>.