Network_netZones

Network_netZones

Network > Zones

A zone is a logical grouping of one or more interfaces designed to make management, such as the definition and application of Access Rules, a simpler and more intuitive process than following strict physical interface scheme. Zone-based security is a powerful and flexible method of managing both internal and external network segments, allowing the administrator to separate and protect critical internal network resources from unapproved access or attack.

A network security zone is simply a logical method of grouping one or more interfaces with friendly, user-configurable names, and applying security rules as traffic passes from one zone to another zone. Security zones provide an additional, more flexible, layer of security for the firewall. With the zone-based security, the administrator can group similar interfaces and apply the same policies to them, instead of having to write the same policy for each interface.

For more information on configuring interfaces, see Network > Interfaces.

SonicOS Enhanced zones allows you to apply security policies to the inside of the network. This allows the administrator to do this by organizing network resources to different zones, and allowing or restricting traffic between those zones. This way, access to critical internal resources such as payroll servers or engineering code servers can be strictly controlled.

Zones can also be used to set up the zones in which Guest Services are enabled.

Zones also allow full exposure of the NAT table to allow the administrator control over the traffic across the interfaces by controlling the source and destination addresses as traffic crosses from one zone to another. This means that NAT can be applied internally, or across VPN tunnels, which is a feature that users have long requested. SonicWALL security appliances can also drive VPN traffic through the NAT policy and zone policy, since VPNs are now logically grouped into their own VPN zone.

How Zones Work

An easy way to visualize how security zones work is to imagine a large new building, with several rooms inside the building, and a group of new employees that do not know their way around the building. This building has one or more exits, which can be thought of as the WAN interfaces. The rooms within the building have one or more doors, which can be thought of as interfaces. These rooms can be thought of as zones inside each room are a number of people. The people are categorized and assigned to separate rooms within the building. People in each room going to another room or leaving the building, must talk to a doorperson on the way out of each room. This doorperson is the inter-zone/intra-zone security policy, and the doorperson’s job to consult a list and make sure that the person is allowed to go to the other room, or to leave the building. If the person is allowed (i.e. the security policy lets them), they can leave the room via the door (the interface).

Upon entering the hallway, the person needs to consult with the hallway monitor to find out where the room is, or where the door out of the building is located. This hallway monitor provides the routing process because the monitor knows where all the rooms are located, and how to get in and out of the building. The monitor also knows the addresses of any of the remote offices, which can be considered the VPNs. If the building has more than one entrance/exit (WAN interfaces), the hallway monitor can direct people to use the secondary entrance/exit, depending upon how they’ve been told to do so (i.e. only in an emergency, or to distribute the traffic in and out of the entrance/exits). This function can be thought of as WAN Load Balancing.

There are times that the rooms inside the building have more than one door, and times when there are groups of people in the room who are not familiar with one another. In this example, one group of people uses only one door, and another group uses the other door, even though groups are all in the same room. Because they also do not recognize each other, in order to speak with someone in another group, the users must ask the doorperson (the security policy) to point out which person in the other group is the one with whom they wish to speak. The doorperson has the option to not let one group of people talk to the other groups in the room. This is an example of when zones have more than one interface bound to them, and when intra-zone traffic is not allowed.

Sometimes, people will wish to visit remote offices, and people may arrive from remote offices to visit people in specific rooms in the building. These are the VPN tunnels. The hallway and doorway monitors check to see if this is allowed or not, and allow traffic through. The doorperson can also elect to force people to put on a costume before traveling to another room, or to exit, or to another remote office. This hides the true identity of the person, masquerading the person as someone else. This process can be thought of as the NAT policy.

Predefined Zones

The predefined zones on your the SonicWALL security appliance depend on the device.The predefined security zones on the SonicWALL security appliance are not modifiable and are defined as follows:

Where Guest Services are supported, either wired or wireless devices Guest login is supported.

Note: Even though you may group interfaces together into one security zone, this does not preclude you from addressing a single interface within the zone.

Security Types

Each zone has a security type, which defines the level of trust given to that zone. There are five security types:

Allow Interface Trust

The Allow Interface Trust setting in the Add Zone window automates the creation of Access Rules to allow traffic to flow between the interface of a zone instance. For example, if the LAN zone has both the LAN and X3 interfaces assigned to it, checking Allow Interface Trust on the LAN zone creates the necessary Access Rules to allow hosts on these interfaces to communicate with each other.

Enabling SonicWALL Security Services on Zones

