Question

Security Risk in Cloud Server?

  • Posted on November 20, 2013
  • dips_wantAsked by dips_want

I am switching from shared hosting to virtual server. I have no experience in server administration but the tutorials here are easy to understand. My main concern is the risk involved in running own server. What are all the security breaches and server related information a novice user should have before running its own server ?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Thanks Pablo of vD and mist1024. The information you provided are pretty helpful.

@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>.

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>