Identify Security Policy Rules with Unused Applications
Policy Optimizer finds Security policy rules that specify applications not seen on your network so you can remove the unused apps to reduce the attack surface.
If you have application-based Security policy rules that allow a large number of applications, you can remove unused applications (applications never seen on the rules) from those rules to tighten them so that they only allow applications actually seen in the rule’s traffic. Identifying and removing unused applications from Security policy rules is a best practice that strengthens your security posture by reducing the attack surface.
- Identify Security policy rules that have unused
applications.PoliciesSecurityPolicy OptimizerUnused Apps displays all application-based rules configured with applications that aren’t in use on the network—that is, rules configured to allow more applications than the number of applications actually seen on those rules.The number of Apps Allowed and Apps Seen are updated approximately every hour, so if you configure applications on a rule and don’t see as many Apps Allowed as you expect, check again after about an hour. Depending on the firewall’s load, it may take longer than one hour for these fields to update.
- Prioritize which rules with unused applications to modify
first.PoliciesSecurityPolicy OptimizerUnused Apps enables you to sort rules without affecting their order in the rulebase and provides other information that helps you prioritize rules to clean up based on your business goals and risk tolerance.
You can also click Traffic (Bytes, 30 days) to sort by the amount of traffic a rule has seen over the last 30 days. Use this information to prioritize which rules to modify first. For example, you can prioritize rules with the largest difference between Apps Allowed and Apps Seen and that also have the most Days with No New Apps, because those rules have the greatest number of unused applications and are the most mature.
- The difference between Apps Allowed (the number of applications the whitelist rule allows) and Apps Seen (the number of whitelisted applications actually seen on the rule) shows how many applications are configured on each rule but not actually seen on the rule, which indicates to what extent the rule is over-provisioned. Click Apps Allowed to sort by the number of applications allowed in a rule and click Apps Seen to sort by the number of applications actually seen on a rule.
- Days with No New Apps (click to sort) shows you the number of days since the last time a new application hit the rule. This indicates how likely it is that the rule is mature and won’t see any applications that haven’t already been seen. The longer the Days with No New Apps, the less likely that new applications will hit the rule and the more likely that you know all the applications the rule allows.
- Created and Modified dates also help determine whether a rule has matured enough to understand whether applications not seen on the rule may be seen at a later date or if the rule has seen all the applications expected to hit the rule. The longer the time since a rule was Modified, the more likely the rule is mature. (If Created and Modified are the same, the rule hasn’t been modified.)
- Hit Count—Displays rules with the most matches over a selected time frame. You can exclude rules for which you reset the hit counter and specify the exclusion time period in days. Excluding rules with recently reset hit counters prevents misconceptions about rules that show fewer hits than you expect because you didn’t know the counter was reset.
- Review the Apps Seen on the rule.On Unused Apps, click Compare or the number in the Apps Seen column to open Applications & Usage, which shows the applications configured on the rule (Apps on Rule) and the Apps Seen on the rule.
Pink-shaded applications configured on the rule may be unused applications, although pink-shaded container apps may have individual applications in use. Consider removing pink-shaded applications to reduce the attack surface. Take into account periodically used applications, such as for quarterly or annual events, which may look unused if you don’t examine a long enough time frame. Timeframe allows you to select the time frame for the Apps Seen on the rule. Select Anytime to see every application seen over the life of the rule. Depending on the Created or Modified date in the No App Specified dialog and the time between periodic events, the rule may not have been on the firewall long enough to see all periodically used applications.
- The number next to Apps Seen (12 in this example) is the number of applications actually seen on the rule. Keep in mind that it takes at least one hour to update Apps Seen.
- The number next to Apps on Rule (32 in this example) is how many applications are configured on the rule, which is calculated by counting each application in a container app (but not the container app itself—if you configure a container app on the rule, the rule allows the container app’s individual applications). However, the Applications list shows only the applications manually configured on the rule, so when you configure a container app on a rule, Applications only shows the container app, not the individual applications in the container (unless you also manually configure the individual applications on the rule). For this reason, the number of Apps on Rule may not be the same as the number of applications in the Applications list.
- The pink-shaded Apps on Rule are either:
- Applications configured on the rule but no matching traffic has been seen on the rule, so the application hasn’t been seen on the rule.
- Container apps, even when their individual applications have been seen on the rule. For example, if a rule configured with the container app active-directory sees traffic from the active-directory-base individual application, the container app is shaded pink even though one of the container app’s individual applications was seen on the rule.
- Click the number next to Apps on Rule for a pop-up dialog that shows all of the individual applications on the rule. Because Apps on Rule lists container apps but not the individual applications in those container apps (unless the individual applications were manually configured on the rule), the pop-up dialog may show a different number of applications than the Applications list under Apps on Rule.In the following example, 7 applications have been seen on the rule and the rule allows 50 Apps on Rule. The linked in container app is configured on the rule and the rule sees traffic from the individual applications linkedin-apps, linkedin-base, linkedin-editing, linkedin-intro, linkedin-mail, and linkedin-posting. Apps on Rule shades the container app linkedin (which is configured on the rule) pink. It does not show the individual applications, which are not specifically configured on the rule. When you click the Apps on Rule number, the pop-up dialog expands the container app to display the individual applications, but not the container app itself.You cannot add or delete applications from the pop-up dialog.
- The unshaded Apps on Rule are applications that have been seen on the rule.
- Remove unused applications from the rule.Delete (or Add) applications in Apps on Rule to remove (or add) applications manually, or Match Usage to add the Apps Seen on the rule and delete applications for which no matching traffic has been seen on the rule with one click.To remove applications from the rule manually, select the pink-shaded applications from Apps on Rule and Delete them. Ensure that none of the pink-shaded applications are required for periodic events before you remove them from the rule. (You can still add or delete applications on the Security policy rule’s Application tab, but unused applications aren’t shaded pink.)Match Usage moves the Apps Seen on the rule to Apps on Rule and removes all unused (pink-shaded) applications from the rule.
- Commit the configuration.
- Monitor updated rules and listen to user feedback to
ensure that updated rules allow the applications you want to allow
and don’t inadvertently block periodically used applications.The number of Apps Allowed and Apps Seen are updated approximately every hour. After you remove all of the unused applications from a rule, the rule remains listed in PoliciesSecurityPolicy OptimzerUnused Apps until the firewall updates the display. When the firewall updates the display and the number of Apps Allowed is the same as the number of Apps Seen, the rule no longer displays in the Unused Apps screen. However, depending on the firewall’s load, it may take longer than one hour for these fields to update.
Applications and Usage Policies > Security > Policy Optimizer > No App Specified > Compare (or click the number in Apps Seen) Policies > Security ...
Migrate Port-Based to App-ID Based Security Policy Rules
Policy Optimizer converts port-based Security policy rules to app-based rules without compromising app availability to safely enable applications. ...
Sorting and Filtering Security Policy Rules
Use application usage information to prioritize which rules to migrate from port-based to app-based rules or to clean up (remove unused apps) first. ...
Convert Simple Rules with Few Well-Known Applications
Convert legacy port-based security policy rules that control a small number of well-known applications after one week of monitoring production traffic. ...
Rule Cloning Migration Use Case: Web Browsing and SSL Traffic
Example of migrating port-based Security policy rules for web browsing and SSL traffic to app-based rules without affecting application availability. ...
Convert the Web Access Rule Using Subcategories
Convert legacy port-based HTTP/HTTPS (port 80/443) internet access rules to application-based rules. ...
Security Policy Rule Usage
Security Policy Optimizer Policies > Security > Policy Optimizer Policies Security Policy Optimizer displays: No App Specified —Rules that have the application set to any ...