Dynamic address groups are used in policy.
They allow you to create policy that automatically adapts to changes—adds,
moves, or deletions of servers. It also enables the flexibility
to apply different rules to the same server based on
tags that
define its role on the network, the operating system, or the different
kinds of traffic it processes.
A dynamic address group uses
tags as a filtering criteria to determine its members. The filter
uses logical
and and
or operators. All
IP addresses or address groups that match the filtering criteria
become members of the dynamic address group. Tags can be defined
statically on the firewall and/or registered (dynamically) to the
firewall. The difference between static and dynamic tags is that
static tags are part of the configuration on the firewall, and dynamic
tags are part of the runtime configuration. This implies that a
commit is not required to update dynamic tags; the tags must however
be used by Dynamic Address Groups that are referenced in policy,
and the policy must be committed on the firewall.
To dynamically
register tags, you can use the XML API or the VM Monitoring agent
on the firewall or on the User-ID agent. Each tag is a metadata
element or attribute-value pair that is registered on the firewall
or Panorama. For example, IP1 {tag1, tag2,.....tag32}, where the
IP address and the associated tags are maintained as a list; each
registered IP address can have up to 32 tags such as the operating
system, the datacenter or the virtual switch to which it belongs.
After receiving the API call, the firewall registers the IP address
and associated tags, and automatically updates the membership information
for the dynamic address group(s).
The maximum number of IP
addresses that can be registered for each model is different. Use
the following table for specifics on your model:
Model | Maximum number of
dynamically registered IP addresses |
M-Series and Panorama Virtual Appliances | 500,000 |
PA-5200 Series, VM-7000 SMC-B Series | 500,000 |
VM-500, VM-700 | 300,000 |
PA-3200 Series, VM-300 | 200,000 |
PA-820, PA-220, VM-50 | 1,000 |
An IP set, such as an IP range or subnet,
is considered as a single registered IP address when counted towards
the maximum number of registered IP addresses supported by each
firewall model.
The following example shows how dynamic
address groups can simplify network security enforcement. The example
workflow shows how to:
Enable the VM Monitoring agent
on the firewall, to monitor the VMware ESX(i) host or vCenter Server and
register VM IP addresses and the associated tags.
Create dynamic address groups and define the tags to filter.
In this example, two address groups are created. One that only filters
for dynamic tags and another that filters for both static and dynamic
tags to populate the members of the group.
Validate that the members of the dynamic address group are
populated on the firewall.
Use dynamic address groups in policy. This example uses two
different security policies:
A security policy for
all Linux servers that are deployed as FTP servers; this rule matches
on dynamically registered tags.
A security policy for all Linux servers that are deployed
as web servers; this rule matches on a dynamic address group that
uses static and dynamic tags.
Validate that the members of the dynamic address groups are
updated as new FTP or web servers are deployed. This ensure that
the security rules are enforced on these new virtual machines too.