Security considerations when running a VM: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
<translate> | <translate> | ||
''Parent page: [[Cloud]]'' | ''Parent page: [[Cloud]]'' | ||
<!--T:1--> | <!--T:1--> | ||
On the [[CC-Cloud|cloud]], you are responsible for the security of your virtual machines. | On the [[CC-Cloud|cloud]], you are responsible for the security of your virtual machines. |
Revision as of 21:26, 14 November 2017
Parent page: Cloud
On the cloud, you are responsible for the security of your virtual machines.
This document is not a complete guide, but will set out some things you need to consider when creating a VM on the cloud.
Keep the operating system secured[edit]
- Apply security updates on a regular basis.
- Avoid using packages from unknown sources.
- Use a recent image. For example, don't use Ubuntu 14.04 when Ubuntu 16.04 is available.
- Use SSH key authentication instead of passwords.
- Install fail2ban to block brute-force attacks.
Network security[edit]
- Limit who can access your service. Avoid using 0.0.0.0 in the CIDR field of the security group form.
- Be aware of the range you are opening with the netmask your are configuring.
- Do not bundle ranges of ports to allow access.
- Think carefully about your security rules. Consider the following:
- These services aren't meant to be publicly accessible:
- mysql (3306)
- postgresql (5432)
- nosql
- RDP (3389)
- ... many, many others
- Some services are meant to be accessible from the internet:
- Apache (80, 443)
- Nginx (80, 443)
- ... others
- These services aren't meant to be publicly accessible:
- Configure your web server to use HTTPS instead of HTTP.
- In many case HTTP should only be used to redirect traffic to HTTPS.
- Do NOT run a mail server.
Further Reading[edit]
An amazon article on securing instances: https://aws.amazon.com/articles/1233/