Migrate to Application-Based Policy Using Policy Optimizer
Convert legacy port-based Security policy rules to application-based rules to gain visibility into and control over applications.
After using Expedition to migrate a like-for-like configuration to a PAN-OS appliance, the next phase is using Policy Optimizer to simplify the migration to App-ID based Security policy rules. Policy Optimizer makes the conversion from legacy port-based rules much easier because it automates presenting application information for each rule with the context you need to understand the information and create intelligent application-based rules in a single view. Policy Optimizer:
- Learns and remembers all applications seen in traffic for each rule automatically, which eliminates the need to comb through and analyze reams of log data. Even if logs roll over, Policy Optimizer retains the application information, so you can be confident you’re seeing all of the applications on a rule.
- Enables you to safely migrate to App-ID without risking application availability.
- Is native to and supported on PAN-OS appliances, so you don’t have to move configurations and data between the appliance and a non-native tool.
- Runs on Panorama appliances as well as on individual next-generation firewalls. If you manage your next-generation firewalls running PAN-OS 8.1 with Panorama, you only have to upgrade Panorama (and any Log Collectors connected to the managed firewalls) to PAN-OS 9.0 to use and gain the benefits of Policy Optimizer, so you can qualify and adopt Policy Optimizer faster than if you had to qualify all your firewalls.Cortex Data Lake supports Policy Optimizer on Panorama devices that run PAN-OS 10.0.4 or later with Cloud Services plugin 2.0 or later.
These capabilities result in an easy-to-use tool that saves time and prevents errors when converting port-based rules to App-ID based rules. Policy Optimizer provides several methods of converting rules:
- Create Cloned Rule—Cloning a rule preserves the original port-based rule and places the new App-ID based rule above the cloned rule. You can clone multiple App-ID based rules from one port-based rule. For example, you can clone multiple App-ID rules based on application subcategories from a general web-browsing rule to group applications that require similar access and threat treatment instead of trying to control all web access for all users in all places in one general, unsecure rule.There’s no risk to application availability because the port-based rule below the cloned rule acts like a safety net. If the cloned (App-ID) based rule doesn’t match all the applications you need to allow, you’ll see those applications hit the port-based rule below the cloned rule and you can make adjustments. You can remove the port-based rule when no traffic you want to allow matches the port-based rule for a reasonable period of time, completing the conversion of that rule to an App-ID based rule.
- Add to This Rule—Adding applications to the rule replaces the port-based rule with an App-ID based rule, which removes the port-based rule from the rulebase and doesn’t provide the safety net that cloning provides. UseAdd to This Ruleonly when you’re sure you know all the applications you want the rule to control. Rules that have seen only a few applications and for which you’re confident you know the required applications for your business are candidates forAdd to This Rule. It’s safest to clone rules that have seen many applications and rules that may see more applications you need to allow. If you miss adding an application to a rule, you lose availability to that application unless another rule allows it, while cloning the rule retains the port-based rule as a safety net.
- Add to Existing Rule—Adding applications to an existing rule does not replace the original port-based rule, which remains in the rulebase.Add to Existing Ruleenables you to select any previously configured rule and add applications to it.When you add applications to an existing application-based rule, the firewall removes those applications from the port-based rule and adds them to the selected application-based rule. The added applications use the same Source, Destination, Service, etc., as the other applications on the application-based rule.When you add applications to another existing port-based rule, the firewall removes those applications from the original port-based rule and adds them to the other port-based rule. This converts the other port-based rule to an application-based rule that controls only the applications you added to the rule. If you convert part of a port-based rule this way, go to the rule and change the Service to application-default to prevent the applications from using non-standard ports (also, the Service configured on the rule may not match the application).
- Match Usage—Matching a port-based rule’s usage replaces the port-based rule with an App-ID based rule that contains all of the applications seen on that rule. UseMatch Usageonly when the rule has seen a small number of well-known applications that have legitimate business purposes. A good example is TCP port 22, which should allow only SSH traffic. If SSH is the only application seen on a port-based rule for port 22, you can safelyMatch Usageand convert the rule to an App-ID rule.
Create Cloned Rule,
Add to This Rule, or
Add to Existing Rule, you must select at least one application from
Applications used only for quarterly or yearly events may not appear in the application information if the history isn’t long enough to capture their latest activity. Be aware of these types of applications when you convert rules.
When you convert a port-based rule to an application-based rule, Policy Optimizer makes no other changes to the rule aside from converting services to App-IDs. In most cases, after you convert a rule, you should change the
application-defaultso that only the applications which legitimately use the port can access the port and to prevent evasive applications from gaining network access by using a non-standard port.
If business needs require allowing applications such as internal custom applications on non-standard ports between particular clients and servers, restrict the exception to only the required applications, sources, and destinations. Consider rewriting custom applications to use application-default ports.
Before you use Policy Optimizer to convert port-based rules to App-ID based rules:
- Run the PAN-OS appliance in your production network for about a week before you start converting rules to App-ID so the appliance can begin to learn and categorize the applications on the network. You can convert some simple rules quickly (for example, a port 22 rule should only allow SSH traffic and is easy to convert), while you need to allow the firewall to gather application data from traffic for a longer period of time for other rules, such as your internet access (port 80/433) rule.
- Set realistic goals. Think about what you want the end result to look like. When you reach the goal, run the BPA again to confirm that you reached the goal, and then reevaluate whether you can go farther and make your network even safer. With Policy Optimizer, you don’t sacrifice availability for security, you just improve security.
Convert rules in phases. You can convert some simple port-based rules that allow well-known applications to App-ID based rules after the PAN-OS appliance has as little as one week of logs (Policy Optimizer discovers the applications seen on rules by reading logs). For other rules that see many applications, such as a general web access rule, wait at least 30 days to gather application information.
Professional Services has a wealth of migration experience. You can engage the Professional Services team to help you move a configuration from your legacy appliances to Palo Alto Networks next-generation firewalls and Panorama appliances.
Recommended For You
Recommended videos not found.