Applies To:
Show Versions
BIG-IQ Security
- 4.3.0
About rules and rule lists
With the BIG-IQ Security system, you can manage rules and rule lists from the Rule Lists panel. You import and manage rules (and/or rule lists) from BIG-IP devices. You can also define rules and rule lists within BIG-IQ Security and deploy back to the BIG-IP device.
Network firewalls use rules (and rule lists) to specify traffic-handling actions.
Rules are not independent objects and can exist only within rule lists or policies. You can define a list of rules for a specific firewall and/or refer to one or more shared rule lists (by name from other firewalls).
The network software compares IP packets to the criteria specified in rules. If a packet matches the criteria, then the system takes the action specified by the rule. If a packet does not match any rule from the list, the software accepts the packet or passes it to the next rule or rule list. For example, the system compares the packet to self IP rules if the packet is destined for a network associated with a self IP address that has firewall rules defined.
A packet must pass all tests to match successfully. For example, to match against a source subnet and several destination ports, a packet must originate from the given subnet and must also have one of the specified destination ports.
Rule lists are containers for rules. A rule list can contain thousands of ordered rules but cannot be nested inside another rule list. It is an ordered list of rules, which means that rules are run in the order they appear. However, you can reorder rules at any time.
Rules and rule lists can be applied to all firewall types:
- Global
- Route domain
- Virtual server
- Self IP
- Management (rules only)
You can reuse a rule list across multiple firewalls, such as the firewalls for self IPs, route domains, and the global firewall. To reuse rule lists, drag-and-drop them to firewalls and policies as you choose.
Adding rules
Adding rule lists
Managing rule lists
Cloning rule lists
Users with the roles of Firewall_View or Firewall_Deploy cannot clone policies.
.- Navigate to the Rule Lists panel.
- Hover over the name of the rule list that you want to clone and when the gear icon appears, click it to display the expanded panel.
- Click Clone.
-
In the Properties tab, edit the fields as required. Click
Tab to advance from field to field.
Option Description Name Enter a name for the cloned rule list. The clone cannot have the same name as the source rule list unless the partition name is changed. Description Enter an optional description. Partition Although pre-populated with Common (default), you can set the partition when creating or cloning rule lists by entering a unique name for the partition. Note: The partition with that name must already exist on the BIG-IP device.No whitespace is allowed in the partition name. - In the Rules tab, edit the rules as required to configure the clone. You can also click Create Rule to add a new rule.
- When finished, click Add. Any changes made are preserved. If you click Cancel, the rule list is not cloned.
Removing rule lists
Rule and rule list properties
You can configure network firewalls after import into the BIG-IQ Security system through the Firewall Contexts panel. Or, you can edit imported rules, rule lists, or policies through the Rule Lists panel or the Policies panel. However, you must edit shared objects through the Shared Objects panel. Shared objects cannot be edited inside rules. The following table lists and describes the properties required when configuring network firewall rules and rule lists.
Property | Description |
---|---|
Name | Unique, user-provided name for the rule or rule list. If the name is a rule list name, it is preceded by referenceTo_ when dragged-and-dropped to a firewall or policy. For example: referenceTo_sys_sef_allow_all. |
Address (Source) | There are many ways to construct an IPv4 or IPv6 address, address range, or
address list. The following methods and examples are not meant to be exhaustive.
IPv4 format: a.b.c.d[/prefix]. For example: 60.63.10.10 IPv6 format: a:b:c:d:e:f:g:h[/prefix]. For example: 2001:db7:3f4a:9dd:ca90:ff00:42:8329 You can specify subnets using forward slash (/) notation; for example: 60.63.10.0/24. An example of an IPv6 subnet is as follows: 2001:db8:a::/64. You can append a route domain to an address using the format %RouteDomainID/Mask. For example, 12.2.0.0%44/16. From the drop-down list, select:
To the right, options are provided to add additional addresses, address ranges, or address lists (+) and to delete addresses, address ranges, or address lists (X). When finished, click Save or Add. |
Port | Ports, port ranges, or port lists. From the drop-down list, select:
To the right, options are provided to add additional ports, port ranges, or port lists (+) and to delete ports, port ranges, or port lists (X). When finished, click Save or Add. |
VLAN | Name of the VLAN physically present on the device (Internal, External, or Any). The VLAN must be configured on the device or the deploy fails. When finished, click Save or Add. |
Address (Destination) | There are many ways to construct an IPv4 or IPv6 address, address range, or
address list. The following methods and examples are not meant to be exhaustive.
IPv4 format: a.b.c.d[/prefix]. For example: 60.63.10.10 IPv6 format: a:b:c:d:e:f:g:h[/prefix]. For example: 2001:db7:3f4a:9dd:ca90:ff00:42:8329 You can specify subnets using forward slash (/) notation; for example: 60.63.10.0/24. An example of an IPv6 subnet is as follows: 2001:db8:a::/64. You can append a route domain to an address using the format %RouteDomainID/Mask. For example, 12.2.0.0%44/16. From the drop-down list, select:
To the right, options are provided to add additional addresses, address ranges, or address lists (+) and to delete addresses, address ranges, or address lists (X). When finished, click Save or Add. |
Port | Ports, port ranges, or port lists. From the drop-down list, select:
To the right, options are provided to add additional ports, port ranges, or port lists (+) and to delete ports, port ranges, or port lists (X). When finished, click Save or Add. |
Action | Click in the column and select one of the following:
When finished, click Save or Add. |
Description | Optional description for the current rule. To add a description, click in the column, enter text, and click Save or Add. |
Protocol | IP protocol to compare against the packet. Select the appropriate protocol from
the drop-down list and click Save or
Add. If you select ICMP or IPv6-ICMP, a gear icon appears. Click the gear icon to display the screen where you can change the Type code combinations for the ICMP and ICMPv6 protocols. The gear icon also appears if you select Other to enter the numeric value of the protocol. The default Type is Any. The default Code is Any.
If the value selected for Type is Any, the selected Code must be Any. If the value selected for Type is Other, the number entered must be in the range of 0 and 255.
If the value selected for Type is Any, the selected Code must be Any. If the value selected for Code is Other, the number entered must be in the range of 0 and 255. |
State | Click in the column and select an option from the drop-down list to specify
whether the rule is enabled, disabled, or scheduled. The field is updated. Click
Save or Add when you are ready to save
your changes. If you select scheduled from the drop-down list, the Select Schedule drop-down list is displayed in the screen. Select a schedule and click OK. If you have assigned a schedule, then a gear icon appears to the right of the State setting in the State column. To make changes to the State setting, click the gear icon to invoke the Select Schedule popup screen. If you have no pre-defined schedules, you cannot assign the scheduled state to the rule. |
Log | Click in the column and select an option from the drop-down list to specify
whether or not the firewall software should write a log entry for any packets that
match this rule. From the drop-down list, select true (log an
entry) or false (do not log an entry). When finished, click
Save or Add. To set or edit this setting, the discovered device must be at version 11.3 HF6 or later. The setting is not editable earlier than version 11.3 HF6. When a new rule is added to a firewall through the BIG-IQ Security GUI, editing is enabled for the Log setting even for devices with versions earlier than 11.3 HF6. |