Security considerations when running a VM: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
* Avoid using packages from unknown sources. | * 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 a recent image; for example, don't use Ubuntu 14.04 when Ubuntu 16.04 is available. | ||
* Use [https://docs.computecanada.ca/wiki/SSH_Keys SSH key] authentication instead of passwords. | * Use [https://docs.computecanada.ca/wiki/SSH_Keys SSH key] authentication instead of passwords. Cloud instances use SSH key authentication by default, and enabling password-based authentication is significantly less secure. | ||
* Install [https://www.fail2ban.org fail2ban] to block [https://en.wikipedia.org/wiki/Brute-force_attack brute-force attacks]. | * Install [https://www.fail2ban.org fail2ban] to block [https://en.wikipedia.org/wiki/Brute-force_attack brute-force attacks]. | ||
==Network security== <!--T:4--> | ==Network security== <!--T:4--> | ||
* Limit who can access your service. Avoid using '''0.0.0.0''' in the CIDR field of the security group form. | * Limit who can access your service. Avoid using '''0.0.0.0''' in the CIDR field of the security group form - in particular, don't create rules for "0.0.0.0" in the default security group, which applies automatically to all project instances. | ||
** Be aware of the range you are opening with the netmask your are configuring. | ** Be aware of the range you are opening with the netmask your are configuring. | ||
* Do not bundle ranges of ports to allow access. | * Do not bundle ranges of ports to allow access. | ||
* Think carefully about your security rules. Consider the following: | * Think carefully about your security rules. Consider the following: | ||
** These services aren't meant to be publicly accessible: | ** These services aren't meant to be publicly accessible: | ||
*** ssh (22) - this service allows interactive login to your instance and MUST NOT be made publicly accessible | |||
*** RDP (3389) - this service allows interactive login to your instance and MUST NOT be made publicly accessible | |||
*** mysql (3306) | *** mysql (3306) | ||
*** postgresql (5432) | *** postgresql (5432) | ||
*** nosql | *** nosql | ||
*** tomcat | *** tomcat | ||
*** ... many, many others | *** ... many, many others | ||
| Line 38: | Line 39: | ||
==Updating your VM== <!--T:5--> | ==Updating your VM== <!--T:5--> | ||
To upgrade a Linux VM choose the commands below for your particular distribution. Note you will need to reconnect to your VM after rebooting. | In order to keep a VM's operating system secure, it must be regularly updated - ideally weekly, or as often as new packages become available. To upgrade a Linux VM choose the commands below for your particular distribution. Note you will need to reconnect to your VM after rebooting. | ||
===Ubuntu/Debian=== | ===Ubuntu/Debian=== | ||
<source lang="console"> | <source lang="console"> | ||
Revision as of 22:54, 15 March 2019
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 (see updating your VM).
- 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. Cloud instances use SSH key authentication by default, and enabling password-based authentication is significantly less secure.
- 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 - in particular, don't create rules for "0.0.0.0" in the default security group, which applies automatically to all project instances.
- 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:
- ssh (22) - this service allows interactive login to your instance and MUST NOT be made publicly accessible
- RDP (3389) - this service allows interactive login to your instance and MUST NOT be made publicly accessible
- mysql (3306)
- postgresql (5432)
- nosql
- tomcat
- ... 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.
Updating your VM[edit]
In order to keep a VM's operating system secure, it must be regularly updated - ideally weekly, or as often as new packages become available. To upgrade a Linux VM choose the commands below for your particular distribution. Note you will need to reconnect to your VM after rebooting.
Ubuntu/Debian[edit]
$ sudo apt-get update
$ sudo apt-get dist-upgrade
$ sudo reboot
CentOS[edit]
$ sudo yum update
$ sudo reboot
Fedora[edit]
$ sudo dnf update
$ sudo reboot
Further Reading[edit]
An amazon article on securing instances: https://aws.amazon.com/articles/1233/