>
    Use Dynamic Address Groups in Policy (PAN-OS & Panorama)
    Focus
    Download PDF
    Focus
    1. Home
    2. Network Security
    3. Network Security: Security Policy
    4. Policy Objects
    5. Policy Object: Address Groups
    6. Use Dynamic Address Groups in Policy (PAN-OS & Panorama)
    Download PDF
    Network Security

    Use Dynamic Address Groups in Policy (PAN-OS & Panorama)

    Table of Contents

    Use Dynamic Address Groups in Policy (PAN-OS & Panorama)

    Create security rules that automatically adapts to changes.
    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 data center 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-5400 Series (excepting the PA-5450), PA-5200 Series, VM-7000 SMC-B Series500,000
    VM-500, VM-700300,000
    PA-3430, PA-3440, PA-3200 Series, VM-300200,000
    PA-3410, PA-3420
    150,000
    PA-7000 Series, PA-5450, PA-450, PA-460
    100,000
    PA-440
    50,000
    PA-850, VM-100
    2,500
    PA-820, PA-410, 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 toward 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 ensures that the security rules are enforced on these new virtual machines too.
    1. Enable VM Source Monitoring.
      See Enable VM Monitoring to Track Changes on the Virtual Network.
    2. Create Dynamic Address Groups on the firewall.
      View the tutorial to see a big picture view of the feature.
      1. Log in to the web interface of the firewall.
      2. Select ObjectAddress Groups.
      3. Click Add and enter a Name and a Description for the address group.
      4. Select Type as Dynamic.
      5. Define the match criteria. You can select dynamic and static tags as the match criteria to populate the members of the group. Click Add Match Criteria, and select the And or Or operator and select the attributes that you would like to filter for or match against, then click OK. Negation isn’t supported.
      6. Click Commit.
    3. The match criteria for each Dynamic Address Group in this example is as follows:
      ftp_server: matches on the guest operating system “Linux 64-bit” and annotated as “ftp” ('guestos.Ubuntu Linux 64-bit' and 'annotation.ftp').
      web-servers: matches on two criteria—the tag black or if the guest operating system is Linux 64-bit and the name of the server us Web_server_Corp. ('guestos.Ubuntu Linux 64-bit' and 'vmname.WebServer_Corp' or 'black')
    4. Use Dynamic Address Groups in policy.
      View the tutorial.
      1. Select PoliciesSecurity.
      2. Click Add and enter a Name and a Description for the policy.
      3. Add the Source Zone to specify the zone from which the traffic originates.
      4. Add the Destination Zone at which the traffic is terminating.
      5. For the Destination Address, select the Dynamic Address Group you just created.
      6. Specify the action— Allow or Deny—for the traffic, and optionally attach the default security profiles to the rule.
      7. Repeats steps 1 through 6 to create another security rule.
      8. Click Commit.
    5. This example shows how to create two policies: one for all access to FTP servers and the other for access to web servers.
    6. Validate that the members of the Dynamic Address Group are populated on the firewall.
      1. Select PoliciesSecurity, and select the rule.
      2. Select the drop-down arrow next to the address group link, and select Value. You can also verify that the match criteria is accurate.
      3. Click the more link and verify that the list of registered IP addresses is displayed.
        Policy will be enforced for all IP addresses that belong to this address group, and are displayed here.
      If you want to delete all registered IP addresses, use the CLI command debug object registered-ip clear all and then reboot the firewall after clearing the tags.

    © 2024 Palo Alto Networks, Inc. All rights reserved.