Firewalls and Microsegmentation in Cloud Networks

Cloud+ · Security · By Super Admin

Understand how cloud firewalls differ from data center firewalls and how microsegmentation provides granular security control.

The Absence of Traditional Firewalls in Cloud

One thing that throws off a lot of people who are new to cloud networking is the apparent absence of firewalls. As they explore their new cloud environment, they see the obvious parallels between the cloud and the data center—VMs, network interfaces, storage volumes—but cannot seem to find any firewalls. The apparent absence of firewalls marks a significant difference between the cloud and the data center. In the data center, a firewall isolates different portions of the network and restricts the types of traffic that can pass between subnets. For example, you may have one subnet for certain database servers and another subnet for application servers, and both subnets are separated by a firewall. By defining rules on the firewall, you can allow only the traffic that you want to pass between the application subnet and database subnet. This configuration provides some isolation, but it falls short in one important way: devices within the same subnet have unrestricted access to each other. The firewall cannot see that intra-subnet traffic, let alone restrict it.

Microsegmentation Approach

Cloud networks overcome this limitation by using a concept called microsegmentation. In the cloud, you can configure and apply packet filtering rules at the network interface level, not just the subnet level. Essentially, you configure firewall rules and choose where to apply them. This eliminates blind spots and gives you granular control over how your cloud resources communicate. This approach makes security more scalable by letting you apply rules to VMs according to their role, rather than what subnet they reside in. In the cloud you can, for example, apply a particular set of rules to all of your database VMs, regardless of what host they are on or what subnet they are in.

The terminology around firewall rules is fluid and somewhat interchangeable between cloud providers. Interface Rules applied to the network interface of a VM are often called security groups. These rules allow or deny traffic to and from a VM's network interface. This is somewhat analogous to an access control list (ACL) applied to a switchport in the data center. Network Rules applied to an entire virtual network (or subnet) are sometimes called ACLs or—confusingly—network security groups. This is analogous to an ACL applied to an entire VLAN in the data center.

Firewall Rule Configuration

At a minimum, firewall rules consist of four elements: Direction (Inbound or outbound), Source (One or more IP addresses), Protocol (For example, TCP, UDP, or ICMP), and Port (The TCP or UDP port, if applicable). Firewall rules always include an implicit deny, causing them to deny all traffic by default. Therefore, the cloud provider will likely add a few rules to allow common traffic. For example, when you create a new VM, the provider will probably create a rule to allow outbound IPv4 network access to any address. Without this rule, the instance would be unable to reach out to the Internet to get updates.

When creating your firewall rules, you must understand whether the firewall you are dealing with is stateful or stateless, because this will impact the rules that you need to create. Stateful means that when traffic is allowed to pass in one direction, the firewall intelligently allows return traffic in the opposite direction. For example, when a VM reaches out to a server on the Internet to download updates, the firewall allows return traffic from that server. Stateful firewalls use connection tracking to identify return traffic and distinguish it from unsolicited traffic. Stateless A stateless firewall does not automatically allow return traffic, so you must create an explicit rule to allow it. This is similar to an ACL on a traditional switch. Consequently, stateless firewall rules tend to be broader and less restrictive than stateful firewall rules.

0.0 (0 ratings)

Discussion (0)

No discussion on this article yet — be the first to comment.

Please sign in to join the discussion.