MyRackspace Firewall Manager

The MyRackspace Firewall Manager application is an upgraded version of the firewall control panel, which enables you to view and edit your firewall configurations. The Firewall Manager is available for all Cisco PIX, Cisco ASA, and Juniper SRX 100/240 firewalls. It is not available for Cisco PIX 515/525/535 URFO and firewalls in a high-availability configuration.

The Firewall Manager allows you to perform the following actions on the firewall's inbound access control list:

  • Add permit policies
  • Add and delete IP addresses to be denied by means of a blacklist
  • Add and delete IP addresses from address sets prefixed with fwcp
  • Delete single deny policies
  • Add comments (notes) to a permit policy, deny policy, IP addresses in the blacklist, and IP addresses in an address set
    prefixed with fwcp-
  • View and export (.csv) changes that occurred on the firewall
  • Export (.csv) the firewall's inbound access list

Firewall user agreement

Every three months, users with administrative and editing privileges are prompted to accept the Firewall User Agreement terms for each firewall. After you accept the user agreement, you and the primary contact person on the account receive a confirmation email. If you choose not to accept the agreement, you can still view your firewall configuration, but you cannot modify it.

Firewall Manager overview

This section describes the main concepts about and attributes that you define for policies in the Firewall Manager.

Hit Count

For Cisco PIX and ASA firewalls, access list hit counts are used to determine policy usage. Any policy that has a hit count of zero is considered as unused. You can view the access list hit counts in the Hit Count column. Hit counts are not enabled by default on the Juniper SRX 100 or 240 firewall. You can enable the hit count on a per-policy basis. However, if you enable it, the hit counts are not visible in the Firewall Manager. The access list hit counts are reset whenever the firewall is restarted. We plan to add support for this feature in a future version.

Access control list

An access control list is a list of policies that the firewall evaluates when governing traffic for a certain traffic path. With the Firewall Manager, you can manage only the firewall's inbound traffic.

Protocol

You can choose an IP (all ports), TCP (single port), or UDP (single port) protocol when you create a policy.

  • IP (all ports): Creates an IP policy that makes all ports and services on your server available from the IP address or address range that you supply. This protocol gives the supplied IP address or range of addresses complete access through the firewall. If you select this protocol, you cannot specify a port number.
    Best practices warning: Do not use an IP address unless it is absolutely necessary. More traffic results in less security.
  • TCP (single port): You must pair this protocol with select ports. This is the most commonly used port. If you are unsure of which port to use, choose this one.
  • UDP (single port): You must pair this protocol with select ports.

For more information about TCP and UDP protocols, see the Destination port section of this article.

Note: The Protocol field sometimes states undefined. This behavior is expected for Juniper firewalls. The protocol is defined on the firewall itself and is not included in the output from the firewall. We are investigating how to display the protocol in a future version of the Firewall Manager.

Source IP address

The source IP address is the same as the IP address of the visiting client. It is the IP address that you want to allow through the firewall for a given destination port or service.

The source IP is often set to Any IP for web and similar services. For services such as FTP and email access, the source IP is often limited to just a few client IP addresses. See the best practices warning in the previous section. You can choose the following options:

  • Enter IP: Allows you to enter a specific IP address
  • Any IP: Allows traffic from any source IP address through the firewall
  • Get My Current IP: Automatically retrieves your client's IP address

Netmask source and destination

Netmasks are a way to specify a range of IP addresses. If you enter an IP address in the Source or Destination fields, you can select a netmask. The default option is **/32 (255.255.255.255)**. Netmasks are listed in both Classless Inter-Domain Routing (CIDR) notation (also known as slash notation) and IP format. Following is a list of allowed IP address ranges:

CIDRNetmaskNumber of hosts in each range
/24255.255.255.0256 (0-255)
/25255.255.255.128128 (0-127 or 128-255)
/26255.255.255.19264 (0-63, or 64-127, or 128-192, or 192-255)
/27255.255.255.22432 (0-31, 32-63, 64-95, others, 192-233, 224-255)
/28255.255.255.24016 (0-15, others, 240-255)
/29255.255.255.2488 (0-7, others, 248-255)
/30255.255.255.2524 (0-3, others, 252-255)
/32255.255.255.2551 (single IP address)

Destination IP address