You can enable SonicWALL Security Services for traffic across zones. For example, you can enable SonicWALL Intrusion Prevention Service for incoming and outgoing traffic on the WLAN zone to add more security for internal network traffic. You can enable the following SonicWALL Security Services on zones:

The Zone Settings Table

The Zone Settings table displays a listing of all the SonicWALL security appliance default predefined zones as well as any zones you create. The table displays the following status information about each zone configuration:

Adding a New Zone

To add a new zone, perform the following tasks:

  1. Click Add under the Zone Settings table. The Add Zone window is displayed.
  2. Type a name for the new zone in the Name field.
  3. Select a security type Trusted, Public or Wireless from the Security Type menu. Use Trusted for zones that you want to assign the highest level of trust, such as internal LAN segments. Use Public for zones with a lower level of trust requirements, such as a DMZ interface. Use Wireless for the WLAN interface.
  4. If you want to allow intra-zone communications, select Allow Interface Trust. If not, select the Allow Interface Trust checkbox.
  5. Select any of the SonicWALL Security Services you want to enforce on the zone. You can select:
  6. Caution: Unsetting the Create Group VPN checkbox will remove any corresponding GroupVPN policy.

  7. Click OK. The new zone is now added to the SonicWALL security appliance.

Deleting a Zone

You can delete a user-created zone by clicking the delete icon in the Configure column. The Delete icon is unavailable for the predefined zones. You cannot delete these zones. Any zones that you create can be deleted.

Configuring a Zone for Guest Access

SonicWALL User Guest Services provides network administrators with an easy solution for creating wired and wireless guest passes and/or locked-down Internet-only network access for visitors or untrusted network nodes. This functionality can be extended to either wired or wireless users on the LAN, WLAN, and DMZ zones, or a public/semi-public zone of your choice.

To configure Guest Services feature:

  1. Navigate to the Network > Zones page in the SonicOS management interface.
  2. Under the Configure column, click the pencil icon button for the zone where you wish to add Guest Services. The Edit Zone menu comes up.
  3. Note: Depending on the zone, there may be tabs available for General, Guest Services, or Wireless.

  4. Click the Guest Services tab. Guest Services allows access to the Internet only.
  5. Choose from the following configuration options for Guest Services:
  6. Note: Refer to the SonicWALL Lightweight Hotspot Messaging Tech Note available at the SonicWALL documentation Web site http://www.sonicwall.com/us/Support.html for complete configuration of the Enable External Guest Authentication feature.

    Special Guest Services Features for Wireless Zones

  7. Click OK to apply these settings to this zone.

Configuring the WLAN Zone

  1. Click the Edit icon for the WLAN zone. The Edit Zone window is displayed.
  2. In the General tab, select the Allow Interface Trust setting to automate the creation of Access Rules to allow traffic to flow between the interfaces of a zone instance. For example, if the LAN zone has both the LAN and X3 interfaces assigned to it, checking Allow Interface Trust on the LAN zone creates the necessary Access Rules to allow hosts on these interfaces to communicate with each other.
  3. Select any of the following settings to enable the SonicWALL Security Services on the WLAN zone:
  4. Click the Wireless tab.
  5. In the Wireless Settings section, check Only allow traffic generated by a SonicPoint to allow only traffic from SonicWALL SonicPoints to enter the WLAN zone interface. This allows maximum security of your WLAN. Uncheck this option if you want to allow any traffic on your WLAN zone regardless of whether or not it is from a wireless connection.
  6. Tip: Uncheck Only allow traffic generated by a SonicPoint and use the zone on a wired interface to allow guest services on that interface.

  7. Select SSL VPN Enforcement to require that all traffic that enters into the WLAN zone be authenticated through a SonicWALL SSL VPN appliance.
  8. In the SSL VPN Server list, select an address object to direct traffic to the SonicWALL SSL VPN appliance. You can select:
  9. In the SSL VPN Service list, select the service or group of services you want to allow for clients authenticated through the SSL VPN.
  10. Under the SonicPoint Settings heading, select the SonicPoint Provisioning Profile you want to apply to all SonicPoints connected to this zone. Whenever a SonicPoint connects to this zone, it will automatically be provisioned by the settings in the SonicPoint Provisioning Profile, unless you have individually configured it with different settings.
  11. Select Only allow traffic generated by a SonicPoint to block non-SonicPoint wireless traffic.
  12. Note: For Guest Services configuration information, see the Configuring a Zone for Guest Access.

  13. Click OK to apply these settings to the WLAN zone.