Securing Virtual Machines
As we provide public ip addresses to the Virtual machines (VMs) started by Eucalyptus and OpenStack it is important to follow some best practices. As a user and admin you will need to make sure the VMs are not exposed and vulnerable to attacks. FutureGrid and IU network have variety of tools to detect compromised systems, however, by applying some common sense and best practices we can prevent these incidents.
Images
To help you get started in each of our cloud infrastructure we uploaded images with compatible kernels. We advise you to use these. If you need to upload a customized image or kernel we advise to contact us first. At this point, we only have restrictions on uploading kernels. We also strongly recommend not to have passwords in the customized images.
Securing Virtual machines After running
Images
To help you get started in each of our cloud infrastructure we uploaded images with compatible kernels. We advise you to use these. If you need to upload a customized image or kernel we advise to contact us first. At this point, we only have restrictions on uploading kernels. We also strongly recommend not to have passwords in the customized images.
Securing Virtual machines After running
- Make sure to only open the ports that you need (use iptables or similar tool to close and open ports).
- Turn off unnecessary services (i.e. if you do not httpd or sendmail, turn it off).
- As soon as you are done with the VM, terminate it.
Futuregrid is a resource provider for