index int64 0 4.08k | text stringlengths 34 4.9k ⌀ | url stringclasses 38
values |
|---|---|---|
891 | App-ID
STEP 2 | Select the Policy Application Usage check box to enable the feature and deselect the check
box to disable the feature.
PAN-OS® Administrator’s Guide Version 10.2 892 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
892 | App-ID
App-ID Cloud Engine
The App-ID Cloud Engine (ACE) is a service that enables the firewall or Panorama to download
App-IDs from the cloud for applications that do not have specific predefined App-IDs from the
Palo Alto Networks content update team. ACE provides specific App-IDs for applications that the
firewall otherwise identifies as ssl or web-browsing traffic. Use ACE App-IDs in Security policy
rules to gain visibility into cloud applications and control them. Use Policy Optimizer to add and
manage applications in Security policy. You cannot use ACE App-IDs in any other types of policy
rules. ACE:
• Vastly increases the number of known App-IDs to identify and control more cloud applications,
and as ACE defines new App-IDs for applications, the ACE App-IDs become available on the
firewall.
• Speeds up the availability and delivery of new App-IDs to the firewall.
• Speeds up and can automate the addition of applications to Security policy through the use of
Application Filters in Security policy rules.
• Dramatically increases visibility into applications that previously were identified as ssl or webbrowsing.
ACE requires a SaaS Security Inline subscription. Each appliance that uses ACE must
have a valid device certificate installed.
All hardware platforms that support PAN-OS 10.1 or later support ACE and all appliances
on which you want to use ACE require PAN-OS 10.1 or later. Panorama cannot push and
commit ACE-based polices or objects to firewalls that don’t have a SaaS Security Inline
license installed or to firewalls that run an earlier version of PAN-OS than 10.1.
ACE is supported in the US, APAC, and EU GCP regions. The region is selected
automatically based on your Strata Logging Service region.
Verify that the firewall uses the correct Content Cloud FQDN (Device > Setup > ContentID > Content Cloud Setting) for your region and change the FQDN if necessary:
• US—hawkeye.services-edge.paloaltonetworks.com
• EU—eu.hawkeye.services-edge.paloaltonetworks.com
• APAC—apac.hawkeye.services-edge.paloaltonetworks.com
ACE data, including traffic payloads, is sent to the servers in the selected region. If you
specify a Content Cloud FQDN that is outside of your region (for example, if you are in the
EU region but you specify the APAC region FQDN), you may violate your country’s or your
organization’s privacy and legal regulations.
Predefined content-delivered App-ID provides new applications once per month and you need
to analyze the new App-IDs before you install them to understand changes that they may make
to Security policy rules. The monthly cadence and need for analysis slows down the adoption of
new App-IDs in policy. Although Palo Alto Networks will continue to provide new App-IDs via
monthly content updates that you need to review, ACE improves the adoption of new App-IDs
by providing on-demand App-IDs for applications initially identified as any of the following two
types:
PAN-OS® Administrator’s Guide Version 10.2 893 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
893 | App-ID
• ssl—Encrypted SSL traffic is by far the most common type of network traffic, with most experts
claiming that it exceeds 90% of total traffic. If you don’t or can’t decrypt that traffic, the
firewall often can only identify it as ssl instead of as the actual underlying application.
• web-browsing—The firewall can’t specifically identify some unencrypted (web-browsing)
traffic because the monthly content-delivered App-ID updates can’t keep up with all the new
applications being developed every day.
ACE provides specific identification of these applications, which enables you to understand them
and control them appropriately in Security policy.
ACE App-IDs do not identify other types of public applications and do not identify private
and custom applications. The ACE App-ID catalog does not contain predefined, contentprovided App-IDs. Content-provided App-IDs still arrive monthly in content updates.
When the firewall encounters ssl or web-browsing traffic, the firewall sends the payload to
ACE for analysis. If it matches an App-ID in the ACE database, ACE returns the App-ID to the
requesting firewall. If ACE has no matching App-ID for the traffic, ACE sends the payload to the
Machine Learning (ML) engine. The ML engine analyzes the payload and develops the new AppID in conjunction with the human content team. When development finishes, the ML engine
uploads new App-ID to the ACE database, and the requesting firewall (and any other firewalls) can
download the App-ID and use it in Security policy.
Because it can take several minutes to retrieve a known application from ACE and longer
if a new App-ID must be developed, cloud application detection is not inline on the
firewall. The firewall does not wait for a verdict to process the application traffic. The
firewall processes the traffic as ssl or web-browsing until it receives an App-ID from ACE
and you use it in Security policy.
If you downgrade a firewall or Panorama after ACE has been enabled and ACE cloud AppIDs are still in use in Security policy rules or Application Groups, the downgrade fails. The
fail reason lists the objects that you need to remove from the configuration in order to
downgrade. Remove those objects from the configuration and Commit the configuration,
and then the downgrade will succeed.
• Prepare to Deploy App-ID Cloud Engine
• Enable or Disable the App-ID Cloud Engine
• App-ID Cloud Engine Processing and Policy Usage
• New App Viewer (Policy Optimizer)
• Add Apps to an Application Filter with Policy Optimizer
• Add Apps to an Application Group with Policy Optimizer
• Add Apps Directly to a Rule with Policy Optimizer
• Replace an RMA Firewall (ACE)
• Impact of License Expiration or Disabling ACE
• Commit Failure Due to Cloud Content Rollback
• Troubleshoot App-ID Cloud Engine
PAN-OS® Administrator’s Guide Version 10.2 894 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
894 | App-ID
Prepare to Deploy App-ID Cloud Engine
There are several prerequisite onboarding tasks to do before the firewall can use the App-ID
Cloud Engine (ACE). You can deploy ACE on standalone firewalls or use Panorama to deploy ACE
on managed firewalls.
Before a firewall can use ACE to provide specific App-IDs for traffic previously identified as ssl or
web-browsing traffic, the PAN-OS administrator and the SaaS Security administrator must work
together to:
• Install a valid device certificate on each appliance that will use ACE, including Panorama
appliances that manage ACE firewalls. (PAN-OS administrator.)
• Activate SaaS Security Inline on each firewall that will use ACE. Panorama doesn’t require a
license. (SaaS Security administrator.)
• Configure a service route for communication between the firewall and ACE. (PAN-OS
administrator.)
• Enable ACE on Panorama appliances which manage firewalls that will use ACE. (PAN-OS
administrator.)
On firewalls, ACE is enabled by default after activating SaaS Security Inline.
• Create Security policy rule that allows ACE traffic. (PAN-OS administrator.)
• Configure Log Forwarding from the firewall to the Strata Logging Service. (PAN-OS
administrator.)
At the appropriate step in the following procedure, the PAN-OS administrator should
notify the SaaS Security administrator that the deployment is ready for SaaS Security
Inline activation. After activating SaaS Security Inline, the SaaS Security Inline
administrator should notify the PAN-OS administrator that the deployment is ready to
complete on the PAN-OS devices. Communication between the administrators is essential
to achieving a smooth deployment.
Requirements:
• Standalone firewalls, Panorama appliances, and managed firewalls must run PAN-OS 10.2 or
later.
• All ACE firewalls must have purchased a SaaS Security Inline license. Panorama does not
require a license to manage ACE firewalls or push ACE configurations to managed firewalls.
PAN-OS® Administrator’s Guide Version 10.2 895 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
895 | App-ID
• All ACE appliances must be able to connect to the US, APAC, or EU GCP region, depending on
your location (the region is selected automatically based on your Strata Logging Service region).
Verify that the firewall uses the correct Content Cloud FQDN (Device > Setup > Content-ID >
Content Cloud Setting) for your region and change the FQDN if necessary:
• US—hawkeye.services-edge.paloaltonetworks.com
• EU—eu.hawkeye.services-edge.paloaltonetworks.com
• APAC—apac.hawkeye.services-edge.paloaltonetworks.com
ACE data, including traffic payloads, is sent to the servers in the selected region. If you specify
a Content Cloud FQDN that is outside of your region (for example, if you are in the EU region
but you specify the APAC region FQDN), you may violate your country’s or your organization’s
privacy and legal regulations.
The PAN-OS administrator completes the first two steps of the procedure and then hands it
off to the SaaS Security Inline administrator for activation (Step 3). After activation, the SaaS
Security Inline administrator hands the rest of the procedure back to the PAN-OS administrator to
complete on the PAN-OS devices.
STEP 1 | Bring the firewall and Panorama (if using) online. (PAN-OS administrator.)
STEP 2 | Install device certificates on Panorama (if you use Panorama) and on individual firewalls so
that they can use cloud services. (PAN-OS administrator.)
• Install a device certificate on Panorama
• Install a device certificate on individual firewalls (if not managed by Panorama)
• Install device certificates on managed firewalls from Panorama
Hand off the next step to the SaaS Security administrator.
STEP 3 | Activate SaaS Security Inline on every firewall that will use ACE. Activation enables ACE on
the firewalls. (SaaS Security administrator.)
Panorama does not require a SaaS Security Inline license to manage firewalls that
use ACE. Only managed firewalls need licenses, which you must retrieve manually as
shown in the next step.
Hand off the rest of the steps to the PAN-OS administrator.
STEP 4 | Retrieve the SaaS Security Inline license on each firewall—Panorama doesn’t need a license—
and verify that it is activated. (PAN-OS administrator.)
The SaaS Security administrator’s activation sets up the licenses for the firewall, so you don’t
have to go to the Customer Support Portal or obtain Auth Codes.
1. Go to Device > Licenses > License Management and select Retrieve license keys from
license server to retrieve the license.
2. Check Device > Licenses to ensure that the SaaS Security Inline license is active.
PAN-OS® Administrator’s Guide Version 10.2 896 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
896 | App-ID
STEP 5 | (Required when the firewall is deployed with an explicit proxy server) Configure the proxy
server used to access the servers that facilitate requests generated by all configured inline
cloud analysis features. A single proxy server can be specified and applies to all Palo Alto
Networks update services, including all configured inline cloud and logging services.
1. (PAN-OS 10.2.11 and later) Configure the proxy server through the firewall CLI.
1. Access the firewall CLI.
2. Configure the base proxy server settings using the following CLI commands:
set deviceconfig system secure-proxy-server <FQDN_or_IP>
set deviceconfig system secure-proxy-port <1-65535>
set deviceconfig system secure-proxy-user <value>
set deviceconfig system secure-proxy-password <value>
The proxy server password must contain a minimum of seven characters.
3. Enable the proxy server to send requests to the inline cloud service servers using the
following CLI command:
debug dataplane mica set inline-cloud-proxy enable
4. View the current operational status of proxy support for inline cloud services using
the following CLI command:
debug dataplane mica show inline-cloud-proxy
For example:
debug dataplane mica show inline-cloud-proxy
Proxy for Advanced Services is Disabled
STEP 6 | Configure a data services (dataplane) service route so that the firewall can communicate with
the App-ID Cloud Engine. (PAN-OS administrator.)
You can push this configuration to managed firewalls from Panorama. Both Panorama
and the managed firewalls must run PAN-OS 10.2 or later.
By default, the firewall uses the management interface as the source interface for the data
services service route, but it is recommended that you configure a dataplane interface that has
connectivity to cloud services as the Source Interface and Source Address for data services, as
shown later in this step.
The issue on firewalls is that if an explicit proxy is configured on the management interface
and you use it for the data services service route, then the management interface can only
connect to the Knowledge Cloud Service (KCS), which manages the cloud application and
signatures. When an explicit proxy is configured on the management interface, it cannot
connect to the Detection Cloud Service (DCS), which checks the application payload against
existing ACE App-IDs and provides verdicts. KCS and DCS are services in the ACE cloud. If the
PAN-OS® Administrator’s Guide Version 10.2 897 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
897 | App-ID
management interface has an explicit proxy configured, you can’t use it for the data services
service route for ACE because it can’t connect to all of the services. In this case, you must use
a dataplane interface on the firewall to connect to the data services.
Panorama uses the management port by default to connect to the KCS and does not
connect to the DCS.
To configure the service route on a data plane interface instead of using the default
management interface:
1. Select Device > Setup > Services then in Service Features, select Service Route
Configuration.
2. Customize a service route.
3. Select the IPv4 protocol.
4. Click Data Services in the Service column to open the Service Route Source dialog box.
5. Select a Source Interface and Source Address (these cannot be the management
interface).
The source interface must have internet connectivity. The best practice is to use a
dataplane interface that has connectivity to cloud services. See Configure Interfaces and
Create an Address Object for more information about creating source interfaces and
addresses.
6. Click OK to set the source interface and address.
7. Click OK to set the Service Route Configuration.
8. Select Policies > Security and add a Security policy rule that allows traffic from the
source interface you specified earlier in this procedure to the FQDN addresses for the
KCS and DCS services, which are kcs.ace.tpcloud.paloaltonetworks (KCS
service for all regions) and hawkeye.services-edge.paloaltonetworks.com (US
region DCS service), eu.hawkeye.services-edge.paloaltonetworks.com (EU
region DCS service), or apac.hawkeye.services-edge.paloaltonetworks.com
(APAC region DCS service).
Also add and allow the following two FQDNs in a new or existing Security policy rule:
ocsp.paloaltonetworks.com and crl.paloaltonetworks.com for certificate
verification.
Finally, add or modify a Security policy rule to allow ACE traffic by allowing the following
three applications: paloalto-ace, paloalto-ace-kcs, and paloalto-dlpservice.
STEP 7 | Make sure that hawkeye.services-edge.paloaltonetworks.com and
kcs.ace.tpcloud.paloaltonetworks are reachable on firewalls and that
kcs.ace.tpcloud.paloaltonetworks is reachable on Panorama devices. (PAN-OS administrator.)
Run the operational command admin@fw1> show cloud-appid connection-tocloud. The output informs you whether the connection is working and if the license is
installed.
PAN-OS® Administrator’s Guide Version 10.2 898 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
898 | App-ID
STEP 8 | (Panorama only) Enable ACE on any Panorama appliance that manages ACE-enabled
firewalls. (PAN-OS administrator.)
ACE is disabled by default on Panorama.
If you push ACE configurations to managed groups that do not have ACE-enabled
firewalls (some or all firewalls in the group do not have ACE enabled), the push fails.
1. Navigate to Panorama > Setup > ACE > Settings.
2. Click edit ( ) and then de-select Disable App-ID Cloud Engine.
3. Click OK.
4. The Enable App-ID Cloud Engine dialog appears.
Click Yes to enable ACE.
5. Commit the change.
STEP 9 | Wait for the App-ID catalog to download. (PAN-OS administrator.)
There are fewer than four thousand content-provided App-IDs. After you download the
ACE catalog, you see many thousands more applications on the firewall and can confirm by
checking Objects > Applications or by using the operational CLI command show cloudappid cloud-app-data application all to see the new App-IDs.
STEP 10 | (Panorama only) Push the desired configuration to the managed firewall(s). (PAN-OS
administrator.)
STEP 11 | Configure Log Forwarding to Strata Logging Service (Strata Logging Service) and enable
Log Forwarding with the correct Log Forwarding profile in Security policy rules. (PAN-OS
administrator.)
A SaaS Security Inline connection to Strata Logging Service is required for SaaS
visibility and to support SaaS App-ID Policy Recommendation. At a minimum, you
must forward Traffic logs and URL logs to Strata Logging Service for SaaS Security
Inline to work properly.
Enable or Disable the App-ID Cloud Engine
The App-ID Cloud Engine (ACE) is disabled by default on Panorama and enabled by default on
firewalls when the SaaS Security Inline license is installed. You must enable ACE on Panorama
appliances that manage ACE-enabled firewalls.
PAN-OS® Administrator’s Guide Version 10.2 899 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
899 | App-ID
To enable or disable ACE:
STEP 1 | Navigate to Device > Setup > ACE > Settings on the firewall or Panorama > Setup > ACE >
Settings on Panorama.
STEP 2 | Click edit ( ) and then either de-select Disable App-ID Cloud Engine to enable ACE or select
Disable App-ID Cloud Engine to disable ACE.
ACE is disabled by default.
STEP 3 | Click OK.
STEP 4 | (Only if enabling ACE) If you are enabling ACE, the Enable App-ID Cloud Engine dialog
appears.
If the firewall or Panorama-managed firewalls have the SaaS Security Inline license installed,
click Yes to enable ACE.
STEP 5 | Commit the change.
App-ID Cloud Engine Processing and Policy Usage
When the firewall downloads App-ID Cloud Engine (ACE) App-IDs, it’s important to understand
how the firewall handles ACE App-IDs and how the firewall handles ACE App-IDs when there
are also predefined content-based App-IDs for the same applications. The Palo Alto Networks
content team develops predefined content-based App-IDs and updates them with modified
and new App-IDs through application content updates (a valid support contract is required for
updates).
ACE requires a SaaS Security Inline license. Firewalls that don’t support ACE have only predefined
content-based App-IDs. The ACE App-ID catalog doesn’t contain content-based App-IDs.
You can only use ACE App-IDs in Security policy rules. You cannot use ACE App-IDs in
any other type of policy rule.
• When the firewall first connects to ACE, the firewall downloads a catalog of the available ACE
App-IDs and you can use those App-IDs in Security policy. The firewall does not download the
full application signatures, only the catalog. The catalog enables you to specify ACE App-IDs
in Security policy even if the applications have never been seen on the firewall. ACE pushes
catalog updates to firewalls regularly so that firewalls have access to the latest ACE App-IDs.
If an application arrives at the firewall that is identified as ssl or web-browsing and the firewall
doesn’t have its signature, the firewall sends the payload to ACE. If ACE has a matching AppPAN-OS® Administrator’s Guide Version 10.2 900 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
900 | App-ID
ID, then ACE sends the full signature back to the firewall. If the traffic doesn’t match any ACE
signatures, then ACE sends the payload to the Machine Learning (ML) engine. The ML engine
analyzes the payload and develops a new App-ID in conjunction with the human content team.
The ML engine sends the new App-ID to ACE and requesting firewalls can download it and use
it in Security policy.
Because it can take several minutes to retrieve an App-ID from ACE and longer if a
new App-ID must be developed, cloud application detection is not inline on the firewall.
The firewall does not wait for a verdict to process the application traffic. The firewall
processes the traffic as ssl or web-browsing until it receives an App-ID from ACE.
• When a firewall requests an App-ID from ACE, the firewall continues to process the traffic
against the current rulebase until it receives an App-ID from ACE and the App-ID is applied in
Security policy.
• The firewall handles ACE App-IDs differently than it handles App-IDs delivered by content
updates. You don’t have to examine how new ACE App-IDs affect Security policy before they
are installed on the firewall because the firewall handles new ACE App-IDs according to your
existing Security policy. Your existing Security policy rules control new ACE App-IDs until you
explicitly use ACE App-IDs in Security policy. For example:
1. An application is identified only as “ssl” and you have a Security policy rule that allows SSL
traffic, so the ssl rule allows that application.
2. The firewall sees an application identified as ssl and sends the payload to ACE.
3. ACE identifies the actual application. If the application exists in the ACE database, then ACE
sends its App-ID to the firewall. If it’s a new application without an ACE App-ID, then ACE
forwards the payload to the ML Engine. The firewall does not receive the App-ID until the
ML Engine and the human content team assign an App-ID and send it to ACE.
4. The rule that allows ssl traffic still allows the newly-identified application, even though its
App-ID is no longer “ssl”. (However, if you use the new ACE App-ID in Security policy, that
policy controls the traffic. Similarly, traffic previously identified as web-browsing continues
to obey the Security policy rules that control web browsing traffic until you use the ACE
App-IDs in Security policy.)
The exception to this behavior is if another Security policy rule already specifies the AppID given to the traffic by ACE. The Security policy rule with the specific App-ID takes
precedence over the rule with the less specific ssl App-ID. For example, if the firewall
identifies an application as ssl and sends the payload to ACE to obtain the granular App-ID.
ACE returns the App-ID “app-abc”. The firewall already has a Security policy rule that allows
the App-ID “app-abc”, so the application’s traffic now matches that rule.
If the rule that specifies the actual App-ID is a block rule, the application is blocked even
though there is a rule that allows ssl traffic. The rule with the more specific (granular) AppID is the one the firewall acts on.
Until you explicitly add new ACE App-IDs to Security policy rules, the firewall controls them
with the same rules that controlled those applications before they had ACE App-IDs and
were identified as ssl or web-browsing traffic. For example, if the firewall sees an application
identified as web-browsing and then receives an ACE App-ID for the traffic, but you don’t use
that ACE App-ID in a Security policy rule, then the firewall still controls that traffic using the
rule that controls web-browsing traffic—if you block web-browsing traffic, then the traffic is
blocked, and if you allow web-browsing traffic, the traffic is allowed.
PAN-OS® Administrator’s Guide Version 10.2 901 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
901 | App-ID
• The firewall caches some information so that the firewall can avoid repeatedly sending data to
the cloud and requesting verdicts. If the firewall is waiting for a verdict from ACE, the firewall
doesn’t forward the same application data twice.
• On the firewall, a particular container app and its functional applications are either all cloudbased App-IDs or all content-based App-IDs. One App-ID delivery method defines a container
app and all of its functional apps.
• If cloud-based, content-provided, and user-defined custom App-ID names overlap, the order of
precedence is:
1. Custom App-IDs—These App-IDs take precedence over all other App-IDs. If the firewall
attempts to download an ACE application with the same App-ID, the commit fails because
two applications on the same firewall cannot have the same App-ID.
In this case, you can rename the custom application, or if the custom application is the same
application as the ACE application, you can delete the custom application and use the ACE
application.
2. Content-based, predefined App-IDs—These App-IDs take precedence over ACE cloud AppID definitions.
3. ACE cloud App-IDs—Custom and content-based App-IDs take precedence over ACE AppID definitions.
• If an App-ID matches a container app, the firewall downloads the container app’s App-ID and
all of its functional apps. For example, if the firewall retrieves the facebook container app, it
also retrieves facebook-base, facebook-chat, facebook-post, etc.
• When you take any of the following actions to add ACE App-IDs to Security policy rules, the
firewall no longer matches the application traffic to the ssl or web-browsing rule, it matches
the application traffic to the rule that controls the specific App-ID:
• Create Application Filters to automate adding ACE App-IDs to Security policy.
Use Application Filters to automate adding ACE App-IDs to Security policy rules.
When a new App-ID matches an Application Filter, the firewall automatically adds
it to the filter. When you use that Application Filter in a Security policy rule, the
rule controls the application traffic for the new App-IDs that were automatically
added to the filter. Application Filters are your “Easy Button” for securing ACE AppIDs automatically to gain maximum application visibility and control with minimum
effort.
• Add ACE App-IDs to Application Groups.
• Use Policy Optimizer to add ACE App-IDs to a cloned rule or to an existing rule, or to an
existing Application Filter or Application Group. You can use Policy Optimizer to create new
Application Filters and Application Groups directly from within the Policy Optimizer tool.
Use Policy Optimizer’s sorting and filtering tools to prioritize the rules to work on and to
assess how many ACE App-IDs match those rules.
• Add an ACE App-ID directly to a new or existing Security policy rule.
When you add a cloud App-ID to a Security policy rule directly or by using an Application Filter
or an Application Group, that rule controls the application.
PAN-OS® Administrator’s Guide Version 10.2 902 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
902 | App-ID
• When you create Application Filters, exclude ssl and web-browsing from the filters. Together,
ssl and web-browsing match all browser-based cloud applications, so an Application Filter that
includes ssl and web-browsing matches all browser-based cloud applications.
• Active/Passive High Availability:
• The Active firewall syncs the ACE catalog to the passive firewall so that they have identical
catalogs.
• The Passive firewall does not initiate connections to ACE until it becomes the Active
firewall.
• Active/Active High Availability: Each device fetches catalogs and signatures separately, so the
catalogs and signatures are not synced. However, commits fail if the catalog is out-of-sync
on peers and ACE App-IDs are referenced in Security policy rules. If the catalogs of peer HA
firewalls are out-of-sync, wait a few minutes for the updates to reach the devices and become
in-sync again.
• A Panorama commit all/push failure to managed firewalls occurs if:
• Managed firewalls do not have a valid SaaS Security Inline license and therefore do not have
the ACE catalog. In this case, remove the ACE objects from the pushed configuration and
try again.
• The connection between a managed firewall and ACE goes down and the pushed
configuration includes applications that are not in the ACE catalog on the firewall. In this
case, check the firewall connection to the ACE cloud and re-establish the connection if
necessary so that the firewall can update its catalog.
The operational CLI command show cloud-appid connection-to-cloud provides
the cloud connection status and the ACE cloud server URL.
• The ACE catalog on Panorama and the ACE catalog on managed firewalls is out-of-sync,
which results in pushed configurations that include ACE apps that are not in the firewall’s
catalog. If the connection between the firewall and ACE is up, the outdated catalog will
update in the next few minutes automatically and resolve the issue. (Wait five minutes and
try again.)
You can use the CLI command debug cloud-appid cloud-manual-pull
check-cloud-app-data to update the catalog manually.
• Some Security profiles such as the File Blocking, Antivirus, WildFire, and DLP profiles can
specify applications as part of the profile. Only content-provided App-IDs are supported
in Security profiles. ACE App-IDs are not supported in Security profiles. ACE App-IDs are
intended for use in Security policy rules only.
• Because ACE App-IDs are supported only for Security policy, they are not supported in
Application Override, Policy-Based Forwarding (PBF), QoS, or SD-WAN policy rules.
You cannot see ACE App-IDs in Application Override or PBF rule configuration.
However, ACE App-IDs are visible (able to be selected) in QoS and SD-WAN policy
rule configuration and may be present in Application Groups or Application Filters
applied to a rule. If you use ACE App-IDs in these rules, the policy doesn’t control the
application traffic and there is no effect on the application traffic—the rules do not
apply to the ACE App-ID traffic even though ACE App-IDs were added to the rule.
PAN-OS® Administrator’s Guide Version 10.2 903 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
903 | App-ID
New App Viewer (Policy Optimizer)
The Policy Optimizer New App Viewer shows you the Security policy rules that match
downloaded cloud App-IDs from ACE. Use Policy Optimizer to manage the newly identified
applications and add them to cloned rules or to existing rules. Select Policies > Security and then
select New App Viewer in the Policy Optimizer portion of the interface.
The upper portion of the screen is similar to Objects > Application Filters. It works in a similar
manner and filters the Security policy rules shown in the lower portion of the screen. You can
filter the rules that allow applications by category, subcategory, etc. The only categories and
subcategories available for filtering are the ones that match the new applications on the rules
listed in the lower half of the screen, so you don’t waste your time filtering for applications that
aren’t there.
When you filter the rules, only the rules that include the filtered applications are shown in the
lower portion of the screen. Rules that have not seen the apps in the filter are removed from the
list. (You can see them all again by removing the filter.)
Click the number in the Apps Seen column to open the Applications & Usage dialog to change
the way the firewall handles the cloud-based applications in Security policy. Add ACE App-IDs
to Security policy rules using an Application Filter, an Application Group, Policy Optimizer, or by
directly adding an ACE App-ID to a rule. Until you take one of these actions to control clouddelivered App-IDs, the firewall continues to treat the traffic as ssl or web-browsing traffic and
uses existing ssl or web-browsing Security policy rules to control the applications.
Add Apps to an Application Filter with Policy Optimizer
Add App-IDs from the App-ID Cloud Engine (ACE) to Application Filters to automate adding cloud
App-IDs to Security policy. When new ACE App-IDs match an Application Filter, the firewall adds
them to the filter automatically. When you use the Application Filter in a Security policy rule, the
rule automatically controls new ACE App-IDs as they arrive at the firewall and are added to the
filter.
ACE provides App-IDs for applications that were previously identified as ssl or webbrowsing.
PAN-OS® Administrator’s Guide Version 10.2 904 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
904 | App-ID
Using Application Filters is a best practice because they:
• Improve your security posture. Application Filters automate adding new ACE App-IDs to
Security policy rules that you design specifically to handle a particular type of application
traffic, instead of matching the traffic to more general ssl or web-browsing rules.
• Save time. Firewall administrators can configure Application Filters to handle different types of
traffic so that adding new ACE App-IDs to policy is automatic and requires no further effort by
the administrator.
When you create Application Filters, exclude ssl and web-browsing from the filters.
Together, ssl and web-browsing match all browser-based cloud applications, so an
Application Filter that includes ssl and web-browsing matches all browser-based cloud
applications.
Use Policy Optimizer to add ACE App-IDs to Application Filters and to apply the filters to Security
policy rules.
STEP 1 | Go to Policies > Security and then select Policy Optimizer > New App Viewer.
If the firewall has identified traffic with ACE App-IDs, a number displays next to New App
Viewer in the left navigation window to show how many rules match ACE App-IDs. The screen
displays the Security policy rules that match cloud App-IDs.
STEP 2 | Click the number in Apps Seen for a Security policy rule to view the cloud-delivered
applications that matched the rule in the Applications & Usage dialog.
STEP 3 | Select the applications that you want to add to an existing or new Application Filter.
You can sort and filter the applications in Apps Seen by subcategory, risk, amount of traffic
seen over the last 30 days, or when the application was first or last seen.
STEP 4 | Select Application Filter from Create Cloned Rule or Add to Existing Rule, depending on
how you want to handle the applications.
The maximum number of applications you can clone using Create Cloned Rule is 1,000
applications. If there are more than 1,000 applications that you want to move to a
different rule, use Add to Existing Rule instead. If you want to move the applications
to a new rule, simply create the rule first (Policies > Security) and then use Policy
Optimizer to add them to that rule.
STEP 5 | Select or create the Application Filter. Creating an Application Filter using Policy Optimizer
is the almost exactly the same as using Objects > Application Filters to create an Application
PAN-OS® Administrator’s Guide Version 10.2 905 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
905 | App-ID
Filter—you use the same filtering tools and options. This step shows you how to use Policy
Optimizer first for creating a cloned and then for adding to an existing rule.
Create Cloned Rule:
1. Type the Cloned Rule Name (the name for the cloned rule, which will appear in the Security
policy rulebase immediately above the original rule).
2. Select the Policy Action (Allow or Deny).
3. Select the Application Filter Name from the menu or type the name of a new Application
Filter.
4. Select whether the filter should Apply to New App-IDs only or if it should apply to all AppIDs.
5. Use the Category, Subcategory, Risk, Tags, and Characteristic values to filter the types of
applications you want to add to the Application Filter. The firewall automatically adds new
applications that meet the filter criteria to the Application Filter.
6. Click OK to add the applications to the new or existing Application Filter. The firewall
includes the applications that you selected in Step 3 in the Application Filter.
7. Commit the changes.
Add to Existing Rule:
1. Select the Existing Rule Name to add the selected applications to an existing rule in an
Application Filter.
2. Select the Application Filter Name from the menu or type the name of a new Application
Filter.
3. Select whether the Application Filter is Shared, whether you want to Disable override of
application characteristics for the filter, and whether the filter should Apply to New AppIDs only or if it should apply to all App-IDs.
4. Use the Category, Subcategory, Risk, Tags, and Characteristic values to filter the types of
applications you want to add to the Application Filter. The firewall automatically adds new
applications that meet the filter criteria to the Application Filter.
PAN-OS® Administrator’s Guide Version 10.2 906 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
906 | App-ID
5. Click OK to add the applications to the new or existing Application Filter. The firewall
includes the applications that you selected in Step 3 in the Application Filter.
6. Commit the changes.
Add Apps to an Application Group with Policy Optimizer
Add App-IDs from the App-ID Cloud Engine (ACE) to Application Groups and use the Application
Groups in Security policy rules to control cloud App-IDs in Security policy.
ACE provides App-IDs for applications that were previously identified as ssl or webbrowsing.
Use Policy Optimizer to add ACE App-IDs to Application Groups and to apply the groups to
Security policy rules and control the ACE App-IDs in Security policy.
STEP 1 | Go to Policies > Security and then select Policy Optimizer > New App Viewer.
If the firewall or Panorama has downloaded ACE App-IDs, a number displays next to New App
Viewer in the left navigation window. The screen displays the Security policy rules that match
downloaded cloud App-IDs.
STEP 2 | Click the number in Apps Seen for a Security policy rule to see the cloud-delivered
applications that matched the rule in the Applications & Usage dialog.
STEP 3 | Select the applications that you want to add to an existing or new Application Group.
You can sort and filter the applications in Apps Seen by subcategory, risk, amount of traffic
seen over the last 30 days, or when the application was first or last seen.
PAN-OS® Administrator’s Guide Version 10.2 907 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
907 | App-ID
STEP 4 | Select Application Group from Create Cloned Rule or Add to Existing Rule, depending on
how you want to handle the applications.
The maximum number of applications you can clone using Create Cloned Rule is 1,000
applications. If there are more than 1,000 applications that you want to move to a
different rule, use Add to Existing Rule instead. If you want to move the applications
to a new rule, simply create the rule first (Policies > Security) and then use Policy
Optimizer to add them to that rule.
STEP 5 | Select or create the Application Group for the cloned or existing rule. Creating Application
Groups using Policy Optimizer is similar to using Objects > Application Groups to create an
Application Group.
Create Cloned Rule:
1. Type the Cloned Rule Name (the name for the cloned rule, which will appear in the Security
policy rulebase immediately above the original rule).
2. Select the Policy Action (Allow or Deny).
3. In Add to Application Group, select the Application Group to which you want to add the
applications that you selected in Step 3.
4. Select whether to Add container app (default) or only to Add specific apps seen.
When you add the container app, you also add all of the functional apps in that container,
including functional apps that have not yet been seen on the firewall. For example, if you
add the “facebook” container app, that also adds facebook-base, facebook-chat, facebookposting, etc., and also any future applications added to the container. The container app and
its functional apps are subject to the Security policy rule to which you add the Application
Group. Selecting the container app essentially future-proofs and automates security for the
container’s apps so that you don’t have to manually add new apps in that container to your
Security policy.
Adding only the specific apps seen means that only the applications that you selected are
added to the Application Group. If new applications in the same container app arrive at the
firewall, the Application Group doesn’t control them and you have to manually decide how
to handle the new apps.
5. In some cases, the applications that you want to place in an Application Group require
(depend on) other applications to function. In those cases, the Create Cloned Rule dialog
box includes Dependent Applications, where you can select whether to add those
PAN-OS® Administrator’s Guide Version 10.2 908 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
908 | App-ID
applications to the cloned rule. Add the dependent applications to the rule to ensure that
the selected applications function properly.
6. Click OK to add the applications to the new or existing Application Group.
7. Commit the changes.
Add Apps to Existing Rule:
1. Select the Existing Rule Name to add the selected applications to an existing rule in an
Application Group.
2. Select the Application Group in Add to Application Group or type the name of a new
Application Group.
3. As with cloning the rule, you can choose whether to Add container app or Add specific
apps seen. Adding the container app adds all the functional apps in the container and any
future apps added to that container. Adding only the specific apps only adds the specific
selected apps.
4. As with cloning the rule, in some cases, the applications that you want to place in an
Application Group require (depend on) other applications to function. In those cases, the
Add Apps to Existing Rule dialog box includes Dependent Applications, where you can
PAN-OS® Administrator’s Guide Version 10.2 909 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
909 | App-ID
select whether to add those applications to the cloned rule. Add the dependent applications
to the rule to ensure that the selected applications function properly.
5. Click OK to add the applications to the new or existing Application Group.
6. Commit the changes.
Add Apps Directly to a Rule with Policy Optimizer
You can add App-ID Cloud Engine (ACE) App-IDs directly to a rule with Policy Optimizer.
However, consider using Application Filters to automate adding ACE App-IDs to Security policy as
they arrive at the firewall instead of adding them manually.
ACE provides App-IDs for applications that were previously identified as ssl or webbrowsing.
STEP 1 | Go to Policies > Security and then select Policy Optimizer > New App Viewer.
If the firewall or Panorama has downloaded ACE App-IDs, a number displays next to New App
Viewer in the left navigation window. The screen displays the Security policy rules that match
downloaded cloud App-IDs.
STEP 2 | Click the number in Apps Seen for a Security policy rule to view the cloud-delivered
applications that matched the rule in the Applications & Usage dialog.
STEP 3 | Select the applications that you want to add to an existing or cloned Security policy rule.
You can sort and filter the applications in Apps Seen by subcategory, risk, amount of traffic
seen over the last 30 days, or when the application was first or last seen.
PAN-OS® Administrator’s Guide Version 10.2 910 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
910 | App-ID
STEP 4 | Select Applications from Create Cloned Rule or Add to Existing Rule, depending on how you
want to handle the applications.
The maximum number of applications you can clone using Create Cloned Rule is 1,000
applications. If there are more than 1,000 applications that you want to move to a
different rule, use Add to Existing Rule instead. If you want to move the applications
to a new rule, simply create the rule first (Policies > Security) and then use Policy
Optimizer to add them to that rule.
STEP 5 | Add the selected applications to a cloned rule or to an existing rule.
Create Cloned Rule:
1. Type the Name (the name for the cloned rule, which will appear in the Security policy
rulebase immediately above the original rule). The cloned rule has the same action (allow or
deny) as the original rule.
2. Select whether to Add container app (default) or only to Add specific apps seen.
When you add the container app, you also add all of the functional apps in that container,
including functional apps that have not yet been seen on the firewall. For example, if you
add the “facebook” container app, that also adds facebook-base, facebook-chat, facebookposting, etc., and also any future applications added to the container. The container and its
functional apps are subject to the Security policy rule that you are cloning. Selecting the
container app essentially future-proofs and automates security for the container’s apps so
that you don’t have to manually add new apps in that container to your Security policy.
Adding only the specific apps seen means that only the applications that you selected are
added to the cloned rule. If new applications in the same container app arrive at the firewall,
the cloned rule doesn’t control them and you have to manually decide how to handle the
new apps.
3. In some cases, the applications that you want to add to a rule require (depend on) other
applications to function. In those cases, the Create Cloned Rule dialog box includes
Dependent Applications, where you can select whether to add those applications to
PAN-OS® Administrator’s Guide Version 10.2 911 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
911 | App-ID
the cloned rule. Add the dependent applications to the rule to ensure that the selected
applications function properly.
4. Click OK to add the applications to the cloned rule.
5. Commit the changes.
Add Apps to Existing Rule:
1. Select the Name of the existing rule to which you want to add the selected applications.
2. As with cloning the rule to add applications, you can choose whether to Add container
app or Add specific apps seen. Adding the container app adds all the functional apps in the
container and any future apps added to that container. Adding only the specific apps only
adds the specific selected apps.
3. As with cloning the rule, in some cases, the applications that you want to add to a rule
require (depend on) other applications to function. In those cases, the Add Apps to Existing
Rule dialog box includes Dependent Applications, where you can select whether to add
PAN-OS® Administrator’s Guide Version 10.2 912 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
912 | App-ID
those applications to the cloned rule. Add the dependent applications to the rule to ensure
that the selected applications function properly.
4. Click OK to add the applications to the existing rule.
5. Commit the changes.
Replace an RMA Firewall (ACE)
To restore the configuration on a managed firewall when there is a Return Merchandise
Authorization (RMA), the procedure is to:
• Review Before Starting RMA Firewall Replacement.
• On Panorama, replace the serial number of the old firewall with the new firewall’s serial
number.
• In the firewall CLI, check to ensure that the firewall is online and connected to the Knowledge
service so that the firewall can download the cloud application catalog:
1. Access the firewall CLI.
2. In Operational mode, check the cloud App-ID connection:
admin@vm1> show cloud-appid connection-to-cloud
If the firewall is connected to the cloud, the show command returns:
ACE Cloud server: kcs.ace.tpcloud.paloaltonetworks.com:443Cloud
connection: connected
Information about the connection also displays. If the firewall is not connected to the cloud,
check whether DNS services are functioning and check for any other network-related
connectivity issues.
• With the firewall connected to the App-ID cloud, Restore the Firewall Configuration after
Replacement.
PAN-OS® Administrator’s Guide Version 10.2 913 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
913 | App-ID
Impact of License Expiration or Disabling ACE
If you enable App-ID Cloud Engine (ACE) on a firewall, download ACE App-IDs to the firewall, and
then use those App-IDs in objects such as Application Filters and in Security policy rules, then you
need to understand what happens if the SaaS Security Inline license expires or if you disable ACE.
Disabling ACE and the SaaS Security Inline license expiring both affect downloaded ACE AppIDs, the catalog of ACE App-IDs, Security policy rules that control ACE App-IDs, and objects that
include ACE App-IDs. The effect is the same unless otherwise noted:
• ACE App-IDs remain on the firewall, but the firewall stops enforcing ACE App-IDs in Security
policy.
Security policy rules that control ACE App-IDs no longer control ACE App-IDs even though
they are visible in the rule. Traffic that was controlled by ssl or web-browsing rules before ACE
was enabled on the firewall is controlled by those rules again until you update and activate the
SaaS Security Inline license and/or re-enable ACE or change those rules.
• Enforcement of Security policy rules based on ACE App-IDs stops within 4-6 hours of the
license expiring (based on a timer that periodically checks license status).
Enforcement of Security policy rules based on ACE App-IDs stops immediately after you
commit the disabling ACE on the firewall.
Disabling ACE stops enforcing Security policy rules based on ACE App-IDs as soon as
you commit the change even if the SaaS Security Inline license is still valid and active.
• The catalog of ACE App-IDs remains on the firewall and on Panorama but the cloud engine no
longer updates the catalog.
• The connection from the firewall to ACE no longer functions. If you re-enable ACE or renew
the SaaS Security Inline license, it may take some time to download all of the catalog updates.
• If the SaaS Security Inline license expires, the ACE service stops working within 4-6 hours.
Panorama doesn’t require a SaaS Security Inline license, so there is no license to expire
on Panorama. However, when the license expires on managed firewalls, configuration
pushes to those firewalls from Panorama fail if they contain ACE configurations in
Security policy or in Application Groups.
• Objects such as Application Filters and Application Groups are not changed, but any ACE AppIDs that you placed in those objects are no longer enforced even though the ACE App-IDs are
still visible.
• If you are using SaaS Policy Recommendation, the firewall can no longer pull SaaS policy
recommendations, so the SaaS administrator cannot push new policy recommendations to the
firewall. Policy recommendations that were downloaded before license expiration remain in
the configuration but they are not enforced (same behavior as Security policies configured with
ACE App-IDs when the license expires or ACE is disabled).
Commit Failure Due to Cloud Content Rollback
Although it is extremely unlikely, it is possible that ACE App-IDs may need to be rolled back
(reverted) because of bad metadata or issues with applications. If ACE must revert App-IDs and
you used those App-IDs in a Security policy rule (directly or in an Application Group), commit
actions fail until those applications are removed from Security policy rules and from objects.
PAN-OS® Administrator’s Guide Version 10.2 914 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
914 | App-ID
If it becomes necessary to roll back App-IDs, ACE reverts all of the most recently delivered cloudbased App-IDs, signatures, metadata, categories, subcategories, and tags from the ACE catalog.
Removing the App-IDs from the catalog removes them from the firewall, which is why the commit
action fails when the App-IDs are used in Security policy.
If you did not use the applications that ACE had to roll back in Security policy, there is no
impact to the configuration and commit actions succeed.
When you attempt to commit a configuration after an ACE content rollback, the commit failure
message lists the applications that ACE reverted, as in this example Validation Error:
To fix the issue, you must remove the listed applications from Security policy rules, regardless
of whether they were added directly to a rule or were added using an Application Group. If the
application is used in an Application Group, remove it from the Application Group.
In this example, content-qa-test-2 is the reverted application, which is referenced in the
Application Group content-qa-test-apps. After you remove content-qa-test-2 from
the Application Group, commit actions succeed.
Troubleshoot App-ID Cloud Engine
This topic provides general troubleshooting information for the App-ID Cloud Engine (ACE).
• To check if an appliance has a valid SaaS Security Inline license, run the operational CLI
command show cloud-appid connection-to-cloud. If there is an issue, the command
returns the message:
ACE Error: License check failed. Check if SaaS license is installed
and activeCloud connection: failed
In addition, the output shows the time of the last successful connection, for example: Last
successful gRPC connection: 2021-05-20 16:00:00 -0800 PDT
If the license is installed and the connection to ACE is good, then the command returns the
URL for the ACE cloud server connection and the status Cloud connection: connected,
along with connection statistics and the status of the device certificate, including the certificate
validity dates.
PAN-OS® Administrator’s Guide Version 10.2 915 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
915 | App-ID
• Panorama commit all/push to managed firewalls fails. Check if any of the following conditions
exist and repair them:
• Do managed firewalls have a valid SaaS Security Inline license? If not, then they do not
have the ACE catalog and the commit all/push operation fails. Depending on whether you
want to managed firewalls to handle ACE App-IDs, either remove the ACE objects from
the pushed configuration and try again or install valid SaaS Security Inline licenses on the
managed firewalls, wait for the catalog to download.
There are fewer than four thousand content-provided App-IDs. After you download
the ACE catalog, you see many thousands more applications on the firewall and
can confirm by checking Objects > Applications or by using the operational CLI
command show cloud-appid cloud-app-data application all to
see the new App-IDs.
• Has the connection between a managed firewall and ACE has gone down? Check the
connection to the ACE cloud and restore the connection if necessary.
The operational CLI command show cloud-appid connection-to-cloud provides
the cloud connection status and the ACE cloud server URL.
• The ACE catalog on Panorama and the ACE catalog on managed firewalls is out-of-sync,
which results in pushed configurations that include ACE apps that are not in the firewall’s
catalog. If the connection between the firewall and ACE is up, the outdated catalog will
update in the next few minutes automatically and resolve the issue. (Wait five minutes and
try again.)
You can also run the operational CLI command debug cloud-appid cloudmanual-pull check-cloud-app-data to update the catalog manually.
• Are the firewalls all running PAN-OS 10.2 or later? (Pushing configurations that reference
ACE applications and objects to firewalls running earlier versions than PAN-OS 10.2 is not
allowed.)
• In an HA pair (active/active or active/passive) that has an ACE configuration, if you run the
operational command show session all or show session id <id>, the output for ACE
applications may show the global App-ID number instead of the application name. The firewall
only shows the application name if its data plane has the cloud application data. If not, then the
firewall shows the global App-ID number for the application instead.
• To reset the connection to ACE (the gRPC connection), run the operational CLI command
debug cloud-appid reset connection-to-cloud.
• View the ACE applications downloaded to the appliance with the operational CLI command
show cloud-appid cloud-app-data application. You can view all downloaded apps
or individual apps by App-ID or application name.
• View pending requests for ACE App-IDs with the operational CLI command show cloudappid signature-dp pending-request. The output includes how many times the
firewall sent the request to ACE (tries). After eleven tries, the send operation times out.
• The operational CLI command show cloud-appid has more useful options:
admin@PAN-ACE-VM-1> show cloud-appid ?
PAN-OS® Administrator’s Guide Version 10.2 916 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
916 | App-ID
> app-objects-in-policy Show application-filter/applicationgroups referred in policy
> app-to-filtergroup-mapping Show application to matched filter
and groups
> application Show Application info for UI
> application-filter Show cloud apps in applicationfilters
> application-group Show cloud apps in applicationgroups
> cloud-app-data Show cloud application, container
and metadata
> connection-to-cloud Show gRPC connection status to cloud
application server
> ha-info Show statistics of cloud application
high availability
> overlap-appid Show duplicated applications in
predefined content
> signature-dp Show cloud signatures and
applications used on DP
> task Show task on management-plane
> transaction Show cloud application transaction
> version Show Cloud-AppID version
• To view the global counters for ACE, run the operational CLI command show counter
global filter value all category cad (cad stands for “cloud app-identification).
• To view statistics for bytes and packets received and sent to/from shared memory and to/from
the security client for services such as ACE, DLP, and IoT, run the operational command show
ctd-agent statistics.
• If you notice a discrepancy between the number of applications that match an Application
Filter when you look in the user interface versus when you look in the CLI, it’s because of the
way the firewall counts matching applications in the user interfaces versus in the CLI:
• When you look at an Application Filter in Objects > Application Filters, the firewall displays
all of the matching applications in the ACE catalog, regardless of whether the firewall has
actually seen those applications and downloaded their App-IDs, and the number count
includes all of those applications.
• When you look at an Application Filter in the CLI with the show cloud-appid
application-filter operational command, the firewall only displays the number of
matching applications for which the firewall has downloaded ACE App-IDs.
For this reason, the user interface may show more matching applications than the CLI for the
same Application Filter.
The same thing applies to Application Groups when you look at them in the user
interface versus the CLI.
• ACE App-IDs are supported for Security policy only. ACE App-IDs are not supported for any
other policy type.
However, when you configure QoS or SD-WAN policy, ACE App-IDs are visible (able to be
selected) and may be present in Application Groups or Application Filters applied to the rule,
but adding them to QoS or SD-WAN policy has no effect on the application traffic. (The QoS
and SD-WAN policies don’t control the application traffic.)
PAN-OS® Administrator’s Guide Version 10.2 917 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
917 | App-ID
SaaS App-ID Policy Recommendation
The rapid proliferation of SaaS applications makes it difficult to assign all of them specific AppIDs, gain visibility into those applications, and control them. Security policy rules that allow ssl,
web-browsing, or “any” application may allow unsanctioned SaaS applications that can introduce
security risks to your network. To gain visibility into those applications and control them on the
firewall, SaaS Security administrators can recommend Security policy rules with specific SaaS
App-IDs provided by the App-ID Cloud Engine (ACE) to PAN-OS firewall administrators. PAN-OS
administrators can import those rules on firewall’s that have a SaaS Security Inline subscription.
SaaS Policy Recommendation requires a SaaS Security Inline subscription. Each appliance
that uses the SaaS Policy Recommendation Engine needs to generate and install a valid
device certificate or use Panorama to generate and install a valid device certificate.
A SaaS Security Inline connection to Strata Logging Service (Strata Logging Service)
is required for SaaS visibility. Configure Log Forwarding to Strata Logging Service and
enable Log Forwarding with the correct Log Forwarding profile in Security policy rules. At
a minimum, you must forward Traffic logs and URL logs to Strata Logging Service for SaaS
Security Inline to work properly.
All hardware platforms that support PAN-OS 10.1 or later support SaaS Policy
Recommendation and all appliances on which you want to use SaaS Policy
Recommendation require PAN-OS 10.1 or later. Panorama cannot push and commit
SaaS Policy Recommendations to firewalls that don’t have a SaaS Security Inline license
installed or to firewalls that run an earlier version of PAN-OS than 10.1.
• The SaaS Security Administrator’s Guide describes the SaaS Security administrator’s procedure
for creating Security policy rule recommendations and then pushing them to the firewall.
• The PAN-OS Administrator’s Guide describes how the PAN-OS administrator imports and
manages policy recommendations from the SaaS Security administrator.
The SaaS Security administrator creates the new rule, adds applications, users, and groups to the
rule, and sets the rule action. The rule action can be allow or block; no other actions are permitted
for pushed rules. The SaaS Security administrator then pushes the rule to the appropriate
appliances and the rule appears in the firewall interface (Device > Policy Recommendation >
SaaS).
The PAN-OS administrator evaluates the recommended rule and decides whether to implement
it on the firewall. If the PAN-OS administrator chooses to implement the rule, the administrator
imports it on the firewall and selects where to place the policy rule in the firewall rulebase. When
a PAN-OS administrator imports a policy recommendation, the firewall creates the required HIP
profiles, tags, and Application Groups automatically (the PAN-OS administrator doesn’t have to do
it manually).
If the SaaS Security administrator pushes Security profiles with the policy
recommendation and those profiles don’t exist on the firewall, the firewall import fails. If
the profiles already exist on the firewall, the import succeeds.
If the SaaS Security administrator updates a policy rule recommendation, the PAN-OS
administrator sees the update and imports it into the firewall. If the SaaS Security administrator
PAN-OS® Administrator’s Guide Version 10.2 918 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
918 | App-ID
deletes a policy rule recommendation, the PAN-OS administrator sees the action and deletes the
rule from the firewall Security policy rulebase.
If the SaaS Security Inline license expires, the firewall no longer pulls SaaS policy
recommendations, so you see no new recommendations. However, Security policy rules
that you already imported continue to work.
If you disable ACE, the firewall no longer receives new cloud application signatures and
App-IDs and the firewall cannot import SaaS policy recommendations based on new ACE
App-IDs.
The ACE deployment process (connecting to the cloud, installing device certificates, activating
the license on the SaaS Security Portal and pushing it to Panorama and firewalls, etc.) also sets up
SaaS Policy Recommendation.
Update all appliances to the latest Threat content updates.
User interface additions for this new feature include:
• Device > Policy Recommendation > SaaS displays policy recommendations from SaaS
administrators and enables firewall administrators to import, update, remove, and control
recommended SaaS policies. The page display includes Application Groups configured by the
SaaS administrator for the policy.
• Role-based interface access (Device > Admin Roles) has a new option on the Web UI tab for
SaaS policy recommendation permissions: Device > Policy Recommendation > SaaS.
• SaaS policy recommendations are automatically tagged SaaSSecurityRecommended, which is
displayed in the Tags column in the interface.
You can import and update SaaS policy recommendations pushed by SaaS administrators and
remove SaaS policy recommendations that the SaaS administrator has deleted.
• Import SaaS Policy Recommendation
• Import Updated SaaS Policy Recommendation
• Remove Deleted SaaS Policy Recommendation
Import SaaS Policy Recommendation
When a SaaS Security administrator pushes Security policy rule recommendations to a PAN-OS
firewall, the PAN-OS firewall administrator can import those rules on the firewall to gain visibility
into and control of the applications in the policy recommendation.
See the SaaS Security Administrator’s Guide for the SaaS administrator’s policy recommendation
and push procedures. This procedure shows PAN-OS administrators how to import policy
recommendations.
If the SaaS Security administrator pushes Security profiles with the policy
recommendation and those profiles don’t exist on the firewall, the firewall import fails. If
the profiles already exist on the firewall, the import succeeds.
PAN-OS® Administrator’s Guide Version 10.2 919 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
919 | App-ID
STEP 1 | Device > Policy Recommendation > SaaS on the firewall and Panorama > Policy
Recommendation > SaaS on Panorama show all of the SaaS policy recommendations pushed
from the SaaS administrator. Push policy recommendations from Panorama to managed
firewalls.
STEP 2 | Refresh ( ) Device > Policy Recommendation > SaaS (or Panorama > Policy
Recommendation > SaaS) to ensure that the SaaS policy recommendations are up-to-date.
Any time you push policy recommendations from Panorama to managed firewalls,
refresh ( ) the page on the firewalls to ensure that the recommendations are up-todate.
Newly pushed policy recommendations appear at the top of the screen. Active
Recommendations shows the value active and New Updates Available shows the value Yes.
STEP 3 | Select a new policy recommendation.
You import one policy recommendation at a time. The Applications column shows an
Application Group for each policy recommendation. Click the name of the group to see the
applications in that group.
The Device column shows the source device that the SaaS administrator configured for the
rule. The term “SaaS” precedes the source device. The source device can be:
• MCD—Managed Compliant Device
• MNCD—Managed Non-compliant Device
• UMCD—Unmanaged Compliant Device
• UMNCD—Unmanaged Non-compliant Device
For example, SaaS - MCD indicates a managed, compliant source device.
STEP 4 | Import Policy Rule.
In the Import Policy Rule dialog:
• Name—Name the imported rule using a name that describes the rule’s intent.
If you specify a rule name that already exists in the Security policy rulebase, the
imported rule overwrites the existing rule.
• After Rule—Select the rule after which to place the imported SaaS rule. Think about the
firewall’s rulebase and how the new rule may affect existing rules. If you do not select a
rule (No Rule Selection), then the rule is placed at the top of the Security policy rulebase.
In some cases, that’s not where you want to place the rule. For example, you may want
some particular block rules to always be at the top of the rulebase, such as blocking QUIC
PAN-OS® Administrator’s Guide Version 10.2 920 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
920 | App-ID
protocol. Be aware of the intent of the imported rule and be careful not to shadow existing
rules.
The Description comes from the description entered when the SaaS administrator created the
rule. You can change it or leave it as-is.
The import process automatically creates an Application Group for the applications
in the policy recommendation. The name of the Application Group is derived from
the Name that the SaaS Security administrator gave to the rule. The firewall also
automatically creates any HIP profiles and tags that the SaaS administrator applied to
the rule.
STEP 5 | Click OK to import the rule and add it to the Security policy rulebase in the position selected
in After Rule.
STEP 6 | When you see the status message “You’ve successfully updated your Security policy rules”,
click OK.
The Location column now shows the rule’s location (vsys) on the firewall, which corresponds
to the vsys to which the SaaS administrator pushed the rule.
STEP 7 | Confirm that the imported policy rule is in the Security policy rulebase (Security > Policies) at
the specified location and that the firewall created the associated objects.
For example, check the Security policy rule for:
• The rule’s Source Device is populated and shows the source device for the rule on the
Source tab.
• The Application Group populates the rule’s Application tab.
• Associated profiles are attached to the rule (Actions tab).
Also check that:
• Objects > Applications Group shows the imported Application Group.
• Objects > GlobalProtect > HIP Objects and Objects > GlobalProtect > HIP Profiles show
the HIP information pushed from the SaaS Security administrator with the rule.
Import Updated SaaS Policy Recommendation
When a SaaS Security administrator pushes Security policy rule recommendations to a PAN-OS
firewall (or Panorama), the PAN-OS administrator can import those rules to gain visibility into
and control of the applications in the policy recommendation. However, if the SaaS administrator
updates the rule, for example by adding or removing applications, the rule also needs to be
updated on the firewall.
If the SaaS Security administrator pushes new or updated Application Groups, HIP
profiles, or tags, the firewall automatically creates or updates those objects. If the SaaS
Security administrator pushes Security profiles with the policy recommendation update
and those profiles don’t exist on the firewall, the firewall import fails. If the profiles already
exist on the firewall, the import succeeds.
PAN-OS® Administrator’s Guide Version 10.2 921 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
921 | App-ID
STEP 1 | Refresh ( ) Device > Policy Recommendation > SaaS (or Panorama > Policy
Recommendation > SaaS) to ensure that you see all of the latest SaaS policy
recommendations that the SaaS administrator pushed to the firewall.
STEP 2 | Check New Updates Available.
If the value in the New Updates Available column is No, then there are no updates to the rule.
If the value is Yes, then the SaaS administrator has pushed an update to the rule to the firewall.
In addition, Active Recommendations shows the value active.
STEP 3 | Click the Application Group name in the Applications column to see the updated list of
applications that the rule controls.
STEP 4 | Select a policy recommendation to update.
You update only one policy recommendation at a time.
STEP 5 | Click Import Policy Rule to import the policy (if there are no updates to the rule, this option
is grayed out and you can’t select it).
The Import Policy Rule dialog appears. The Name is already populated and cannot be changed
because the rule has already been imported. After Rule also cannot be changed in the dialog,
but if you want to change the rule’s location in the Security policy rulebase, you can do that on
Policies > Security in the same way that you change the position of any Security policy rule.
You can change the Description or leave it as-is.
STEP 6 | Click OK.
STEP 7 | Click Yes in Confirm Change to import the updated rule (or click No if you don’t want to
import the changed rule).
The firewall automatically makes any changes to the Application Group, HIP profiles, and tags
associated with the rule.
Remove Deleted SaaS Policy Recommendation
When a SaaS Security administrator pushes Security policy rule recommendations to a PAN-OS
appliance, the PAN-OS administrator can import those rules to gain visibility into and control
of the applications in the policy recommendation. However, if the SaaS Security administrator
deletes the rule, you should also delete that rule from the PAN-OS appliance.
When a SaaS Security administrator deletes a rule, the Active Recommendation column shows
the value removed (for valid rules, the value is active).
STEP 1 | Select a rule that the SaaS Security administrator removed (you can select only one rule to
remove at a time).
The Import Policy Rule option is grayed out because the rule can no longer be
imported.
PAN-OS® Administrator’s Guide Version 10.2 922 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
922 | App-ID
STEP 2 | Click Remove Recommendation Mapping.
This removes local mapping of the Security policy rule on the firewall. For example, mappings
to locations, users, and the rule are deleted. The Remove Recommendation Mapping dialog
box shows you the location of the rule so that you know from where the rule is removed.
STEP 3 | Click OK.
STEP 4 | In the Confirm Change dialog, click Yes to remove the rule from the policy recommendation
database.
This action only removes the rule from the policy recommendation rule list. It does
NOT remove the rule from the Security policy rulebase. You must manually remove the
rule from the rulebase.
STEP 5 | A Status dialog appears to confirm that the policy recommendation mapping has been
removed, but you still need to remove the rule from the Security policy rulebase.
STEP 6 | Go to Policies > Security and delete the rule from the Security policy rulebase.
PAN-OS® Administrator’s Guide Version 10.2 923 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
923 | App-ID
Application Level Gateways
The Palo Alto Networks firewall does not classify traffic by port and protocol; instead it identifies
the application based on its unique properties and transaction characteristics using the AppID technology. Some applications, however, require the firewall to dynamically open pinholes
to establish the connection, determine the parameters for the session and negotiate the ports
that will be used for the transfer of data; these applications use the application-layer payload to
communicate the dynamic TCP or UDP ports on which the application opens data connections.
For such applications, the firewall serves as an Application Level Gateway (ALG), and it opens a
pinhole for a limited time and for exclusively transferring data or control traffic. The firewall also
performs a NAT rewrite of the payload when necessary.
• H.323 (H.225 and H.248) ALG is not supported in gatekeeper routed mode.
• When the firewall serves as an ALG for the Session Initiation Protocol (SIP), by default
it performs NAT on the payload and opens dynamic pinholes for media ports. In some
cases, depending on the SIP applications in use in your environment, the SIP endpoints
have NAT intelligence embedded in their clients. In such cases, you might need to
disable the SIP ALG functionality to prevent the firewall from modifying the signaling
sessions. When SIP ALG is disabled, if App-ID determines that a session is SIP, the
payload is not translated and dynamic pinholes are not opened. See Disable the SIP
Application-level Gateway (ALG).
When you use Dynamic IP and Port (DIPP) NAT, the Palo Alto Networks firewall ALG
decoder needs a combination of IP and Port (Sent-by Address and Sent-by Port) under SIP
headers (Contact and Via fields) to be able to translate the mentioned headers and open
predict sessions based on them.
The following table lists IPv4, NAT, IPv6, NPTv6 and NAT64 ALGs and indicates with a check
mark whether the ALG supports each protocol (such as SIP).
App-ID IPv4 NAT IPv6 NPTv6 NAT64
SIP — —
SCCP — —
MGCP — — —
FTP —
RTSP —
MySQL — — —
PAN-OS® Administrator’s Guide Version 10.2 924 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
924 | App-ID
App-ID IPv4 NAT IPv6 NPTv6 NAT64
Oracle/
SQLNet/ TNS
—
RPC — — —
RSH — — —
UNIStim — — —
H.225 — — —
H.248 — — —
PAN-OS® Administrator’s Guide Version 10.2 925 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
925 | App-ID
Disable the SIP Application-level Gateway (ALG)
The Palo Alto Networks firewall uses the Session Initiation Protocol (SIP) application-level
gateway (ALG) to open dynamic pinholes in the firewall where NAT is enabled. However, some
applications—such as VoIP—have NAT intelligence embedded in the client application. In these
cases, the SIP ALG on the firewall can interfere with the signaling sessions and cause the client
application to stop working.
One solution to this problem is to define an Application Override Policy for SIP, but using this
approach disables the App-ID and threat detection functionality. A better approach is to disable
the SIP ALG, which does not disable App-ID or threat detection.
You can disable only the following App-IDs: sccp, sip, teredo, and unistim.
The following procedure describes how to disable the SIP ALG.
STEP 1 | Select Objects > Applications.
STEP 2 | Select the sip application.
You can type sip in the Search box to help find the sip application.
STEP 3 | Select Customize... for ALG in the Options section of the Application dialog box.
STEP 4 | Select the Disable ALG check box in the Application - sip dialog box and click OK.
PAN-OS® Administrator’s Guide Version 10.2 926 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
926 | App-ID
STEP 5 | Close the Application dialog box and Commit the change.
PAN-OS® Administrator’s Guide Version 10.2 927 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
927 | App-ID
Use HTTP Headers to Manage SaaS Application Access
Unsanctioned usage of SaaS applications can be a way for your users to transmit sensitive
information outside of your network, usually by accessing a consumer version of an application.
However, if you need to allow access to the enterprise version of these applications for specific
individuals or organizations, then you can't block the SaaS application entirely.
You can use custom HTTP headers to disallow SaaS consumer accounts while allowing a specific
enterprise account. Many SaaS applications allow or disallow access to applications based on
information contained in specific HTTP headers. You can Create HTTP Header Insertion Entries
using Predefined Types to manage access to popular SaaS applications, such as Google G Suite
and Microsoft Office 365. Palo Alto Networks® uses content updates to maintain predefined rule
sets specific to these applications, as well as to add new predefined rule sets.
You can also Create Custom HTTP Header Insertion Entries if you want to manage access to a
SaaS application—that uses HTTP headers to limit service access—for which Palo Alto Networks
has not provided a predefined set of rules.
Be aware that commercial SaaS applications always use SSL so decryption is necessary to perform
HTTP header insertion. You can configure the firewall to decrypt traffic using SSL Forward Proxy
decryption if traffic is not already decrypted by an upstream firewall.
You don't need a URL Filtering license to use this feature.
To understand how to use HTTP headers to manage SaaS applications, see the following:
• Understand SaaS Custom Headers
• Domains used by the Predefined SaaS Application Types
• Create HTTP Header Insertion Entries using Predefined Types
• Create Custom HTTP Header Insertion Entries
Understand SaaS Custom Headers
Before you begin, make sure you understand the custom HTTP headers you will use with the
SaaS application you are managing. You need to understand what you can accomplish with these
headers and the information you need to specify to accomplish your goals.
Be aware that SaaS applications that use custom headers do not always use them to control
access to types of accounts. For example, Palo Alto Networks® provides predefined support for
YouTube custom headers that determine whether network users can access restricted content.
You should also read the documentation for the SaaS application to which you want to control
access so that you understand what headers you need to use for that application.
PAN-OS® Administrator’s Guide Version 10.2 928 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
928 | App-ID
The following limits apply to HTTP header insertion:
• Header name character length: 100.
• Header value character length: 16K.
Be aware that some SaaS applications might define custom header names, or assign
values to their custom headers, that exceed these limits. These situations should be
rare, but if a SaaS application does exceed one or both of these character length limits,
then your next-generation firewall can not successfully manage access to that SaaS
application.
The following table lists the headers that you can use for the SaaS applications for which Palo
Alto Networks provides predefined support; each header also includes a link to more information
specific to that header.
Application Headers For More Information
Dropbox X-Dropbox-allowedTeam-Ids
www.dropbox.com/help/business/networkcontrol
You can allow access to sanctioned Enterprise
Dropbox accounts. This header's value is
the business account's team ID, which you
can obtain from the network control section
of the Dropbox admin console. You must
also enable this functionality from the same
location.
For details on managing this header, as well
as how to enable your Dropbox clients so that
you can decrypt their traffic, contact your
Dropbox account representative.
Google G Suite X-GooGApps-AllowedDomains
support.google.com/a/answer/1668854?
hl=en
You can allow access to specific Google
accounts from your domain. The values that
you give to this header are your domain and
subdomains.
To successfully insert headers for Google
applications, you must also:
PAN-OS® Administrator’s Guide Version 10.2 929 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
929 | App-ID
Application Headers For More Information
1. Create an SSL decryption profile that
includes the following categories and URLs:
• business-and-economy
• computer-and-internet-info
• content-delivery-networks
• internet-communications-andtelephony
• low-risk
• online-storage-and-backup
• search-engine
• web-based-email
• drive.google.com
• *.google.com
• *.googleusercontent.com
• *.gstatic.com
2. HTTP header insertion is not currently
supported for HTTP/2. To insert headers,
downgrade HTTP/2 connections to
HTTP/1.1 using the Strip ALPN feature
in the appropriate decryption profile. For
more information, see App-ID and HTTP/2
Inspection.
3. Create rules to block the Quick UDP
Internet Connections (QUIC) App-ID and
place them at the top of your security
policy because the firewall does not
support header insertion for this protocol.
When you do, the app reverts to using
HTTP/2 over TLS, which the firewall
handles in the previous step.
Microsoft Office
365
Restrict-Access-ToTenants
Restrict-AccessContext
docs.microsoft.com/en-us/azure/activedirectory/active-directory-tenant-restrictions
You provide Restrict-Access-ToTenants with a list of tenants you want to
allow your users to access. You can use any
domain that is registered with a tenant to
identify the tenant in this list.
You provide Restrict-Access-Context
with the directory ID that is setting the tenant
restriction. You can find your directory ID in
PAN-OS® Administrator’s Guide Version 10.2 930 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
930 | App-ID
Application Headers For More Information
the Azure portal. Sign in as an administrator,
select Azure Active Directory, then select
Properties.
YouTube YouTube-Restrict support.google.com/a/answer/6214622?
hl=en
You provide this header with information on
the type of videos you want your users to be
able to view. You can specify either a Strict or
Moderate setting. See support.google.com/
a/answer/6212415 for details on these
different settings.
Domains used by the Predefined SaaS Application Types
SaaS applications use HTTPS so, to insert custom headers into this traffic, custom headers must
be decrypted. If you use the forward-proxy decryption available on the firewall to decrypt custom
headers, you must identify the specific HTTPS traffic you want to decrypt by identifying the
domains associated with the traffic. The following table identifies the relevant domains for each of
the SaaS applications for which Palo Alto Networks® has provided predefined rules.
Application Domains
Dropbox *.dropbox.com
G Suite *.google.com
gmail.com
Microsoft Office
365
login.microsoftonline.com
login.microsoft.com
login.windows.net
YouTube www.youtube.com
m.youtube.com
youtubei.googleapis.com
youtube.googleapis.com
www.youtube-nocookie.com
PAN-OS® Administrator’s Guide Version 10.2 931 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
931 | App-ID
Create HTTP Header Insertion Entries using Predefined Types
STEP 1 | If there are no upstream devices already decrypting HTTPS traffic, configure SSL Forward
Proxy decryption.
If you're configuring SSL decryption for Dropbox, then you must also configure your
Dropbox clients to allow SSL traffic. These procedures are specific and private to
Dropbox. To obtain these procedures, contact your Dropbox account representative.
1. Add a custom URL category for the SaaS application you're managing (Objects > Custom
Objects > URL Category).
2. Specify a Name for the category.
3. Add the domains specific to the SaaS application you're managing or for which you want
to insert the username and domain in the headers. See Domains used by the Predefined
SaaS Application Types for a list of the domains that you use for each of the predefined
SaaS applications. See Insert Username in HTTP Headers for more information on
configuring the firewall to include the username and domain in the HTTP headers.
Each domain name can be up to 254 characters and you can identify a maximum
of 50 domains for each entry. The domain list supports wildcards (for example,
*.example.com). As a best practice, do not nest wildcards (for example, *.*.*) and do
not overlap domains within the same URL profile.
4. For SaaS application management, create a decryption policy rule and, as you follow this
procedure, configure the following:
• In the Service/URL Category tab, Add the URL Category that you created in the
previous step.
• In the Options tab, make sure the Action is set to Decrypt and that the Type is set to
SSL Forward Proxy.
STEP 2 | Edit or create a URL Filtering profile.
STEP 3 | Select HTTP Header Insertion in the URL Filtering Profile dialog.
STEP 4 | Add an entry.
1. Specify a Name (up to 100 characters) for this entry.
2. Select a predefined Type.
This populates the Domains and Headers lists.
3. For each Header, enter a Value.
Each header value can have up to 16 thousand characters.
4. (Optional) Select Log to enable logging of insertion activity for the headers.
Allowed traffic is not logged, so header insertions are not logged for allowed traffic.
5. Click OK to save your changes.
PAN-OS® Administrator’s Guide Version 10.2 932 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
932 | App-ID
STEP 5 | Add or edit a Security policy rule (Policies > Security) to include the HTTP header insertion
URL Filtering profile.
• For SaaS application management, allow users to access the SaaS application for which
you're configuring this header insertion rule.
• To include the username and domain in the HTTP headers, apply the URL Filtering profile to
the Security policy rule for HTTP or HTTPS traffic.
1. Choose the URL Filtering profile (Actions > URL Filtering) that you edited or created in
step 2.
2. Click OK to save and then Commit your changes.
STEP 6 | Verify that the firewall correctly inserts the header.
• For SaaS application management, from an endpoint, confirm that access to the SaaS
application is working in the way you expect.
1. Try to access an account or content that you expect to be able to access. If you cannot
access the SaaS account or content, then the configuration is not working.
2. Try to access an account or content that you expect will be blocked. If you can access
the SaaS account or content, then the configuration is not working.
3. If both of the previous steps work as expected, examine the URL Filtering logs for
recorded HTTP header insertion activity (if you configured logging in step 4.4).
Create Custom HTTP Header Insertion Entries
STEP 1 | If there are no upstream devices already decrypting HTTPS traffic, configure SSL Forward
Proxy decryption.
1. Add a custom URL category for the SaaS application you are managing (Objects >
Custom Objects > URL Category).
2. Specify a Name for the category.
3. Add the domains specific to the SaaS application you are managing.
4. Create a decryption policy rule and, as you follow this procedure, configure the
following:
• In the Service/URL Category tab, Add the URL Category that you created in the
previous step.
• In the Options tab, make sure the Action is set to Decrypt and that the Type is set to
SSL Forward Proxy.
STEP 2 | Edit or create a URL Filtering profile.
STEP 3 | Select HTTP Header Insertion in the URL Filtering Profile dialog.
PAN-OS® Administrator’s Guide Version 10.2 933 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
933 | App-ID
STEP 4 | Add an entry.
1. Specify a Name for this entry.
2. Select Custom as the Type.
3. Add domains to the Domains list.
You can add up to 50 domains and each domain name can have up to 256 characters;
wildcards are supported (for example, *.example.com).
HTTP header insertion occurs when a domain in this list matches the domain in
the Host header of the HTTP request.
4. Add headers to the Headers list.
You can add up to 5 headers, and each header can have up to 100 characters but cannot
contain any spaces.
5. For each header, enter a Value.
Each header value can have up to 16K characters.
6. (Optional) Log insertion activity for the headers.
7. Click OK to save your changes.
STEP 5 | Add or edit a Security policy rule (Policies > Security) that allows users to access the SaaS
application for which you are configuring this header insertion rule.
1. Choose the URL Filtering profile (Actions > URL Filtering) that you edited or created in
Step 2.
2. Click OK to save and then Commit your changes.
STEP 6 | Verify that access to the SaaS application is working in the way you expect. From an
endpoint that is connected to your network:
1. Try to access an account or content that you expect to be able to access. If you cannot
access the SaaS account or content, then the configuration is not working.
2. Try to access an account or content that you expect will be blocked. If you can access
the SaaS account or content, then the configuration is not working.
3. If both of the previous steps work as expected, then you can View Logs (if you
configured logging in step 4.6) and you should see the recorded HTTP header insertion
activity.
PAN-OS® Administrator’s Guide Version 10.2 934 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
934 | App-ID
Maintain Custom Timeouts for Data Center Applications
Easily maintain custom timeouts for applications as you move from a port-based policy to an
application-based policy. Use this method to maintain custom timeouts instead of overriding AppID (losing application visibility) or creating a custom App-ID (expending time and research).
To get started, configure custom timeout settings as part of a service object:
Then add the service object in a policy rule to apply the custom timeouts to the application(s) the
rule enforces.
The following steps describe how apply custom timeouts to applications; to apply custom
timeouts to user groups, you can follow the same steps but just make sure to add the service
object to the security policy rule that enforces the users to whom you want the timeout to apply.
STEP 1 | Select Objects > Services to add or modify a service object.
You can also create service objects as you are defining match criteria for a security policy rule:
select Policies > Security > Service/URL Category and Add a new Service object to apply to
the application traffic the rule governs.
STEP 2 | Select the protocol for the service to use (TCP or UDP).
STEP 3 | Enter the destination port number or a range of port numbers used by the service.
STEP 4 | Define the session timeout for the service.
• Inherit from application (default)—No service-based timeouts are applied; instead, apply
the application timeout.
• Override—Define a custom session timeout for the service.
STEP 5 | If you chose to override the application timeout and define a custom session timeout,
continue to:
• Enter a TCP Timeout value to set the Maximum length of time in seconds that a TCP
session can remain open after data transmission has started. When this time expires, the
session closes. The value range is 1 - 604800, and the default value is 3600 seconds.
• Enter a TCP Half Closed value to set the maximum length of time in seconds that a
session remains in the session table between receiving the first FIN packet and receiving
PAN-OS® Administrator’s Guide Version 10.2 935 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
935 | App-ID
the second FIN packet or RST packet. If the timer expires, the session closes. The value
range is 1 - 604800, and the default value is 120 seconds.
• Enter a TCP Wait Time value to set the maximum length of time in seconds that a session
remains in the session table after receiving the second FIN packet or a RST packet. When
the timer expires, the session closes. The value range is 1 - 600, and the default value is
15 seconds.
STEP 6 | Click OK to save the service object.
STEP 7 | Select Policies > Security and Add or modify a policy rule to govern the application traffic
you want to control.
STEP 8 | Select Service/URL Category and Add the service object you just created to the security
policy rule.
STEP 9 | Click OK and Commit your changes.
PAN-OS® Administrator’s Guide Version 10.2 936 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
936 | Device-ID
• Device-ID Overview
• Prepare to Deploy Device-ID
• Configure Device-ID
• Manage Device-ID
• CLI Commands for Device-ID
937 | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
937 | Device-ID
Device-ID Overview
According to the 2020 Unit 42 IoT Threat Report, 30% of all network-connected devices in an
average enterprise are IoT. This presents a constantly growing area of risk with many possibilities
for exploitation by malicious users. Additionally, once you identify these devices, how do you
secure them from vulnerabilities such as outdated operating software? Using Device-ID™
on your firewalls, you can get device context for events on your network, obtain policy rule
recommendations for those devices, write policy rules based on devices, and enforce Security
policy based on the recommendations.
Similar to how User-ID provides user-based policy and App-ID provides app-based policy,
Device-ID provides policy rules that are based on a device, regardless of changes to its IP
address or location. By providing traceability for devices and associating network events with
specific devices, Device-ID allows you to gain context for how events relate to devices and write
policies that are associated with devices, instead of users, locations, or IP addresses, which can
change over time. You can use Device-ID in Security, Decryption, Quality of Service (QoS), and
Authentication policies.
For Device-ID features to be available on a firewall, you must purchase an IoT Security
subscription and select the firewall during the IoT Security onboarding process. There are two
types of IoT Security subscriptions:
• IoT Security Subscription
• IoT Security – Doesn’t Require Data Lake (DRDL) Subscription
With the first subscription, firewalls send data logs to the logging service, which streams them
to IoT Security for analysis and to a Strata Logging Service instance for storage. The data lake
instance can either be a new or existing one. With the second subscription, firewalls send data
logs to the logging service, which streams them to IoT Security for analysis but not to a Strata
Logging Service instance for storage. It’s important to note that both IoT Security and IoT Security
(DRDL) subscriptions provide the same functionality in terms of IoT Security and Device-ID.
To permit connections to IoT Security, a firewall needs a device license; and to permit connections
to the logging service, it needs a logging service license. A firewall also requires a device
certificate to authenticate itself when connecting to IoT Security and the logging service.
If you use PAN-OS version 8.1.0 through PAN-OS 9.1.x on a firewall, the IoT Security license
provides device classification, behavior analysis, and threat analysis for your devices. If you use
PAN-OS 10.0 or later, you can use Device-ID to obtain IP address-to-device mappings to view
device context for network events, use IoT Security to obtain policy rule recommendations for
these devices, and gain visibility for devices in reports and the ACC.
You can create a device-based Security policy on any Panorama or firewall that uses PANOS version 10.0 or later. To enforce the Security policy, the device must have a valid IoT
Security license.
To identify and classify devices, the IoT Security app uses metadata from logs, network protocols,
and sessions on the firewall. This does not include private or sensitive information or data that
is not relevant for device identification. Metadata also forms the basis of the expected behavior
for the device, which then establishes the criteria for the policy rule recommendation that defines
what traffic and protocols to allow for that device.
PAN-OS® Administrator’s Guide Version 10.2 938 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
938 | Device-ID
When a firewall imports security policy rule recommendations and IP address-to-device mappings
from IoT Security, the firewall sends its device certificate to an edge server to authenticate itself.
The edge server authenticates itself to the firewall by sending its own certificate. The firewall uses
Online Certificate Status Protocol (OCSP) to validate the server’s certificate by checking it against
the following sites using HTTP on TCP port 80:
• *.o.lencr.org
• x1.c.lencr.org
Panorama performs the same check to validate the edge server’s certificate when Panorama
imports policy rule recommendations from IoT Security.
After IoT Security identifies and classifies the devices in your network using the Palo Alto
Networks firewalls already in your network, so you don’t have to implement new devices or
third-party solutions, Device-ID can leverage this data to match devices with policy rules and
provide device context for network events. Through the visibility that the firewall or Panorama
provides for traffic, apps, users, devices, and threats, you can instantly trace network events back
to individual devices and obtain Security policy rule recommendations for securing those devices.
All firewall platforms that support PAN-OS 10.0 and support Device-ID and the IoT
Security app with the exception of the VM-50 series, the VM-200, and the CN series.
There are six levels of classification (also known as attributes) for devices:
Attribute Example
Category Printer
Profile Sharp Printer
Model MX-6070N
OS Version ThreadX 5
OS Family ThreadX RTOS
Vendor SHARP Corporation
To obtain policy rule recommendations for devices in your network, the firewall observes traffic
to generate Enhanced Application logs (EALs). The firewall then forwards the EALs to the logging
service. The IoT Security app receives logs from the logging service for analysis, provides IP
address-to-device mappings, and generates the latest policy rule recommendations for your
devices. Using the IoT Security app, you can review these policy rule recommendations and create
a Security policy for these devices. After you activate the policy rules in the IoT Security app,
import them to the firewall or Panorama and commit your Security policy.
The firewall must be able to observe DHCP broadcast and unicast traffic on your network
to identify devices with dynamically assigned network settings. IoT Security also supports
static IP devices. The more traffic the firewall can observe, the more accurate the policy rule
recommendations are for the device and the more rapid and accurate the IP address-to-device
mappings are for the device. When a device sends DHCP traffic to obtain an IP address, the
PAN-OS® Administrator’s Guide Version 10.2 939 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
939 | Device-ID
firewall observes this type of request, it generates EALs to send to the logging service, where IoT
Security accesses them for analysis.
To observe traffic on an L2 interface, you must configure a VLAN for that interface. By
allowing the firewall to treat the interface as an L3 interface for a DHCP relay, it can
observe the DHCP broadcast traffic without impacting traffic or performance.
Because the firewall needs to both detect the devices based on their traffic and then enforce
Security policy for those devices, the firewall acts as both a sensor to collect metadata from
devices and an enforcer by enforcing your Security policy for the devices. The IoT Security app
automatically detects new devices as soon as they send DHCP traffic and can identify 95% of
devices within the first week.
Each application has an individual recommendation that you import to the firewall or Panorama
as a rule. When you import the recommendation, the firewall or Panorama creates at least two
objects to define the device behavior from the recommendation:
• A source device object that identifies the device where the traffic originates
• One or more destination objects that identify the permitted destinations for the traffic, which
can be a device, IP address, or Fully Qualified Domain Name (FQDN)
If any of the device objects already exist on the firewall or Panorama, the firewall or Panorama
updates the device object instead of creating a new one. You can use these device objects in
Security, authentication, decryption, and Quality of Service (QoS) policy rules.
Additionally, the firewall assigns two tags to each rule:
• One that identifies the source device, including the category (such as NetworkDevice -
TrendNet).
• One that indicates that the rule is an IoT policy rule recommendation
(IoTSecurityRecommended).
Because the tags that the firewall assigns to the rule are the only way to restore your
mappings if they become out of sync, do not edit or remove the tags.
For optimal deployment and operation of Device-ID, we recommend the following best practices:
• Deploy Device-ID on firewalls that are centrally located in your network. For example, if you
have a large environment, deploy Device-ID on a firewall that is upstream from the IP address
management (IPAM) device. If you have a small environment, deploy Device-ID on a firewall
that is acting as a DHCP server.
• During initial deployment, allow Device-ID to collect metadata from your network for at least
fourteen days. If devices are not active daily, the identification process may take longer.
• Write device-based policy in order of your most critical devices to least critical. Prioritize by:
1. Class (secure networked devices first)
2. Critical devices (such as servers or MRI machines)
3. Environment-specific devices (such as fire alarms and badge readers)
4. Consumer-facing IoT devices (such as a smart watch or smart speaker)
• Enable Device-ID on a per-zone basis for internal zones only.
PAN-OS® Administrator’s Guide Version 10.2 940 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
940 | Device-ID
Prepare to Deploy Device-ID
To prepare your network for Device-ID deployment, complete the following predeployment tasks
to enable your firewall to generate and send Enhanced Application logs (EALs) to the logging
service for processing and analysis by IoT Security for policy rule recommendation generation.
STEP 1 | If you have not already done so, install a device certificate on your firewalls or Panorama.
The device certificate authenticates the firewall when connecting to the logging service and
IoT Security.
If you use Panorama to manage multiple firewalls, Palo Alto Networks strongly
recommends upgrading all firewalls in your Device-ID deployment to PAN-OS 10.0
or a later version. If you create a rule that uses Device as a match criteria and
Panorama pushes the rule to a firewall that uses PAN-OS 9.1 or an earlier version, the
firewall omits the Device match criteria because it is not supported, which may cause
issues with policy rule traffic matching.
STEP 2 | Install a device license and a logging service license on your firewalls.
To do this, click Device > Licenses, and then select Retrieve license keys from license server
in the License Management section. This installs the licenses for the logging service and IoT
Security on the firewall.
The logging service license permits a firewall to connect to the logging service.
The device license permits a firewall to connect to IoT Security.
STEP 3 | (L2 interfaces only) Create a VLAN interface for each L2 interface so the firewall can observe
the DHCP broadcast traffic.
STEP 4 | (Optional) Configure a service route to allow the necessary traffic for Device-ID and IoT
Security.
By default, the firewall uses the management interface. To use a different interface, complete
the following steps.
1. Select Device > Setup > Services then select Service Route Configuration.
2. Customize a service route.
3. Select the IPv4 protocol.
Device-ID and IoT Security do not support IPv6.
4. Select Data Services in the Service column.
5. Select a Source Interface and Source Address.
6. Click OK twice.
PAN-OS® Administrator’s Guide Version 10.2 941 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
941 | Device-ID
STEP 5 | Use App-IDs to allow the necessary traffic for Device-ID and IoT Security.
Purpose App-ID
Retrieve policy rule recommendations and allow
traffic between the IoT Security app and your firewall
or Panorama.
paloalto-iot-security
Allow traffic for all EALs and all session logs. paloalto-logging-service
Retrieve IoT Security dynamic updates and Device
Dictionary updates.
paloalto-updates
If you have a third-party firewall between a Palo Alto Networks next-generation
firewall using Device-ID and the internet, verify that the next-generation firewall can
access the appropriate regional edge services FQDN; for example, iot.servicesedge.paloaltonetworks.com:443 if it’s in the Americas region, or
eu.iot.services-edge.paloaltonetworks.com:443 if it’s in the EU
region.
STEP 6 | If there’s a third-party firewall between the internet and Panorama and Panorama-managed
next-generation firewalls, make sure it allows the necessary traffic for Device-ID and IoT
Security.
Purpose Address TCP Port
(PAN-OS versions 10.0.3
and later) Receive the
regional FQDN allowing
next-generation firewalls
to retrieve IP address-todevice mappings and policy
rule recommendations from
IoT Security.
enforcer.iot.servicesedge.paloaltonetworks.com
443
(PAN-OS versions 10.0.0
and later) Let nextgeneration firewalls
receive policy rule
recommendations and
IP address-to-device
mappings from IoT
Security.
United States
iot.servicesedge.paloaltonetworks.com
Canada
ca.iot.servicesedge.paloaltonetworks.com
EU region
eu.iot.servicesedge.paloaltonetworks.com
Asia-Pacific region
443
PAN-OS® Administrator’s Guide Version 10.2 942 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
942 | Device-ID
Purpose Address TCP Port
apac.iot.servicesedge.paloaltonetworks.com
Japan
jp.iot.servicesedge.paloaltonetworks.com
Australia
au.iot.servicesedge.paloaltonetworks.com
(PAN-OS versions 10.0.0
and later) Let nextgeneration firewalls
download device dictionary
files from the update
server.
updates.paloaltonetworks.com 443
(PAN-OS versions 10.0.0
and later) Let Panorama
send queries for logs to the
logging service.
United States
iot.servicesedge.paloaltonetworks.com
Canada
ca.iot.servicesedge.paloaltonetworks.com
EU region
eu.iot.servicesedge.paloaltonetworks.com
Asia-Pacific region
apac.iot.servicesedge.paloaltonetworks.com
Japan
jp.iot.servicesedge.paloaltonetworks.com
Australia
au.iot.servicesedge.paloaltonetworks.com
443
(IoT Security subscription
+ Strata Logging Service)
See TCP Ports and FQDNs Required for Strata Logging Service.
PAN-OS® Administrator’s Guide Version 10.2 943 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
943 | Device-ID
Purpose Address TCP Port
Forward logs to Strata
Logging Service.
PAN-OS versions 10.0.0 - 10.0.2 connect to the edge services FQDN in the Americas
region by default (iot.services-edge.paloaltonetworks.com). For
firewalls running these PAN-OS versions to connect to the edge services FQDN in
other regions, you must manually configure it (see the FQDNs in the next step). For
PAN-OS versions 10.0.3 and later, firewalls automatically discover the correct FQDN
to use based on the region set during the IoT Security onboarding process. There is no
need to set it manually.
STEP 7 | If there’s a third-party firewall between the internet and next-generation firewalls (without
Panorama), make sure it allows the necessary traffic for Device-ID and IoT Security.
Purpose Address TCP Port
(PAN-OS versions 10.0.3 and later)
Receive the regional FQDN allowing
next-generation firewalls to retrieve
IP address-to-device mappings and
policy rule recommendations from
IoT Security.
enforcer.iot.servicesedge.paloaltonetworks.com
443
(PAN-OS versions 10.0.0 and later)
Let next-generation firewalls receive
policy rule recommendations and IP
address-to-device mappings from IoT
Security.
United States
iot.servicesedge.paloaltonetworks.com
Canada
ca.iot.servicesedge.paloaltonetworks.com
EU region
eu.iot.servicesedge.paloaltonetworks.com
Asia-Pacific region
apac.iot.servicesedge.paloaltonetworks.com
Japan
jp.iot.servicesedge.paloaltonetworks.com
Australia
au.iot.servicesedge.paloaltonetworks.com
443
PAN-OS® Administrator’s Guide Version 10.2 944 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
944 | Device-ID
Purpose Address TCP Port
(PAN-OS versions 10.0.0 and
later) Let next-generation firewalls
download device dictionary files from
the update server.
updates.paloaltonetworks.com 443
(IoT Security subscription + Strata
Logging Service) Forward logs to
Strata Logging Service.
See TCP Ports and FQDNs Required for Strata Logging
Service.
STEP 8 | Configure your firewall to observe and generate logs for DHCP traffic then forward the logs
for processing and analysis by IoT Security.
• If the firewall is acting as a DHCP server:
1. Enable Enhanced Application logging.
2. Create a Log Forwarding profile to forward the logs to the logging service for processing.
3. Enable the DHCP Broadcast Session option (Device > Setup > Session > Session
Settings).
This setting is supported from PAN-OS 10.2.4 on the PA-3200, PA-5200,
PA-5450, and PA-7000 series and on all other firewalls running any version of
PAN-OS 10.2.
4. Create a Security policy rule to allow dhcp as the Application type.
• If the firewall is not a DHCP server, configure an interface as a DHCP relay agent so that
the firewall can generate EALs for the DHCP traffic it receives from clients.
• If your DHCP server is on the same network segment as the interface your firewall, deploy
a virtual wire interface in front of the DHCP server to ensure the firewall generates EALs
for all packets in the initial DHCP exchange with minimal performance impact.
1. Configure a virtual wire interface with corresponding zones and enable the Multicast
Firewalling option (Network > Virtual Wires > Add).
2. Configure a rule to allow DHCP traffic to and from the DHCP server between the virtual
wire zones. The policy must allow all existing traffic that the server currently observes
and use the same Log Forwarding profile as the rest of your rules.
3. To allow the DHCP servers to check if an IP address is active before assigning it as a
lease to a new request, configure a rule to allow pings from the DHCP server to the rest
of the subnet.
4. Configure a rule to allow all other traffic to and from the DHCP server that does not
forward logs for traffic matches.
5. Configure the DHCP server host to use the first virtual wire interface and the network
switch to use the second virtual wire interface. To minimize cabling, you can use an
PAN-OS® Administrator’s Guide Version 10.2 945 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
945 | Device-ID
isolated VLAN in the switching infrastructure instead of connecting the DHCP server
host directly to the firewall.
• If you want to use a tap interface to gain visibility into DHCP traffic that the firewall doesn’t
usually observe due to the current configuration or topology of the network, use the
following configuration as a best practice.
1. Configure a tap interface and corresponding zone.
2. Configure a rule to match DHCP traffic that uses the same Log Forwarding profile as the
rest of your rules.
3. To minimize the session load on the firewall, configure a rule to drop all other traffic.
4. Connect the tap interface to the port mirror on the network switch.
• If you want to collect data about devices whose network traffic isn’t visible to a firewall,
use Encapsulated Remote Switched Port Analyzer (ERSPAN) to send mirrored traffic from a
network switch through a Generic Routing Encapsulation (GRE) tunnel to the firewall.
STEP 9 | Apply a Log Forwarding profile to your Security policy rules.
Apply a predefined Log Forwarding profile for IoT Security to your rules—or update an existing
profile or create a new one—so that they forward the required types of logs to the logging
service.
PAN-OS® Administrator’s Guide Version 10.2 946 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
946 | Device-ID
Configure Device-ID
Complete the following tasks to import the IP address-to-device mappings and policy rule
recommendations from IoT Security to your firewall or Panorama.
If you use Panorama to manage multiple firewalls, Palo Alto Networks strongly
recommends upgrading all firewalls in your Device-ID deployment to PAN-OS 10.0 or a
later version. If you create a rule that uses Device as a match criteria and Panorama
pushes the rule to a firewall that uses PAN-OS 9.1 or an earlier version, the firewall omits
the Device match criteria because it is not supported, which may cause issues with
policy rule traffic matching.
STEP 1 | Activate your IoT Security license on the hub.
1. Follow the instructions that you received in your email to activate your IoT Security
license.
2. Initialize your IoT Security app. For more information, refer to Get Started with IoT
Security and IoT Security Best Practices.
3. Apply the license to the firewalls you want to use to enforce the IoT Security policy.
4. Refresh your license on the firewall or Panorama.
STEP 2 | Define your IoT Security policy on the IoT Security app.
1. On the IoT Security app, select the source device object.
2. Create a new set of policy rules for the source device object.
For more information about creating security policies with the IoT Security app, refer to
Recommend Security Policies.
3. Activate the policy rules to confirm your changes.
PAN-OS® Administrator’s Guide Version 10.2 947 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
947 | Device-ID
STEP 3 | Import the IP address-to-device mappings and policy rule recommendations to the firewall or
Panorama.
1. Import the policy rule recommendation.
• On the firewall, select Device > Policy Recommendation > IoT.
• For Panorama, select Panorama > Policy Recommendation > IoT then push the policy
rules to the firewalls that Panorama manages.
After you push the policy to the firewalls, you must Sync Policy Rules on the
firewalls to create the policy rule recommendation-to-policy rule mapping.
When you select Policy Recommendation, the firewall or Panorama communicates
with IoT Security to obtain the latest policy rule recommendations. The policy rule
recommendations are not cached on the firewall or Panorama.
Because IoT Security creates the policy rule recommendation using the trusted
behaviors for the device, the default action for the rule is allow.
2. Select the Source Device Profile.
3. Verify that the Destination Device Profile and permitted Applications are correct.
4. Select Import Policy Rules to import the policy rules.
5. (Panorama only) Select the Location of the device group where you want to import the
policy rules.
6. Enter a Name for the policy rules.
7. (Panorama only) Select the Destination Type (Pre-Rulebase or Post-Rulebase).
8. Select After Rule to define the placement of the rule in the rulebase.
• No Rule Selection—Places the rule at the top of the rulebase.
• Default One—Places the rule after the listed rule.
In your Security policy, Device-ID rules must precede any existing rules that
apply to the devices.
9. Repeat this process for each policy rule recommendation to create rules to allow access
for each device object to the necessary destination(s).
10. Click OK and Commit your changes.
STEP 4 | Enable Device-ID in each zone where you want to use Device-ID to detect devices and
enforce your Security policy.
By default, Device-ID maps all subnetworks in the zones where you enable it. You can modify
which subnetworks Device-ID maps in the Include List and Exclude List.
As a best practice, enable Device-ID in the source zone to detect devices and enforce
Security policy. Only enable Device-ID for internal zones.
1. Select Network > Zones.
2. Select the zone where you want to enable Device-ID.
3. Enable Device Identification then click OK.
PAN-OS® Administrator’s Guide Version 10.2 948 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
948 | Device-ID
STEP 5 | Commit your changes.
STEP 6 | Verify your Security policy is correct.
1. Select Policies then select the rule you created from the policy rule recommendation.
IoT Security assigns a Description that contains the source device object and Tags
to identify the source device object and that this rule is a recommendation from IoT
Security.
Device object names must be unique.
2. Select the Source tab, then verify the Source Device Profile.
3. Select the Destination tab and verify the Destination Device Profile.
4. Select the Application tab and verify the Applications.
5. Select the Actions tab and verify the Action (default is Allow).
6. Use Explore to verify Strata Logging Service receives your logs and review which logs it
receives.
STEP 7 | Create custom device objects for any devices that do not have IoT Security policy rule
recommendations.
All device object names must be unique.
For example, you cannot secure traditional IT devices such as laptops and smartphones using
policy rule recommendations, so you must manually create device objects for these types of
devices to use in your Security policy. For more information on custom device objects, see
Manage Device-ID.
STEP 8 | Use the device objects to enforce policy rules and to monitor and identify potential issues.
The following list includes some example use cases for device objects.
• Use source device objects and destination device objects in Security, Authentication, QoS,
& decryption policies.
• Use the decryption log to identify failures and which assets are the most critical to decrypt.
• View device object activity in ACC to track new devices and device behavior.
• Use device objects to create a custom report (for example, for incident reports or audits).
PAN-OS® Administrator’s Guide Version 10.2 949 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
949 | Device-ID
Manage Device-ID
Perform the following tasks as needed to ensure your policy rule recommendations and device
objects are current or to restore policy rule recommendation mappings.
STEP 1 | Update your policy rule recommendation whenever the New Updates Available column
displays Yes for that recommendation.
As devices gain new capabilities, IoT Security updates the policy rule recommendations to
advise what additional traffic or protocols the firewall or Panorama should allow. Check IoT
Security daily for updates and update your policy rule recommendations as soon as possible.
1. On the IoT Security app, Edit the policy rules then click Next.
2. Select the new recommendation then click Next.
3. Save your changes.
4. On the firewall or Panorama, click Import Policy Rules then click Yes to confirm that you
want to overwrite the current rule.
This action overwrites the recommendation for the rule, not the rule itself.
5. (Panorama only) Repeat the previous step for all device groups.
6. Commit your changes.
STEP 2 | Review, update, and maintain the device objects in the Device Dictionary.
You must create device objects for any devices that do not have an IoT Security policy
rule recommendation. For example, you cannot secure traditional IT devices such as
laptops and smartphones using IoT Security policy rule recommendations, so you must
create device objects for these types of devices and use them in your Security policy to
secure these devices.
1. Select Objects > Devices.
2. Add a device object.
3. Browse the list or Search using keywords.
The search results can include multiple types of device object attributes (for example,
both Category and Profile).
4. To add a custom device object, enter a Name and optionally a Description for the device
object.
Always use a unique name for each device object. Do not change the tags in the
description for device objects from policy rule recommendations.
5. (Panorama only) Select the Shared option to make this device object available to other
device groups.
6. Select the attributes for the device object (Category, OS, Profile, Osfamily, Model, and
Vendor).
7. Click OK to confirm your changes.
PAN-OS® Administrator’s Guide Version 10.2 950 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
950 | Device-ID
STEP 3 | In some cases (for example, if you restore a previous configuration), the policy rule
recommendation-to-policy rule mappings may become out of sync. You must also sync the
mappings on each firewall after you push the policy rules from Panorama to the firewalls that
Panorama manages. To sync the mappings:
• On the firewall, select Device > Policy Recommendation > IoT > Sync Policy Rules
• For Panorama, select Panorama > Policy Recommendation > IoT > Sync Policy Rules.
The firewall or Panorama scans all of the rules in the rulebase to check for tags that identify
a rule as an IoT Security policy rule recommendation, obtains the source device object
information, and repopulates the local policy rule recommendation database.
STEP 4 | Delete any policy rule recommendations that are no longer needed.
If a policy rule recommendation no longer applies, you can remove the policy rule
recommendation. You must also remove the rule for the policy rule recommendation to
enforce the updated Security policy.
1. On the IoT Security app, select Delete.
2. Click Mark as Removed to select this recommendation for removal.
3. Remove the mapping.
• On the firewall, select Device > Policy Recommendation > IoT > Remove Policy
Mapping.
• For Panorama, select Device > Policy Recommendation > IoT > Remove Policy
Mapping then select the Location from which you want to remove the mapping.
4. Click Yes to confirm the mapping removal.
5. Select Policies > Security. For Panorama, select Policies > Security > Pre-Rules/PostRules.
6. Select the rule for the policy rule recommendation you want to remove then select
Delete.
7. Commit your changes.
STEP 5 | Use CLI commands to troubleshoot any issues between the firewall and IoT Security.
PAN-OS® Administrator’s Guide Version 10.2 951 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
951 | Device-ID
CLI Commands for Device-ID
Use the following CLI commands to view information for troubleshooting any issues between the
firewall and IoT Security. In general, CLI commands that include eal show counters for outgoing
data and CLI commands that include icd show counters for incoming data.
Example Command
View Enhanced Application Logging (EAL)
counters, such as the number of connections
between the firewall and the Strata Logging
Service and the volume of the logs.
show iot eal all
View more details about the connection between
the firewall and Strata Logging Service.
show iot eal conn
View a summary of the EAL counters by plane
(dataplane or management plane), such as the
PAN-OS version and serial number.
show iot eal dpi-eal
View EAL counters by plane (dataplane or
management plane) and by protocol.
show iot eal dpi-stats all
View EAL counters by protocol. show iot eal dpi-stats subtype
dhcp|http
View a summary of Host Information Profile (HIP)
Match report counters.
show iot eal hipreport-eal
View EAL log response time counters. show iot eal response-time
View details for the health of the connection
to the edge service between the firewall and
the IoT Security app and counters for the IP
address-to-device mappings and policy rule
recommendations.
show iot icd statistics all
View counters for the connection to the edge
service.
show iot icd statistics conn
View counters for the IP address-to-device
mappings.
show iot icd statistics
verdict
View all IP address-to-device mappings on the
firewall.
show iot ip-device-mapping-mp
all
View the IP address-to-device mapping for a
specific IP address.
show iot ip-device-mapping-mp
ip IP-address
PAN-OS® Administrator’s Guide Version 10.2 952 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
952 | Device-ID
Example Command
View a list of IP address-to-device mappings on
the data plane.
show iot ip-device-mapping all
Clear the IP address-to-device mappings on the
management plane.
debug iot clear-all type
device
Clear the IP address-to-device mappings on the
data plane.
clear user-cache all
PAN-OS® Administrator’s Guide Version 10.2 953 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
953 | Device-ID
PAN-OS® Administrator’s Guide Version 10.2 954 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
954 | Quality of Service
Quality of Service (QoS) is a set of technologies that work on a network to guarantee its ability
to dependably run high-priority applications and traffic under limited network capacity. QoS
technologies accomplish this by providing differentiated handling and capacity allocation to
specific flows in network traffic. This enables the network administrator to assign the order in
which traffic is handled, and the amount of bandwidth afforded to traffic.
Palo Alto Networks Application Quality of Service (QoS) provides basic QoS applied to networks
and extends it to provide QoS to applications and users.
Use the following topics to learn about and configure Palo Alto Networks application-based QoS:
• QoS Overview
• QoS Concepts
• Configure QoS
• Configure Lockless QoS
• Configure QoS for a Virtual System
• Enforce QoS Based on DSCP Classification
• QoS Use Cases
Use the Palo Alto Networks product comparison tool to view the QoS features supported on
your firewall model. Select two or more product models and click Compare Now to view QoS
feature support for each model (for example, you can check if your firewall model supports QoS
on subinterfaces and if so, the maximum number of subinterfaces on which QoS can be enabled).
QoS on Aggregate Ethernet (AE) interfaces is supported on PA-7000 Series, PA-5400 Series,
PA-5200 Series, PA-3400 Series, PA-3200 Series, and PA-400 Series firewalls running PAN-OS
7.0 or later release versions.
955 | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
955 | Quality of Service
QoS Overview
Use QoS to prioritize and adjust quality aspects of network traffic. You can assign the order in
which packets are handled and allot bandwidth, ensuring preferred treatment and optimal levels
of performance are afforded to selected traffic, applications, and users.
Service quality measurements subject to a QoS implementation are bandwidth (maximum rate
of transfer), throughput (actual rate of transfer), latency (delay), and jitter (variance in latency).
The capability to shape and control these service quality measurements makes QoS of particular
importance to high-bandwidth, real-time traffic such as voice over IP (VoIP), video conferencing,
and video-on-demand that has a high sensitivity to latency and jitter. Additionally, use QoS to
achieve outcomes such as the following:
• Prioritize network and application traffic, guaranteeing high priority to important traffic or
limiting non-essential traffic.
• Achieve equal bandwidth sharing among different subnets, classes, or users in a network.
• Allocate bandwidth externally or internally or both, applying QoS to both upload and download
traffic or to only upload or download traffic.
• Ensure low latency for customer and revenue-generating traffic in an enterprise environment.
• Perform traffic profiling of applications to ensure bandwidth usage.
QoS implementation on a Palo Alto Networks firewall begins with three primary configuration
components that support a full QoS solution: a QoS Profile, a QoS Policy, and setting up the QoS
Egress Interface. Each of these options in the QoS configuration task facilitate a broader process
that optimizes and prioritizes the traffic flow and allocates and ensures bandwidth according to
configurable parameters.
The figure QoS Traffic Flow shows traffic as it flows from the source, is shaped by the firewall
with QoS enabled, and is ultimately prioritized and delivered to its destination.
Figure 6: QoS Traffic Flow
The QoS configuration options allow you to control the traffic flow and define it at different
points in the flow. The figure QoS Traffic Flow indicates where the configurable options define
the traffic flow. A QoS policy rule allows you to define traffic you want to receive QoS treatment
PAN-OS® Administrator’s Guide Version 10.2 956 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
956 | Quality of Service
and assign that traffic a QoS class. The matching traffic is then shaped based on the QoS profile
class settings as it exits the physical interface.
Each of the QoS configuration components influence each other and the QoS configuration
options can be used to create a full and granular QoS implementation or can be used sparingly
with minimal administrator action.
When a queue is filling faster than it can be emptied, the device has two choices as to where to
drop traffic. It can wait until the queue is full and simply drop packets as they arrive (tail dropping),
or it can detect incipient congestion and proactively begin to drop packets based on a probability
function that is tied to an average depth of the queue. This technique is called random early drop
(RED). PAN-OS uses a weighted RED (WRED) algorithm.
Each firewall model supports a maximum number of ports that can be configured with QoS. Refer
to the spec sheet for your firewall model or use the product comparison tool to view QoS feature
support for two or more firewalls on a single page.
PAN-OS® Administrator’s Guide Version 10.2 957 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
957 | Quality of Service
QoS Concepts
Use the following topics to learn about the different components and mechanisms of a QoS
configuration on a Palo Alto Networks firewall:
• QoS for Applications and Users
• QoS Policy
• QoS Profile
• QoS Classes
• QoS Priority Queuing
• QoS Bandwidth Management
• QoS Egress Interface
• QoS for Clear Text and Tunneled Traffic
QoS for Applications and Users
A Palo Alto Networks firewall provides basic QoS, controlling traffic leaving the firewall according
to network or subnet, and extends the power of QoS to also classify and shape traffic according
to application and user. The Palo Alto Networks firewall provides this capability by integrating the
features App-ID and User-ID with the QoS configuration. App-ID and User-ID entries that exist to
identify specific applications and users in your network are available in the QoS configuration so
that you can easily specify applications and users for which you want to manage and/or guarantee
bandwidth.
QoS Policy
Use a QoS policy rule to define traffic to receive QoS treatment (either preferential treatment or
bandwidth-limiting) and assign such traffic a QoS class of service.
Define a QoS policy rule to match to traffic based on:
• Applications and application groups.
• Source zones, source addresses, and source users.
• Destination zones and destination addresses.
• Services and service groups limited to specific TCP and/or UDP port numbers.
• URL categories, including custom URL categories.
• Differentiated Services Code Point (DSCP) and Type of Service (ToS) values, which are used to
indicate the level of service requested for traffic, such as high priority or best effort delivery.
You cannot apply DSCP code points or QoS to SSL Forward Proxy, SSL Inbound
Inspection, and SSH Proxy traffic.
Set up multiple QoS policy rules (Policies > QoS) to associate different types of traffic with
different QoS Classes of service.
PAN-OS® Administrator’s Guide Version 10.2 958 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
958 | Quality of Service
Because QoS is enforced on traffic as it egresses the firewall, the QoS policy rule is applied to
traffic after the firewall has enforced all other security policy rules, including Network Address
Translation (NAT) rules. However, the firewall evaluates QoS rules based on the contents of
the original packet, such as pre-NAT source IP, pre-NAT source zone, pre-NAT destination IP,
and post-NAT destination zone. Therefore, do not configure the QoS policy with the post-NAT
addresses.
QoS Profile
Use a QoS profile to define values of up to eight QoS Classes contained within that single profile.
With a QoS profile, you can define QoS Priority Queuing and QoS Bandwidth Management for
QoS classes. Each QoS profile allows you to configure individual bandwidth and priority settings
for up eight QoS classes, as well as the total bandwidth allotted for the eight classes combined.
Attach the QoS profile (or multiple QoS profiles) to a physical interface to apply the defined
priority and bandwidth settings to the traffic exiting that interface.
A default QoS profile is available on the firewall. The default profile and the classes defined in the
profile do not have predefined maximum or guaranteed bandwidth limits.
To define priority and bandwidth settings for QoS classes, see Step Add a QoS profile.
QoS Classes
A QoS class determines the priority and bandwidth for traffic matching a QoS Policy rule. You can
use a QoS Profile to define QoS classes. There are up to eight definable QoS classes in a single
QoS profile. Unless otherwise configured, traffic that does not match a QoS class is assigned a
class of 4.
QoS Priority Queuing and QoS Bandwidth Management, the fundamental mechanisms of a QoS
configuration, are configured within the QoS class definition (see Step 4). For each QoS class, you
can set a priority (real-time, high, medium, and low) and the maximum and guaranteed bandwidth
for matching traffic. QoS priority queuing and bandwidth management determine the order of
traffic and how traffic is handled upon entering or leaving a network.
PAN-OS® Administrator’s Guide Version 10.2 959 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
959 | Quality of Service
QoS Priority Queuing
One of four priorities can be enforced for a QoS class: real-time, high, medium, and low. Traffic
matching a QoS policy rule is assigned the QoS class associated with that rule, and the firewall
treats the matching traffic based on the QoS class priority. Packets in the outgoing traffic flow are
queued based on their priority until the network is ready to process the packets. Priority queuing
allows you to ensure that important traffic, applications, and users take precedence. Real-time
priority is typically used for applications that are particularly sensitive to latency, such as voice and
video applications.
QoS Bandwidth Management
QoS bandwidth management allows you to control traffic flows on a network so that traffic does
not exceed network capacity (resulting in network congestion) and also allows you to allocate
bandwidth for certain types of traffic and for applications and users. With QoS, you can enforce
bandwidth for traffic on a narrow or a broad scale. A QoS profile allows you to set bandwidth
limits for individual QoS classes and the total combined bandwidth for all eight QoS classes. As
part of the steps to Configure QoS, you can attach the QoS profile to a physical interface to
enforce bandwidth settings on the traffic exiting that interface—the individual QoS class settings
are enforced for traffic matching that QoS class (QoS classes are assigned to traffic matching QoS
Policy rules) and the overall bandwidth limit for the profile can be applied to all clear text traffic,
specific clear text traffic originating from source interfaces and source subnets, all tunneled traffic,
and individual tunnel interfaces. You can add multiple profile rules to a single QoS interface to
apply varying bandwidth settings to the traffic exiting that interface.
The following fields support QoS bandwidth settings:
PAN-OS® Administrator’s Guide Version 10.2 960 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
960 | Quality of Service
• Egress Guaranteed—The amount of bandwidth guaranteed for matching traffic. When the
egress guaranteed bandwidth is exceeded, the firewall passes traffic on a best-effort basis.
Bandwidth that is guaranteed but is unused continues to remain available for all traffic.
Depending on your QoS configuration, you can guarantee bandwidth for a single QoS class, for
all or some clear text traffic, and for all or some tunneled traffic.
Example:
Class 1 traffic has 5 Gbps of egress guaranteed bandwidth, which means that 5 Gbps is
available but is not reserved for class 1 traffic. If Class 1 traffic does not use or only partially
uses the guaranteed bandwidth, the remaining bandwidth can be used by other classes of
traffic. However, during high traffic periods, 5 Gbps of bandwidth is absolutely available for
class 1 traffic. During these periods of congestion, any Class 1 traffic that exceeds 5 Gbps is
best effort.
• Egress Max—The overall bandwidth allocation for matching traffic. The firewall drops traffic
that exceeds the egress max limit that you set. Depending on your QoS configuration, you can
set a maximum bandwidth limit for a QoS class, for all or some clear text traffic, for all or some
tunneled traffic, and for all traffic exiting the QoS interface.
The cumulative guaranteed bandwidth for the QoS profile attached to the interface
must not exceed the total bandwidth allocated to the interface.
To define bandwidth settings for QoS classes, see Step Add a QoS profile. To then apply those
bandwidth settings to clear text and tunneled traffic, and to set the overall bandwidth limit for a
QoS interface, see Step Enable QoS on a physical interface.
QoS Egress Interface
Enabling a QoS profile on the egress interface of the traffic identified for QoS treatment
completes a QoS configuration. The ingress interface for QoS traffic is the interface on which the
traffic enters the firewall. The egress interface for QoS traffic is the interface that traffic leaves
the firewall from. QoS is always enabled and enforced on the egress interface for a traffic flow.
The egress interface in a QoS configuration can either be the external- or internal-facing interface
of the firewall, depending on the flow of the traffic receiving QoS treatment.
For example, in an enterprise network, if you are limiting employees’ download traffic from a
specific website, the egress interface in the QoS configuration is the firewall’s internal interface,
as the traffic flow is from the Internet, through the firewall, and to your company network.
Alternatively, when limiting employees’ upload traffic to the same website, the egress interface in
the QoS configuration is the firewall’s external interface, as the traffic you are limiting flows from
your company network, through the firewall, and then to the Internet.
PAN-OS® Administrator’s Guide Version 10.2 961 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
961 | Quality of Service
Because QoS is enforced on traffic as it egresses the firewall, the QoS policy rule is applied to
traffic after the firewall has enforced all other security policy rules, including Network Address
Translation (NAT) rules. However, the firewall evaluates QoS rules based on the contents of
the original packet, such as pre-NAT source IP, pre-NAT source zone, pre-NAT destination IP,
and post-NAT destination zone. Therefore, do not configure the QoS policy with the post-NAT
addresses.
Learn more about how to Identify the egress interface for applications that you want to receive
QoS treatment.
QoS for Clear Text and Tunneled Traffic
At the minimum, enabling a QoS interfaces requires you to select a default QoS profile that
defines bandwidth and priority settings for clear text traffic egressing the interface. However,
when setting up or modifying a QoS interface, you can apply granular QoS settings to outgoing
clear text traffic and tunneled traffic. QoS preferential treatment and bandwidth limiting can
be enforced for tunneled traffic, for individual tunnel interfaces, and/or for clear text traffic
originating from different source interfaces and source subnets. On Palo Alto Networks firewalls,
tunneled traffic refers to tunnel interface traffic, specifically IPSec traffic in tunnel mode.
PAN-OS® Administrator’s Guide Version 10.2 962 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
962 | Quality of Service
Configure QoS
Follow these steps to configure Quality of Service (QoS), which includes creating a QoS profile,
creating a QoS policy, and enabling QoS on an interface.
Before you create a QoS policy rule, make sure you understand that the set of IPv4 addresses is
treated as a subset of the set of IPv6 addresses, as described in detail in Policy.
STEP 1 | Identify the traffic you want to manage with QoS.
This example shows how to use QoS to limit web browsing.
Select ACC to view the Application Command Center page. Use the settings and charts on the
ACC page to view trends and traffic related to Applications, URL filtering, Threat Prevention,
Data Filtering, and HIP Matches.
Click any application name to display detailed application information.
PAN-OS® Administrator’s Guide Version 10.2 963 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
963 | Quality of Service
STEP 2 | Identify the egress interface for applications that you want to receive QoS treatment.
The egress interface for traffic depends on the traffic flow. If you are shaping incoming
traffic, the egress interface is the internal-facing interface. If you are shaping outgoing
traffic, the egress interface is the external-facing interface.
Select Monitor > Logs > Traffic to view the Traffic logs.
To filter and only show logs for a specific application:
• If an entry is displayed for the application, click the underlined link in the Application
column then click the Submit icon.
• If an entry is not displayed for the application, click the Add Log icon and search for the
application.
The Egress I/F in the traffic logs displays each application’s egress interface. To display the
Egress I/F column if it is not displayed by default:
• Click any column header to add a column to the log:
• Click the spyglass icon to the left of any entry to display a detailed log that includes the
application’s egress interface listed in the Destination section:
PAN-OS® Administrator’s Guide Version 10.2 964 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
964 | Quality of Service
STEP 3 | Add a QoS policy rule.
A QoS policy rule defines the traffic to receive QoS treatment. The firewall assigns a QoS class
of service to the traffic matched to the policy rule.
Because QoS is enforced on traffic as it egresses the firewall, your QoS policy rule is
applied to traffic after the firewall has enforced all other security policy rules, including
Network Address Translation (NAT) rules. If you want to apply QoS treatment to traffic
based on source, you must specify the pre-NAT source address (such as pre-NAT
source IP, pre-NAT source zone, pre-NAT destination IP, and post-NAT destination
zone) in a QoS policy rule. Do not configure the QoS policy with the post-NAT source
address if you want to apply QoS treatment for the source traffic.
1. Select Policies > QoS and Add a new policy rule.
2. On the General tab, give the QoS Policy Rule a descriptive Name.
3. Specify traffic to receive QoS treatment based on Source, Destination, Application,
Service/URL Category, and DSCP/ToS values (the DSCP/ToS settings allow you to
Enforce QoS Based on DSCP Classification).
For example, select the Application, click Add, and select web-browsing to apply QoS to
web browsing traffic.
4. (Optional) Continue to define additional parameters. For example, select Source and Add
a Source User to provide QoS for a specific user’s web traffic.
5. Select Other Settings and assign a QoS Class to traffic matching the policy rule. For
example, assign Class 2 to the user1’s web traffic.
6. Click OK.
PAN-OS® Administrator’s Guide Version 10.2 965 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
965 | Quality of Service
STEP 4 | Add a QoS profile.
A QoS profile allows you to define the eight classes of service that traffic can receive, including
priority, and enables QoS Bandwidth Management.
You can edit any existing QoS profile, including the default, by clicking the QoS profile name.
1. Select Network > Network Profiles > QoS Profile and Add a new profile.
2. Enter a descriptive Profile Name.
3. Set the overall bandwidth limits for the QoS profile:
• Enter an Egress Max value to set the overall bandwidth allocation for the QoS profile.
• Enter an Egress Guaranteed value to set the guaranteed bandwidth for the QoS
Profile.
Any traffic that exceeds the Egress Guaranteed value is best effort and not
guaranteed. Bandwidth that is guaranteed but is unused continues to remain
available for all traffic.
You can configure the Egress Guaranteed and Egress Max values in Mbps or
percentages. The following considerations should be taken into account when
configuring these values in percentages:
• The Egress Guaranteed (%) per class is calculated using the Egress Max value, not the
Egress Guaranteed value.
• Profile Egress Guaranteed equals the sum of the Egress Guaranteed (%) per class
multiplied by the Egress Max.
For example: The Egress Max is configured as 100Mbps. The guaranteed percentage
configured for Class 1 is 30%, for Class 2 it is 20%, for Class 3 it is 5%, and for Class 4
it is 1%. This configuration results in a total percentage guaranteed as 56%. In this case,
PAN-OS® Administrator’s Guide Version 10.2 966 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
966 | Quality of Service
profile Egress Guaranteed is 56Mbps (56% x Egress Max). This also means that Class 1
Egress Guaranteed is 30Mbps, Class 2 Egress Guaranteed is 20Mbps, and so on.
4. In the Classes section, specify how to treat up to eight individual QoS classes:
1. Add a class to the QoS Profile.
2. Select the Priority for the class: real-time, high, medium, or low.
3. Enter the Egress Max and Egress Guaranteed bandwidth for traffic assigned to each
QoS class.
5. Click OK.
In the following example, the QoS profile Limit Web Browsing limits Class 2 traffic to a
maximum bandwidth of 50Mbps and a guaranteed bandwidth of 2Mbps.
PAN-OS® Administrator’s Guide Version 10.2 967 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
967 | Quality of Service
STEP 5 | Enable QoS on a physical interface.
Part of this step includes the option to select clear text and tunneled traffic for unique QoS
treatment.
Check if the firewall model you’re using supports enabling QoS on a subinterface by
reviewing a summary of the Product Specifications.
1. Select Network > QoS and Add a QoS interface.
2. Select Physical Interface and choose the Interface Name of the interface on which to
enable QoS.
In the example, Ethernet 1/1 is the egress interface for web-browsing traffic (see Step
2).
3. Set the Egress Max bandwidth for all traffic exiting this interface.
It is a best practice to always define the Egress Max value for a QoS interface.
Ensure that the cumulative guaranteed bandwidth for the QoS profile attached
to the interface does not exceed the total bandwidth allocated to the interface.
4. Select Turn on QoS feature on this interface.
5. In the Default Profile section, select a QoS profile to apply to all Clear Text traffic exiting
the physical interface.
6. (Optional) Select a default QoS profile to apply to all tunneled traffic exiting the
interface.
For example, enable QoS on ethernet 1/1 and apply the bandwidth and priority settings you
defined for the QoS profile Limit Web Browsing (Step 4) to be used as the default settings for
clear text egress traffic.
1. (Optional) Continue to define more granular settings to provide QoS for Clear Text and
Tunneled Traffic. Settings configured on the Clear Text Traffic tab and the Tunneled
PAN-OS® Administrator’s Guide Version 10.2 968 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
968 | Quality of Service
Traffic tab automatically override the default profile settings for clear text and tunneled
traffic on the Physical Interface tab.
• Select Clear Text Traffic and:
• Set the Egress Guaranteed and Egress Max bandwidths for clear text traffic.
• Click Add and apply a QoS profile to enforce clear text traffic based on source
interface and source subnet.
(PA-3200 Series, PA-5200 Series, PA-5450 firewall, and PA-7000 Series
only) You must also select a destination interface when configuring a QoS
policy rule if the rule is applied to a specific subinterface.
• Select Tunneled Traffic and:
• Set the Egress Guaranteed and Egress Max bandwidths for tunneled traffic.
• Click Add and attach a QoS profile to a single tunnel interface.
2. Click OK.
STEP 6 | Commit your changes.
Click Commit.
PAN-OS® Administrator’s Guide Version 10.2 969 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
969 | Quality of Service
STEP 7 | Verify a QoS configuration.
Select Network > QoS and then Statistics to view QoS bandwidth, active sessions of a
selected QoS class, and active applications for the selected QoS class.
For example, see the statistics for ethernet 1/3 with QoS enabled:
Class 2 traffic limited to 2.343 Mbps of guaranteed bandwidth and a maximum bandwidth of
51.093 Mbps.
Continue to click the tabs to display further information regarding applications, source users,
destination users, security rules and QoS rules.
Bandwidth limits shown on the QoS Statistics window include a hardware adjustment
factor.
PAN-OS® Administrator’s Guide Version 10.2 970 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
970 | Quality of Service
Configure Lockless QoS
The Palo Alto Networks firewalls supports two types of QoS:
• Legacy QoS—In legacy QoS mode, the firewall supports both QoS and non-QoS traffics, where
the legacy QoS shapes the QoS traffic.
• (PAN-OS 10.2.5 and later 10.2 releases) Lockless QoS —In Lockless QoS mode, the firewall
supports both QoS and non-QoS traffics, where the Lockless QoS shapes the QoS traffic.
The firewall shapes the packets from the same interface (or port) by the same core for
achieving Lockless QoS. For firewalls with higher bandwidth QoS requirements, the Lockless
QoS dedicates CPU cores to the QoS function that improves QoS performance, resulting in
improved throughput and latency.
In Lockless QoS mode, as the members in a LAG have to be mapped to the same core, the
overall LAG QoS throughput is limited by the per core throughput.
• The QoS throughput on a 100G, 40G, and 25G port is limited to a single core
throughput.
• Whenever more than two ports are mapped to a single core, the QoS throughput of
that core is shared.
We support Lockless QoS mode on the following firewall models. Regardless of the type of
QoS configured, the maximum bandwidth (maximum rate of transfer) you can allocate at the
port level and QoS profile level for the following platforms is 10G.
• PA-3410 firewall
• PA-3420 firewall
• PA-3430 firewall
• PA-3440 firewall
• PA-5410 firewall
• PA-5420 firewall
• PA-5430 firewall
Follow these steps to enable, disable, and view the status of the Lockless QoS.
STEP 1 | Access the CLI
STEP 2 | Use the operational command set lockless-qos yes to enable the Lockless QoS
to improve the QoS performance. Commit and reboot the firewall for the changes to take
effect.
username@hostname> set lockless-qos yes
Changing lockless-qos enable requires reboot of the device. Do you
want to continue? (y or n)
If you want to configure Lockless QoS where the legacy QoS is already configured, you can do
so by running the set lockless-qos yes command and reboot your firewall. If you don't
run this command, the firewall retains the legacy QoS behavior. When you disable the Lockless
PAN-OS® Administrator’s Guide Version 10.2 971 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
971 | Quality of Service
QoS, the firewall falls back to the legacy QoS behavior, if you have already configured legacy
QoS before enabling Lockless QoS.
STEP 3 | Use the operational command set lockless-qos no to disable the Lockless QoS. As a
result, Lockless QoS isn't supported on the firewall.
username@hostname> set lockless-qos no
STEP 4 | Use the operational command show lockless-qos enable to view the Lockless QoS
enable status.
username@hostname> show lockless-qos enable
lockless-qos enable : yes
STEP 5 | Use the operational command show lockless-qos if-core-mapping to view the list
of ports with the number of cores allocated for the QoS process by the Lockless QoS.
username@hostname> show lockless-qos if-core-mapping
interface qos-core
ethernet1/41 71
ethernet1/42 72
PAN-OS® Administrator’s Guide Version 10.2 972 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
972 | Quality of Service
Configure QoS for a Virtual System
QoS can be configured for a single or several virtual systems configured on a Palo Alto
Networks firewall. Because a virtual system is an independent firewall, QoS must be configured
independently for a single virtual system.
Configuring QoS for a virtual system is similar to configuring QoS on a physical firewall, with the
exception that configuring QoS for a virtual system requires specifying the source and destination
of traffic. Because a virtual system exists without set physical boundaries and because traffic in a
virtual environment spans more than one virtual system, specifying source and destination zones
and interfaces for traffic is necessary to control and shape traffic for a single virtual system.
The example below shows two virtual systems configured on firewall. VSYS 1 (purple) and VSYS
2 (red) each have QoS configured to prioritize or limit two distinct traffic flows, indicated by their
corresponding purple (VSYS 1) and red (VSYS 2) lines. The QoS nodes indicate the points at which
traffic is matched to a QoS policy and assigned a QoS class of service, and then later indicate the
point at which traffic is shaped as it egresses the firewall.
Refer to Virtual Systems for information on virtual systems and how to configure them.
STEP 1 | Confirm that the appropriate interfaces, virtual routers, and security zones are associated
with each virtual system.
• To view configured interfaces, select Network > Interface.
• To view configured zones, select Network > Zones.
• To view information on defined virtual routers, select Network > Virtual Routers.
PAN-OS® Administrator’s Guide Version 10.2 973 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
973 | Quality of Service
STEP 2 | Identify traffic to apply QoS to.
Select ACC to view the Application Command Center page. Use the settings and charts on the
ACC page to view trends and traffic related to Applications, URL filtering, Threat Prevention,
Data Filtering, and HIP Matches.
To view information for a specific virtual system, select the virtual system from the Virtual
System drop-down:
Click any application name to display detailed application information.
PAN-OS® Administrator’s Guide Version 10.2 974 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
974 | Quality of Service
STEP 3 | Identify the egress interface for applications that you identified as needing QoS treatment.
In a virtual system environment, QoS is applied to traffic on the traffic’s egress point on the
virtual system. Depending the configuration and QoS policy for a virtual system, the egress
point of QoS traffic could be associated with a physical interface or could be a zone.
This example shows how to limit web-browsing traffic on vsys 1.
Select Monitor > Logs > Traffic to view traffic logs. Each entry has the option to display
columns with information necessary to configure QoS in a virtual system environment:
• virtual system
• egress interface
• ingress interface
• source zone
• destination zone
To display a column if it is not displayed by default:
• Click any column header to add a column to the log:
• Click the spyglass icon to the left of any entry to display a detailed log that includes the
application’s egress interface, as well as source and destination zones, in the Source and
Destination sections:
For example, for web-browsing traffic from VSYS 1, the ingress interface is ethernet 1/2, the
egress interface is ethernet 1/1, the source zone is trust and the destination zone is untrust.
PAN-OS® Administrator’s Guide Version 10.2 975 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
975 | Quality of Service
STEP 4 | Create a QoS Profile.
You can edit any existing QoS Profile, including the default, by clicking the profile name.
1. Select Network > Network Profiles > QoS Profile and click Add to open the QoS Profile
dialog.
2. Enter a descriptive Profile Name.
3. Enter an Egress Max to set the overall bandwidth allocation for the QoS profile.
4. Enter an Egress Guaranteed to set the guaranteed bandwidth for the QoS profile.
Any traffic that exceeds the QoS profile’s egress guaranteed limit is best effort
but is not guaranteed.
5. In the Classes section of the QoS Profile, specify how to treat up to eight individual QoS
classes:
1. Click Add to add a class to the QoS Profile.
2. Select the Priority for the class.
3. Enter an Egress Max for a class to set the overall bandwidth limit for that individual
class.
4. Enter an Egress Guaranteed for the class to set the guaranteed bandwidth for that
individual class.
6. Click OK to save the QoS profile.
STEP 5 | Create a QoS policy.
In an environment with multiple virtual systems, traffic spans more than one virtual system.
Because of this, when you are enabling QoS for a virtual system, you must define traffic to
receive QoS treatment based on source and destination zones. This ensures that the traffic is
PAN-OS® Administrator’s Guide Version 10.2 976 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
976 | Quality of Service
prioritized and shaped only for that virtual system (and not for other virtual systems through
which the traffic might flow).
1. Select Policies > QoS and Add a QoS Policy Rule.
2. Select General and give the QoS Policy Rule a descriptive Name.
3. Specify the traffic to which the QoS policy rule will apply. Use the Source, Destination,
Application, and Service/URL Category tabs to define matching parameters for
identifying traffic.
For example, select Application and Add web-browsing to apply the QoS policy rule to
that application:
4. Select Source and Add the source zone of vsys 1 web-browsing traffic.
5. Select Destination and Add the destination zone of vsys 1 web-browsing traffic.
6. Select Other Settings and select a QoS Class to assign to the QoS policy rule. For
example, assign Class 2 to web-browsing traffic on vsys 1:
7. Click OK to save the QoS policy rule.
PAN-OS® Administrator’s Guide Version 10.2 977 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
977 | Quality of Service
STEP 6 | Enable the QoS Profile on a physical interface.
It is a best practice to always define the Egress Max value for a QoS interface.
1. Select Network > QoS and click Add to open the QoS Interface dialog.
2. Enable QoS on the physical interface:
1. On the Physical Interface tab, select the Interface Name of the interface to apply the
QoS Profile to.
In this example, ethernet 1/1 is the egress interface for web-browsing traffic on vsys
1 (see Step 2).
2. Select Turn on QoS feature on this interface.
3. On the Physical Interface tab, select the default QoS profile to apply to all Clear Text
traffic.
(Optional) Use the Tunnel Interface field to apply a default QoS profile to all tunneled
traffic.
4. (Optional) On the Clear Text Traffic tab, configure additional QoS settings for clear text
traffic:
• Set the Egress Guaranteed and Egress Max bandwidths for clear text traffic.
• Click Add to apply a QoS Profile to selected clear text traffic, further selecting the
traffic for QoS treatment according to source interface and source subnet (creating a
QoS node).
5. (Optional) On the Tunneled Traffic tab, configure additional QoS settings for tunnel
interfaces:
• Set the Egress Guaranteed and Egress Max bandwidths for tunneled traffic.
• Click Add to associate a selected tunnel interface with a QoS Profile.
6. Click OK to save changes.
7. Commit the changes.
STEP 7 | Verify QoS configuration.
• Select Network > QoS to view the QoS Policies page. The QoS Policies page verifies that
QoS is enabled and includes a Statistics link. Click the Statistics link to view QoS bandwidth,
PAN-OS® Administrator’s Guide Version 10.2 978 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
978 | Quality of Service
active sessions of a selected QoS node or class, and active applications for the selected QoS
node or class.
• In a multi-vsys environment, sessions cannot span multiple systems. Multiple sessions are
created for one traffic flow if the traffic passes through more than one virtual system. To
browse sessions running on the firewall and view applied QoS Rules and QoS Classes, select
Monitor > Session Browser.
PAN-OS® Administrator’s Guide Version 10.2 979 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
979 | Quality of Service
Enforce QoS Based on DSCP Classification
A Differentiated Services Code Point (DSCP) is a packet header value that can be used to request
(for example) high priority or best effort delivery for traffic. Session-Based DSCP Classification
allows you to both honor DSCP values for incoming traffic and to mark a session with a DSCP
value as session traffic exits the firewall. This enables all inbound and outbound traffic for a
session to receive continuous QoS treatment as it flows through your network. For example,
inbound return traffic from an external server can now be treated with the same QoS priority
that the firewall initially enforced for the outbound flow based on the DSCP value the firewall
detected at the beginning of the session. Network devices between the firewall and end user
will also then enforce the same priority for the return traffic (and any other outbound or inbound
traffic for the session).
You cannot apply DSCP code points or QoS to SSL Forward Proxy, SSL Inbound
Inspection, and SSH Proxy traffic.
Different types of DSCP markings indicate different levels of service:
Completing this step enables the firewall to mark traffic with the same DSCP value that was
detected at the beginning of a session (in this example, the firewall would mark return traffic
with the DSCP AF11 value). While configuring QoS allows you to shape traffic as it egresses the
firewall, enabling this option in a security rule allows the other network devices intermediate to
the firewall and the client to continue to enforce priority for DSCP marked traffic.
• Expedited Forwarding (EF): Can be used to request low loss, low latency and guaranteed
bandwidth for traffic. Packets with EF codepoint values are typically guaranteed highest
priority delivery.
• Assured Forwarding (AF): Can be used to provide reliable delivery for applications. Packets
with AF codepoint indicate a request for the traffic to receive higher priority treatment than
the best-effort service provides (though packets with an EF codepoint will continue to take
precedence over those with an AF codepoint).
• Class Selector (CS): Can be used to provide backward compatibility with network devices that
use the IP precedence field to mark priority traffic.
• IP Precedence (ToS): Can be used by legacy network devices to mark priority traffic (the IP
Precedence header field was used to indicate the priority for a packet before the introduction
of the DSCP classification).
• Custom Codepoint: Create a custom codepoint to match to traffic by entering a Codepoint
Name and Binary Value.
For example, select the Assured Forwarding (AF) to ensure traffic marked with an AF codepoint
value has higher priority for reliable delivery over applications marked to receive lower
priority.Use the following steps to enable Session-Based DSCP Classification. Start by configuring
QoS based on the DSCP marking detected at the beginning of a session. You can then continue
to enable the firewall to mark the return flow for a session with the same DSCP value used to
enforce QoS for the initial outbound flow.
STEP 1 | Perform the preliminary steps to Configure QoS.
PAN-OS® Administrator’s Guide Version 10.2 980 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
980 | Quality of Service
STEP 2 | Define the traffic to receive QoS treatment based on DSCP value.
1. Select Policies > QoS and Add or modify an existing QoS rule and populate required
fields.
2. Select DSCP/ToS and select Codepoints.
3. Add DSCP/ToS codepoints for which you want to enforce QoS.
4. Select the Type of DSCP/ToS marking for the QoS rule to match to traffic:
It is a best practice to use a single DSCP type to manage and prioritize your
network traffic.
5. Match the QoS policy to traffic on a more granular scale by specifying the Codepoint
value. For example, with Assured Forwarding (AF) selected as the Type of DSCP value
for the policy to match, further specify an AF Codepoint value such as AF11.
When Expedited Forwarding (EF) is selected as the Type of DSCP marking, a
granular Codepoint value cannot be specified. The QoS policy rule matches to
traffic marked with any EF codepoint value.
6. Select Other Settings and assign a QoS Class to traffic matched to the QoS rule. In this
example, assign Class 1 to sessions where a DSCP marking of AF11 is detected for the
first packet in the session.
7. Click OK to save the QoS rule.
STEP 3 | Define the QoS priority for traffic to receive when it is matched to a QoS rule based the
DSCP marking detected at the beginning of a session.
1. Select Network > Network Profiles > QoS Profile and Add or modify an existing QoS
profile. For details on profile options to set priority and bandwidth for traffic, see QoS
Concepts and Configure QoS.
2. Add or modify a profile class. For example, because Step 2 showed steps to classify
AF11 traffic as Class 1 traffic, you could add or modify a class1 entry.
3. Select a Priority for the class of traffic, such as high.
4. Click OK to save the QoS Profile.
STEP 4 | Enable QoS on an interface.
Select Network > QoS and Add or modify an existing interface and Turn on QoS feature on
this interface.
In this example, traffic with an AF11 DSCP marking is matched to the QoS rule and assigned
Class 1. The QoS profile enabled on the interface enforces high priority treatment for Class 1
traffic as it egresses the firewall (the session outbound traffic).
PAN-OS® Administrator’s Guide Version 10.2 981 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
981 | Quality of Service
STEP 5 | Enable DSCP Marking.
Mark return traffic with a DSCP value, enabling the inbound flow for a session to be marked
with the same DSCP value detected for the outbound flow.
1. Select Policies > Security and Add or modify a security policy.
2. Select Actions and in the QoS Marking drop-down, choose Follow Client-to-Server
Flow.
3. Click OK to save your changes.
Completing this step enables the firewall to mark traffic with the same DSCP value that
was detected at the beginning of a session (in this example, the firewall would mark return
traffic with the DSCP AF11 value). While configuring QoS allows you to shape traffic as it
egresses the firewall, enabling this option in a security rule allows the other network devices
intermediate to the firewall and the client to continue to enforce priority for DSCP marked
traffic.
STEP 6 | Commit the configuration.
Commit your changes.
PAN-OS® Administrator’s Guide Version 10.2 982 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
982 | Quality of Service
QoS Use Cases
The following use cases demonstrate how to use QoS in common scenarios:
• Use Case: QoS for a Single User
• Use Case: QoS for Voice and Video Applications
Use Case: QoS for a Single User
A CEO finds that during periods of high network usage, she is unable to access enterprise
applications to respond effectively to critical business communications. The IT admin wants to
ensure that all traffic to and from the CEO receives preferential treatment over other employee
traffic so that she is guaranteed not only access to, but high performance of, critical network
resources.
STEP 1 | The admin creates the QoS profile CEO_traffic to define how traffic originating from the CEO
will be treated and shaped as it flows out of the company network:
The admin assigns a guaranteed bandwidth (Egress Guaranteed) of 50 Mbps to ensure that the
CEO will have that amount that bandwidth guaranteed to her at all times (more than she would
need to use), regardless of network congestion.
The admin continues by designating Class 1 traffic as high priority and sets the profile’s
maximum bandwidth usage (Egress Max) to 1000 Mbps, the same maximum bandwidth for the
interface that the admin will enable QoS on. The admin is choosing to not restrict the CEO’s
bandwidth usage in any way.
It is a best practice to populate the Egress Max field for a QoS profile, even if the
max bandwidth of the profile matches the max bandwidth of the interface. The QoS
profile’s max bandwidth should never exceed the max bandwidth of the interface you
are planning to enable QoS on.
STEP 2 | The admin creates a QoS policy to identify the CEO’s traffic (Policies > QoS) and assigns it
the class that he defined in the QoS profile (see prior step). Because User-ID is configured,
the admin uses the Source tab in the QoS policy to singularly identify the CEO’s traffic by
PAN-OS® Administrator’s Guide Version 10.2 983 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
983 | Quality of Service
her company network username. (If User-ID is not configured, the administrator could Add
the CEO’s IP address under Source Address. See User-ID.):
The admin associates the CEO’s traffic with Class 1 (Other Settings tab) and then continues
to populate the remaining required policy fields; the admin gives the policy a descriptive
Name (General tab) and selects Any for the Source Zone (Source tab) and Destination Zone
(Destination tab):
STEP 3 | Now that Class 1 is associated with the CEO’s traffic, the admin enables QoS by checking
Turn on QoS feature on interface and selecting the traffic flow’s egress interface. The egress
interface for the CEO’s traffic flow is the external-facing interface, in this case, ethernet 1/2:
Because the admin wants to ensure that all traffic originating from the CEO is guaranteed by
the QoS profile and associated QoS policy he created, he selects the CEO_traffic to apply to
Clear Text traffic flowing from ethernet 1/2.
STEP 4 | After committing the QoS configuration, the admin navigates to the Network > QoS page to
confirm that the QoS profile CEO_traffic is enabled on the external-facing interface, ethernet
1/2:
PAN-OS® Administrator’s Guide Version 10.2 984 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
984 | Quality of Service
STEP 5 | He clicks Statistics to view how traffic originating with the CEO (Class 1) is being shaped as it
flows from ethernet 1/2:
This case demonstrates how to apply QoS to traffic originating from a single source
user. However, if you also wanted to guarantee or shape traffic to a destination user,
you could configure a similar QoS setup. Instead of, or in addition to this work flow,
create a QoS policy that specifies the user’s IP address as the Destination Address on
the Policies > QoS page (instead of specifying the user’s source information) and then
enable QoS on the network’s internal-facing interface on the Network > QoS page
(instead of the external-facing interface).
Use Case: QoS for Voice and Video Applications
Voice and video traffic is particularly sensitive to measurements that the QoS feature shapes and
controls, especially latency and jitter. For voice and video transmissions to be audible and clear,
voice and video packets cannot be dropped, delayed, or delivered inconsistently. A best practice
for voice and video applications, in addition to guaranteeing bandwidth, is to guarantee priority to
voice and video traffic.
In this example, employees at a company branch office are experiencing difficulties and
unreliability in using video conferencing and Voice over IP (VoIP) technologies to conduct
business communications with other branch offices, with partners, and with customers. An IT
admin intends to implement QoS in order to address these issues and ensure effective and reliable
business communication for the branch employees. Because the admin wants to guarantee QoS
to both incoming and outgoing network traffic, he will enable QoS on both the firewall’s internaland external-facing interfaces.
PAN-OS® Administrator’s Guide Version 10.2 985 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
985 | Quality of Service
STEP 1 | The admin creates a QoS profile, defining Class 2 so that Class 2 traffic receives real-time
priority and on an interface with a maximum bandwidth of 1000 Mbps, is guaranteed a
bandwidth of 250 Mbps at all times, including peak periods of network usage.
Real-time priority is typically recommended for applications affected by latency, and is
particularly useful in guaranteeing performance and quality of voice and video applications.
On the firewall web interface, the admin selects the Network > Network Profiles > Qos
Profile page, clicks Add, enters the Profile Name, "ensure voip-video traffic", and defines Class
2 traffic.
STEP 2 | The admin creates a QoS policy to identify voice and video traffic. Because the company
does not have one standard voice and video application, the admin wants to ensure
QoS is applied to a few applications that are widely and regularly used by employees to
communicate with other offices, with partners, and with customers. On the Policies > QoS
> QoS Policy Rule > Applications tab, the admin clicks Add and opens the Application Filter
window. The admin continues by selecting criteria to filter the applications he wants to apply
PAN-OS® Administrator’s Guide Version 10.2 986 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
986 | Quality of Service
QoS to, choosing the Subcategory voip-video, and narrowing that down by specifying only
voip-video applications that are both low-risk and widely-used.
The application filter is a dynamic tool that, when used to filter applications in the QoS policy,
allows QoS to be applied to all applications that meet the criteria of voip-video, low risk, and
widely used at any given time.
The admin names the Application Filter voip-video-low-risk and includes it in the QoS policy:
The admin names the QoS policy Voice-Video and selects Other Settings to assign all traffic
matched to the policy Class 2. He is going to use the Voice-Video QoS policy for both
incoming and outgoing QoS traffic, so he sets Source and Destination information to Any:
STEP 3 | Because the admin wants to ensure QoS for both incoming and outgoing voice and video
communications, he enables QoS on the network’s external-facing interface (to apply QoS
PAN-OS® Administrator’s Guide Version 10.2 987 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
987 | Quality of Service
to outgoing communications) and to the internal-facing interface (to apply QoS to incoming
communications).
The admin begins by enabling the QoS profile he created, ensure voice-video traffic (Class 2 in
this profile is associated with policy, Voice-Video) on the external-facing interface, in this case,
ethernet 1/2.
He then enables the same QoS profile ensure voip-video traffic on a second interface, the
internal-facing interface (in this case, ethernet 1/1).
STEP 4 | The admin selects Network > QoS to confirm that QoS is enabled for both incoming and
outgoing voice and video traffic:
The admin has successfully enabled QoS on both the network’s internal- and external-facing
interfaces. Real-time priority is now ensured for voice and video application traffic as it flows
both into and out of the network, ensuring that these communications, which are particularly
sensitive to latency and jitter, can be used reliably and effectively to perform both internal and
external business communications.
PAN-OS® Administrator’s Guide Version 10.2 988 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
988 | VPNs
Virtual private networks (VPNs) create tunnels that allow users/systems to connect securely
over a public network, as if they were connecting over a local area network (LAN). To set up a
VPN tunnel, you need a pair of devices that can authenticate each other and encrypt the flow of
information between them. The devices can be a pair of Palo Alto Networks firewalls, or a Palo
Alto Networks firewall along with a VPN-capable device from another vendor.
• VPN Deployments
• Site-to-Site VPN Overview
• Site-to-Site VPN Concepts
• Set Up Site-to-Site VPN
• Site-to-Site VPN Quick Configs
989 | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
989 | VPNs
VPN Deployments
The Palo Alto Networks firewall supports the following VPN deployments:
• Site-to-Site VPN— A simple VPN that connects a central site and a remote site, or a hub and
spoke VPN that connects a central site with multiple remote sites. The firewall uses the IP
Security (IPSec) set of protocols to set up a secure tunnel for the traffic between the two sites.
See Site-to-Site VPN Overview.
• Remote User-to-Site VPN—A solution that uses the GlobalProtect agent to allow a remote
user to establish a secure connection through the firewall. This solution uses SSL and IPSec
to establish a secure connection between the user and the site. Refer to the GlobalProtect
Administrator’s Guide.
• Large Scale VPN— The Palo Alto Networks GlobalProtect Large Scale VPN (LSVPN) provides
a simplified mechanism to roll out a scalable hub and spoke VPN with up to 1,024 satellite
offices. The solution requires Palo Alto Networks firewalls to be deployed at the hub and at
every spoke. It uses certificates for device authentication, SSL for securing communication
between all components, and IPSec to secure data. See Large Scale VPN (LSVPN).
Figure 7: VPN Deployments
PAN-OS® Administrator’s Guide Version 10.2 990 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
990 | VPNs
Site-to-Site VPN Overview
A VPN connection that allows you to connect two Local Area Networks (LANs) is called a site-tosite VPN. You can configure route-based VPNs to connect Palo Alto Networks firewalls located at
two sites or to connect a Palo Alto Networks firewall with a third-party security device at another
location. The firewall can also interoperate with third-party policy-based VPN devices; the Palo
Alto Networks firewall supports route-based VPN.
The Palo Alto Networks firewall sets up a route-based VPN, where the firewall makes a routing
decision based on the destination IP address. If traffic is routed to a specific destination through a
VPN tunnel, then it is handled as VPN traffic.
The IP Security (IPSec) set of protocols is used to set up a secure tunnel for the VPN traffic, and
the information in the TCP/IP packet is secured (and encrypted if the tunnel type is ESP). The IP
packet (header and payload) is embedded in another IP payload, and a new header is applied and
then sent through the IPSec tunnel. The source IP address in the new header is that of the local
VPN peer and the destination IP address is that of the VPN peer on the far end of the tunnel.
When the packet reaches the remote VPN peer (the firewall at the far end of the tunnel), the
outer header is removed and the original packet is sent to its destination.
In order to set up the VPN tunnel, first the peers need to be authenticated. After successful
authentication, the peers negotiate the encryption mechanism and algorithms to secure the
communication. The Internet Key Exchange (IKE) process is used to authenticate the VPN peers,
and IPSec Security Associations (SAs) are defined at each end of the tunnel to secure the VPN
communication. IKE uses digital certificates or preshared keys, and the Diffie Hellman keys to set
up the SAs for the IPSec tunnel. The SAs specify all of the parameters that are required for secure
transmission— including the security parameter index (SPI), security protocol, cryptographic keys,
and the destination IP address—encryption, data authentication, data integrity, and endpoint
authentication.
The following figure shows a VPN tunnel between two sites. When a client that is secured
by VPN Peer A needs content from a server located at the other site, VPN Peer A initiates a
connection request to VPN Peer B. If the security policy permits the connection, VPN Peer A uses
the IKE Crypto profile parameters (IKE phase 1) to establish a secure connection and authenticate
VPN Peer B. Then, VPN Peer A establishes the VPN tunnel using the IPSec Crypto profile, which
defines the IKE phase 2 parameters to allow the secure transfer of data between the two sites.
Figure 8: Site-to-Site VPN
PAN-OS® Administrator’s Guide Version 10.2 991 ©2025 Palo Alto Networks, Inc. | https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/pan-os/10-2/pan-os-admin/pan-os-admin.pdf |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.