The destination IP address is the target IP address that resides on the server behind the firewall. See the Source IP address section for the available options. You can enter an IP address, select Any IP, or select an IP address from the menu that includes the primary and secondary IP addresses of the devices behind the firewall.

Note: The new Search by Device Name feature is now available in the Firewall Manager.

Destination port

If you select either the TCP or UDP protocol, you can enter a port number or select one from the menu of common ports. Ports 1 to 65535 are accepted.

The following port and protocol combinations are not permitted:

  • Port 21 and UDP
  • Port 22 and UDP
  • Port 25 and UDP
  • Port 69 and TCP
  • Port 80 and UDP
  • Port 110 and UDP
  • Port 115 and UDP
  • Port 443 and UDP

Cisco PIX and ASA firewalls

For Cisco PIX and ASA firewalls, access list hit counts are used to determine policy usage. Any policy that has a hit count of zero is considered as unused. You can view the access list hit counts in the Hit Count column. Hit counts are not enabled by default on the Juniper SRX 100 or 240 firewall. You can enable the hit count on a per-policy basis. However, if you enable it, the hit counts are not visible in the Firewall Manager. The access list hit counts are reset whenever the firewall is restarted. We plan to add support for this feature in a future version.

Add a permit policy

You can open a single port to all server IP addresses for a specific IP address.

Note: Do not perform this action unless the source IP address is trusted; otherwise, any device provisioned in the future will be accessible by this source.

In the following image, a policy was added to allow an alternate SMTP (Port 587) mail traffic through the firewall from the IP address 207.250.49.146.

{{}}

The following image shows a protocol that was changed to IP (all ports). When you select this protocol, you cannot enter or select a port number.

{{}}

Copy a policy

Click copy to copy an existing policy. The form fields are automatically populated where possible. You can then modify the policy before adding it. You cannot copy the following kinds of policies:

  1. Single deny policies
  2. Policies that reference an address set
  3. Locked policies

The copy icon is not displayed for these kinds of policies on the Firewall Manager screen.

Delete a policy

With the File Manager, you can delete permit policies and single deny policies by using the following steps:

  • In the Firewall Manager, select the check box for the policy that you want to delete.
  • Click Delete Selected Policies on the side bar.

If you want to delete multiple policies, you must delete them one at a time. Some policies do not display a check box and cannot be deleted. These policies allow Rackspace support technicians and specific systems to access your server.

Add a comment to a permit or deny policy

You can add a comment to a permit or deny policy after you add the policy to the configuration. You can then modify and delete comments that you add.

View and manage IP groups

If a network address set is prefixed with fwcp, you can add and delete IP addresses from the IP group. If a network address does not have the fwcp- prefix, you can only view the IP group. The address set must contain at least one IP address at all times. You can view updates to address sets in the change log.

To manage editable IP groups with the fwcp- prefix, click the hyperlink for the group you want to manage. In the manage IP group dialog box that appears, you can manage addresses and comments from the address set from this window.

To view non-editable IP groups, click the hyperlink for the group that you want to view.

Note: For changes to be written to the firewall, click Commit Changes.

Manage the blacklist

The blacklist is a central area for source IP addresses for which you want to deny access. You can add and delete host IP addresses and IP ranges from the Manage Blacklist menu. All IP addresses listed in the earlier version were migrated to this blacklist. Updates to the blacklist are logged in the change log.

Access the blacklist from the Manage Blacklist option in the side navigation bar, as shown in the following image. Customers with view-only permissions have the View Blacklist option.

Use the Manage Blacklist dialog box to add IP addresses to and delete IP addresses from the blacklist, and to add comments.

Note: The blacklist is listed a FWCP-Customer-Deny Object Group in earlier versions of the firewall manager.

View the Change Log

The Change Log tracks details about each change made in the Firewall Manager, with the exception of comments. It lists the type of change that occurred, the category of the change, details about the change, the user who made the change, and the date the change was made.

Note: Changes made directly in the firewall are not displayed in the Change Log.

To access the log, click the Change Log tab.

View static NATs (network address translations)

The Static NATs tab displays the public IP address, the private IP address that the public IP address is translated to, and the associated private IP netmask.

Note: If the device is a Cisco ASA using software version 8.3 or later, the static NATs cannot be displayed because they are formatted differently in this version. We will be working to support iOS 8.3 in a future version of the Firewall Manager.