
What’s New in PAN-OS 6.0
© 2014 Palo Alto Networks (PAN-OS 6.0) Page 4
Dynamic Address Groups—Allows you to dynamically update the network address of an object referenced in policy.
Unlike a static address group where you specify the network address of a host, the members of a dynamic address
group are populated using the match criteria that you define. The match criteria uses logical “and” or “or” operators;
each host that you want to add to the dynamic address group must contain the tag that is defined in the match criteria.
Tags can be defined directly on the firewall or on Panorama or they can be dynamically defined using the XML API and
registered with the firewall.
When an IP address and the corresponding tag (one or more) are registered, each dynamic group evaluates the tags
and updates the list of members in its group. This capability allows you to add/ remove/update the members of a group
without making any changes on the firewall; a commit is not required for policy to take effect when you provision new
hosts or decommission existing hosts on your network. The dynamic address group will use the tags to populate its
members. All matching tags—both static and dynamic—are evaluated to populate the group. The difference between
static and dynamic tags is that statically added tags are part of the configuration on the firewall, and dynamically added
tags are part of the runtime configuration.
VM-Series on Citrix SDX—The VM-Series firewall is now supported on the Citrix SDX hardware platform running Citrix
XenServer. Deploying the VM- Series firewall (one or more instances) on the SDX server provides the ability to
consolidate the NetScaler VPX and the VM-Series firewall on the same physical platform. This addresses consolidated
application delivery controller and security needs for multi-tenant cloud deployments (business units, application owners,
service providers) or Citrix XenApp XenDesktop deployments. Supported Citrix platforms are the 11500 or 17500 Series
running Citrix XenServer version 6.0.2 or later.
VM-Series for VMware NSX—NOTE: The VM-Series for VMware NSX will be available in late Q1 CY2014. The Palo
Alto Networks and VMware joint solution addresses challenges associated with applying network security to software
defined networks. With this new offering, customers will be able to safely enable intra-server virtual machine
communications. NSX, VMware's Networking and Security platform, automates the process of deploying and
provisioning the VM-Series firewall as a service (also called Security Virtual Machine) on ESXi servers. VM to VM traffic
is automatically steered to the VM-Series without requiring any manual virtual network configuration. VM context is also
shared between NSX and Panorama, to keep track of virtual machine provisioning and changes.
Mware/VM-Series Integration Components and Requirements
VMware NSX
VMware vCenter 5.5.0
VMware NSX Manager 6.0
VMware ESXI vSphere 5.5
VM-Series
VM-Series for VMware NSX (model available in late Q1 CY2014) in
PAN-OS/Panorama 6.0
Minimum system requirements
Two vCPUs. One will be used for the management plane
and one
for the dataplane. You can add up to eight additional
vCPUs for the
dataplane in the following increments: 2, 4, or 8
vCPUs.
5GB of memory. Any additional memory will be used by the
management plane only.
40GB of virtual disk space
GlobalProtect Features
Agent Deployment Customization—All GlobalProtect agent customization settings can now be set in the Windows
Registry allowing you to deploy GlobalProtect agent settings to client systems prior to their first connection to the
GlobalProtect portal. For Windows clients, this also enables simplified deployment via group policy, as well as the option
to automatically deploy the settings in the Windows Installer. Additional configuration options include:
o Show GlobalProtect icon—Disabling this option makes GlobalProtect invisible to the end user by
removing the icon from the system tray and preventing the user from having any interaction with the
GlobalProtect agent user interface.
o Allow user to change portal address—Disabling this option prevents users from manually
changing the portal address pushed to the client in the portal configuration file.
o Allow user to continue if portal server certificate is invalid—Disabling this option prevents
users from continuing if there is a warning screen that might indicate a man-in-the-middle (MITM)
attack.
Comentarios a estos manuales