How to configure and use security groups
Security groups in OpenStack are part of the network security mechanisms provided for the users. They resemble sets of simple firewall rules allowing specific network traffic at a Port of a VM that connects it to a network. The rules allow specific network port numbers and protocols while also differentiating between ingress and egress directions. Usually security groups are assigned to the Port(s) when a virtual machine is created, but assignments can also be changed at runtime later on. Multiple security groups can be assigned to a VM or Port simultaneously and in such case they will be combined as the union of all their rules.
Security groups are mutable resources. Their rules can be adjusted at any time after creation. Changing the rules of a security group will immediately apply the changes to all Ports or VMs it is assigned to. It is advisable to always review resources which use a security group before making changes to it.
Identify the requirements of your setup
Every virtual machine that is created may need different firewall rules. These requirements can also change over time. Adding or removing security groups will allow users to adapt the firewall rules specifically to their virtual machines.
To harden the firewall settings for your virtual machine you may follow these steps:
- Before creating a virtual machine its purpose is usually already known. Use this information to identify all incoming and outgoing traffic rules that will be needed based on the communication patterns of the services it is meant to deploy. This includes communication protocols, port numbers, communication directions and optionally target/source address ranges.
- Look through already existing security groups and their rules. If a security group allows more traffic than needed it SHOULD NOT be used. If a security group contains only a subset of the required rules it MAY be used in combination with other security groups that contain rules which fulfill the remaining required traffic rules from point 1.
- If you were not successful in finding an appropriate combination of existing security groups or you need additional specific rules to cover all requirements, you MAY create one or more new Security Groups in which you can add the required rules.
- After ensuring the existence of one or more security groups that fulfill your requirements, you can create the VM with those security groups already specified in the creation command.
Further security considerations
When implementing network security requirements, firewall rules alone are not always sufficient and might need to be augmented with additional configuration or time-based constraints. Notable examples are:
SSH SSH is needed on many virtual machines to operate their guest operating system. In a security group the port 22 can be opened for the TCP protocol to allow incoming SSH connections. But that only should be done while also restricting the SSH configuration to public key authentication only (the recommended way) or having a strong username and password policy already applied to the operating system of the virtual machine. Otherwise default usernames and passwords which are often preconfigured in system images may be exploited through the exposed SSH port which enables attackers to compromise the virtual machine.
ICMP It might be useful to be able to ping a virtual machine or use other ICMP requests. But for some virtual machine configurations this is either not necessary at all or only temporarily needed. One benefit of security groups among other things is the ability to be easily added to and removed from existing virtual machines. So a dedicated security group allowing ICMP could be added temporarily to a virtual machine for debugging purposes and removed from it afterwards.
How to create security groups
Security groups are managed within a project. So every project will have a different set of security groups. They can be added dynamically to each virtual machine, during their creation or afterwards. Additionally, they may also be removed from VMs at any point.
Every project has its own default security group, which rules can be edited. Additionally other security groups can be added until the project's quota is exhausted. To add a security group, use the following command:
openstack security group create $SECURITY_GROUP
Within every security group rules can be added up unto a defined maximum of rules, that usually is about 100. Rules can be added to security groups with the following command:
openstack security group rule create [...] $SECURITY_GROUP
To delete rules from a security group, the rule id has to be used. It is listed in the details of the rules section of the security group.
openstack security group rule delete $RULE_ID
Default security group
Unless specified otherwise, the default security group is assigned to all VMs or Ports at creation. To use any other than the default security group at creation it is necessary to specify the desired security group(s) during the creation process.
To review which rules are defined in a security group, the following command can be used:
openstack security group show default
Recommended security groups
While projects can use very different aspects in security group rules and thus the security groups will always differ between projects, there are some security groups that are widely used. Through the nature of security groups being seen as a set of rules that can be combined, having some basic security groups that allow basic protocols is a commonly used setup. This section will demonstrate how to create some security groups for commonly used protocols and ports.
- A security groups, that allows incoming SSH traffic:
openstack security group create ssh
openstack security group rule create --ingress --protocol tcp --dst-port 22 ssh
- A security group, that allows incoming HTTP requests:
openstack security group create http
openstack security group rule create --ingress --protocol tcp --dst-port 80 http
- A security group, that allows incoming HTTPS requests:
openstack security group create https
openstack security group rule create --ingress --protocol tcp --dst-port 443 https
- A security group, that allows incoming ICMP requests:
openstack security group create icmp
openstack security group rule create --protocol icmp icmp
How to use security groups
Security groups can be assigned to multiple resources simultaneously (such as VMs or Ports). This means that security groups are reusable and don't need to be recreated for each applicable resource individually.
Usually, initial security groups are added at the time of the creation of a VM.
During creation, multiple security groups can also be added at the same time by repeating the --security-group argument:
openstack server create [...] --security-group $SECURITY_GROUP_1 --security-group $SECURITY_GROUP_2 $SERVER_NAME
To add a security group to an existing VM, the following command can be used:
openstack server add security group $SERVER_NAME $SECURITY_GROUP
To remove a security group from a VM, the following command can be used:
openstack server remove security group $SERVER_NAME $SECURITY_GROUP
The source of this document can be found in the SovereignCloudStack/docs repository.
Author: SCS Community, License: CC by Attribution 4.0 International