Pcnse Study Guide PDF
Pcnse Study Guide PDF
Pcnse Study Guide PDF
NETWORKS
PCNSE
STUDY GUIDE
January 2020
Palo Alto Networks, Inc. www.paloaltonetworks.com
©2016-2020 Palo Alto Networks – all rights reserved. AutoFocus, Demisto, GlobalProtect, Palo Alto
Networks, PAN-OS, Panorama, Prisma SaaS, RedLock, Traps, and WildFire are trademarks of Palo Alto
Networks, Inc. All other trademarks are the property of their respective owners.
Overview
The Palo Alto Networks Certified Network Security Engineer (PCNSE) is a formal, third‐party proctored
certification that indicates that those who have passed it possess the in‐depth knowledge to design,
install, configure, maintain, and troubleshoot most implementations based on the Palo Alto Networks
platform.
This exam will certify that the successful candidate has the knowledge and skills necessary to implement
the Palo Alto Networks next-generation firewall PAN-OS 9.1 platform in any environment.
Exam Details
• Certification Name: Palo Alto Networks Certified Network Security Engineer
• Delivered through Pearson VUE: www.pearsonvue.com/paloaltonetworks
• Exam Series: PCNSE
• Seat Time: 80 minutes
• Number of items: 75
• Format: Multiple Choice, Scenarios with Graphics, and Matching
• Languages: English and Japanese
Intended Audience
The PCNSE exam should be taken by anyone who wants to demonstrate a deep understanding of Palo
Alto Networks technologies, including customers who use Palo Alto Networks products, value-added
resellers, pre-sales system engineers, system integrators, and support staff.
Qualifications
Candidate should have three to five years’ experience working in the Networking or Security industries
and the equivalent of 6 to 12 months’ experience deploying and configuring Palo Alto Networks NGFW
within the Palo Alto Networks Security Operating Platform.
Recommended Training
Palo Alto Networks strongly recommends that you attend the following instructor-led training courses or
equivalent virtual digital learning courses:
• Firewall Essentials: Configuration and Management (EDU-210) or digital learning (EDU-110)
• Panorama: Managing Firewalls at Scale (EDU-220) or digital learning (EDU-120)
• Optional Training: Firewall: Optimizing Firewall Threat Prevention (EDU-214) or digital learning
(EDU-114)
• Optional training: Firewall: Troubleshooting (EDU-330)
After you have completed the courses, practice on the platform to master the basics. Use the following
resources to prepare for the exam. All resources can be found here:
https://www.paloaltonetworks.com/services/education/certification.html#pcnse
• Cybersecurity Skills Practice Lab
• PCNSE Study Guide and Practice Exam
• Administrator’s Guide: specific configuration information and “best practice” settings
• Preparation videos and tutorials
Disclaimer
This study guide is intended to provide information about the objectives covered by this exam, related
resources, and recommended courses. The material contained within this study guide is not intended to
guarantee that a passing score will be achieved on the exam. Palo Alto Networks recommends that a
candidate thoroughly understand the objectives indicated in this guide and use the resources and
courses recommended in this guide where needed to gain that understanding.
Cortex Data Lake automatically collects, integrates, and normalizes data across your security
infrastructure. If your data is unified, you can run advanced AI and machine learning to radically simplify
security operations with apps built on Cortex. Cortex Data Lake is augmented with data from Palo Alto
Networks WildFire®, AutoFocus/MineMeld, and Unit 42 information sources.
Cortex XDR is a set of tools that works with Cortex Data Lake to identify threats manually. With AI, it
determines root causes of security events and responds to threats by deploying response settings to
enforcement products.
Palo Alto Networks products are organized into two areas of focus that are described in the following
sections.
DNS Security: DNS security service applies predictive analytics, machine learning, and automation to
block attacks that use DNS. Tight integration with the next-generation firewall gives you automated
protections and eliminates the need for independent tools. DNS Security service makes malicious domain
information available to your NGFW collected from WildFire, Unit 42, URL filtering, and the Cyber Threat
Alliance.
WildFire: WildFire automatically prevents zero-day exploits and malware. Traditional malware analysis
and sandboxing techniques are not adequate and cannot keep pace with new exploits. WildFire uses
shared community-sourced threat data and advanced analysis, and immediately shares protections
across the network, endpoint, and cloud. WildFire automatically delivers protections about every 5
minutes (by accessing a database that is updated every 5 minutes), thus preventing successful
cyberattacks.
AutoFocus: AutoFocus contextual threat intelligence brings speed, consistency, and precision to threat
investigation. It provides instant access to community-based threat data, enhanced with deep context
and attribution from the Unit 42 threat research team, thus saving time and effort. Now your teams can
©2016-2020, Palo Alto Networks, Inc. 21
quickly investigate, correlate, and pinpoint malware’s root cause without adding dedicated malware
researchers or additional tools. Plus, automated protections make raw intelligence simple to turn into
protection across your environment.
Traps: Traps advanced endpoint protection stops threats on the endpoint and coordinates enforcement
with cloud and network security to prevent successful cyberattacks. Traps is the only solution that pre-
emptively blocks security breaches such as ransomware attacks. It uses a unique multi-method approach
that prevents known and unknown malware, exploits, and zero-day threats.
Threat Prevention: Threat Prevention capitalizes on the next-generation firewall’s capability to inspect all
traffic, and can prevent known threats, regardless of port, protocol, or SSL encryption. Threat Prevention
automatically stops vulnerability exploits with IPS capabilities, offers inline malware protection, and
blocks outbound command-and control-traffic. When Threat Prevention is combined with WildFire and
URL filtering, organizations are protected at every stage of the attack lifecycle, including both known and
zero-day threats. This service is consumed by other products and integrated into others.
MineMeld: MineMeld is an open-source application that streamlines the aggregation, enforcement, and
sharing of threat intelligence. MineMeld is available for all users directly on GitHub or on pre-built virtual
machines (VMs) for easy deployment. Anyone using the proper software can add to the MineMeld
functionality by contributing code to the open-source repository. MineMeld integrates information from
disparate sources, normalizes it for consumption, and can automate settings on managed products.
Expedition: Expedition is a free, virtual appliance that helps convert firewall configurations from leading
vendors to Palo Alto Networks next-generation firewalls.
VM-Series next-generation firewalls: Palo Alto Networks virtualized next-generation firewalls protect
your private and public cloud deployments by segmenting applications and preventing threats. VM-Series
firewalls are available for many public and private cloud technologies and provide the same world-class
level of detection and prevention of your physical next-generation firewalls.
Prisma SaaS: The use of software as a service (SaaS) applications is creating new risks and gaps in security
visibility for malware propagation, data leakage, and regulatory non-compliance. Prisma SaaS provides
complete visibility and granular enforcement across all user, folder, and file activity within sanctioned
SaaS applications, thus providing detailed analysis and analytics about usage without requiring any
additional hardware, software, or network changes.
Prisma Access: Prisma Access provides the full security capabilities of the Palo Alto Networks next-
Prisma Cloud: The Prisma Cloud security and compliance service uses machine learning to understand the
role and behavior of each cloud resource and enriches visibility by correlating data from external sources
such as vulnerability scanners, threat intelligence tools, and SIEMS. Information provided by Prisma Cloud
provide security personnel with unmatched insight into the threats detected in their environment.
Cortex Data Lake: The cloud-delivered logging service allows you to easily collect large volumes of log
data so that innovative apps can gain insight from your environment. You can simplify your log
infrastructure, automate log management, and use the insights gained from your data to prevent attacks
more effectively.
Cortex XDR – Analytics: Cortex XDR – Analytics behavioral analytics applies machine learning at a cloud
scale to network, endpoint, and cloud data so that you can quickly find and stop targeted attacks, insider
abuse, and compromised endpoints. Cortex XDR – Analytics uncovers the actions attackers cannot
conceal by profiling user and device behavior and identifying anomalies that indicate active attacks.
Cortex XDR – Analytics integrates rich metadata collected from the Security Operating Platform with
attack detection algorithms and enables you to detect post-intrusion activity with precision.
Sample Questions
1. Which component of the integrated Palo Alto Networks security solution limits network-
attached workstation access to a corporate mainframe?
A. threat intelligence cloud
B. advanced endpoint protection
C. next-generation firewall
D. tunnel inspection
2. Which Palo Alto Networks product is designed primarily to provide threat context with deeper
information about attacks?
A. Prisma Cloud
B. WildFire
C. AutoFocus
D. Threat Prevention
3. Which Palo Alto Networks product is designed primarily to provide normalization of threat
intelligence feeds with the potential for automated response?
A. MineMeld
B. WildFire
C. AutoFocus
D. Threat Prevention
A few features, such as the Decryption Broker, are supported only on firewalls that have larger compute
resources. The following link provides a features summary of all firewall models, including throughput:
https://www.paloaltonetworks.com/resources/datasheets/product-summary-specsheet
The Palo Alto Networks firewall was designed to use an efficient system referred to as next-generation
processing. Next-generation processing enables packet evaluation, application identification, policy
decisions, and content scanning in a single efficient processing pass.
Security Policy
The Security policy consists of security rules that are the basis of the firewall’s ability to enable or block
sessions. Multiple match conditions can be used when you create these rules. Security zones, source and
destination IP address, application (App-ID), source user (User-ID), service (port), HIP match, and URL
categories in the case of web traffic all can serve as traffic matching criteria for decisions to allow or
block. App-ID ensures the positive identification of applications regardless of their attempts at
evasiveness. Allowed session traffic can be scanned further based on Security Profiles (Content-ID) to
identify unwanted traffic content. These profiles use signatures to identify known threats. Unknown
threats are identified by WildFire, which creates signatures to turn them into known threats.
Examples of creating a policy rule security rules and profile settings follow:
All sessions on the firewall are defined by the source and destination zones. Rules can use these defined
zones to allow or deny traffic, apply QoS, or perform NAT. All traffic can flow freely within a zone and is
referred to as intrazone traffic. Traffic between zones (called interzone traffic) is denied by default.
Security policy rules are required to modify these default behaviors. Traffic is allowed to traverse
between zones only if a defined Security policy rule matches and allows the traffic. For interzone traffic,
Security policy rules must reference a source zone and destination zone (not interfaces) to allow or deny
traffic.
Security policies are used to create a positive (whitelist) and/or negative (blacklist) enforcement model
for traffic flowing through the firewall. These rules are enumerated from the top down, and the first rule
with the appropriate matching conditions will allow or deny the matching traffic. If logging is enabled on
the matching rule, and the traffic crosses a zone, the action for that session is logged. These logs are
©2016-2020, Palo Alto Networks, Inc. 27
extremely useful for adjusting the positive/negative enforcement model. The log information can be
used to characterize traffic, thus providing specific use information and allowing precise policy creation
and control. Log entries can be forwarded to external locations including email and web servers, syslog
servers, Panorama, and the Cortex Data Lake. Palo Alto Networks firewall logs, Application Command
Center, App Scope, and other reporting tools all work to precisely describe traffic and use patterns.
Additional information about best practices in designing and deploying your Security policy when
deploying a firewall as an edge device can be found here:
https://docs.paloaltonetworks.com/best-practices/9-1/internet-gateway-best-practices.html
Sample Questions
8. A potential customer says it wants to maximize the threat detection capability of its next-
generation firewall. Which three additional services should it consider implementing to
enhance its firewall’s capability to detect threats? (Choose three.)
A. Traps
B. WildFire
C. URL Filtering
D. Expedition
E. DNS Security
9. A VM-Series virtual firewall differs from a physical Palo Alto Networks firewall in which way?
A. A VM-Series firewall cannot be managed by Panorama.
B. A VM-Series firewall supports fewer traffic interface types.
C. A VM-Series firewall cannot terminate VPN site-to-site tunnels.
D. A VM-Series firewall cannot use dynamic routing protocols.
10. Which product would best secure east-west traffic within a public cloud implementation?
A. Prisma Cloud
B. MineMeld
C. VM-Series firewall
D. Cortex
HA Modes
Palo Alto Networks firewalls support stateful active/passive or active/active High Availability with session
and configuration synchronization with a few exceptions:
• The PA-200 (a discontinued model) firewall supports HA Lite only. HA Lite is an active/passive
deployment that provides configuration synchronization and some run-time data synchronization
such as IPsec security associations. It does not support session synchronization (HA2), and
therefore does not offer stateful failover.
• The VM-Series firewall in AWS supports active/passive HA only; if it is deployed with Amazon
Elastic Load Balancing (ELB), it does not support HA (in this case ELB provides the failover
capabilities).
• The VM-Series firewall in Microsoft Azure does support HA in PAN-OS 9x only.
• The VM-Series firewall deployed in Google Cloud Platform supports both active/active and
active/passive HA.
Public cloud deployments of VM-Series firewalls also are supported in each vendor’s version of a “scaled”
implementation, thus allowing virtual firewalls to share the traffic load through a deployment of parallel
firewall instances and the option to create or remove firewall instances in response to changes in traffic
loads. These deployments all include the cloud vendor’s load balancer deployed in front of the firewall
“scale set” to manage the spreading of the traffic across the available firewalls. This same deployment
practice also creates a High-Availability scenario in the sense that failing firewall instances can be
removed from the “scale set” automatically using various detection abilities within the load balancer. A
limitation of the “scale set” methods of High Availability is there typically is no synchronization between
firewalls, so failovers are disruptive in the sense that existing sessions are terminated.
Because one firewall is handling traffic and both firewalls share the same traffic interface configuration,
active/passive usually is much easier to manage.
Active/Active Clusters
Both firewalls in the pair are active and processing traffic and work synchronously to handle session setup
and session ownership. Both firewalls individually maintain session tables and routing tables and
synchronize to each other. Active/active HA is supported in virtual wire and Layer 3 deployments.
In active/active HA mode, the firewall HA interfaces cannot receive address via DHCP. Furthermore, only
the active-primary firewall’s traffic interface can function as a DHCP relay. The active-secondary firewall
that receives DHCP broadcast packets drops them.
In a Layer 3 deployment of HA active/active mode, you can assign floating IP addresses, which move from
one HA firewall to the other if a link or firewall fails. The interface on the firewall that owns the floating IP
address responds to ARP requests with a virtual MAC address.
Floating IP addresses are recommended when you need functionality such as the Virtual Router
Redundancy Protocol (VRRP). Floating IP addresses also can be used to implement VPNs and source NAT,
thus allowing for persistent connections when a firewall offering those services fails.
As shown in the figure that follows, each HA firewall interface has its own IP address and floating IP
address. The interface IP address remains local to the firewall, but the floating IP address moves between
the firewalls upon firewall failure. You configure the end hosts to use a floating IP address as its default
gateway, thus allowing you to load balance traffic to the two HA peers. You also can use external load
balancers to load balance traffic.
If a link or firewall fails or a path monitoring event causes a failover, the floating IP address and virtual
MAC address move over to the functional firewall. (In the figure that follows, each firewall has two
floating IP addresses and virtual MAC addresses; they all move over if the firewall fails.) The functioning
firewall sends a gratuitous ARP to update the MAC tables of the connected switches to inform them of
the change in floating IP address and MAC address ownership to redirect traffic to itself.
After the failed firewall recovers, by default the floating IP address and virtual MAC address move back to
firewall with the Device ID (0 or 1) to which the floating IP address is bound. More specifically, after the
failed firewall recovers, it becomes online. The currently active firewall determines that the firewall is
©2016-2020, Palo Alto Networks, Inc. 31
back online and checks whether the floating IP address it is handling belongs natively to itself or to the
other firewall. If the floating IP address originally was bound to the other Device ID, the firewall
automatically gives it back. An example of a floating IP deployment follows:
Each firewall in the HA pair creates a virtual MAC address for each of its interfaces that has a floating IP
address or ARP load-sharing IP address.
Information about data that is not synchronized between HA partners is at the following links:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/high-availability/reference-ha-
synchronization/what-settings-dont-sync-in-activepassive-ha.html
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/high-availability/reference-ha-
synchronization/what-settings-dont-sync-in-activeactive-ha.html
Sample Questions
11. Why would you recommend an active/active firewall cluster instead of an active/passive
firewall cluster?
A. Active/active is the preferred solution when the firewall cluster is behind a load balancer
that randomizes routing, thus requiring both firewalls to be active.
B. Active/active usually is the preferred solution because it allows for more bandwidth while
both firewalls are up.
C. Active/active is the preferred solution when the PA-7000 Series is used. Use
active/passive with the PA-5200 Series or smaller form factors.
D. Active/active is the preferred solution when the PA-5200 Series or smaller form factors
are used. Use active/passive with the PA-7000 Series.
12. Which two events can trigger an HA pair failover event? (Choose two.)
A. An HA1 cable is disconnected from one of the firewalls.
B. A dynamic update fails to download and install.
C. The firewall fails to ping a path-monitored destination address successfully.
D. OSPF implemented on the firewall determines that an available route is now down.
E. RIP implemented on the firewall determines that an available route is now down.
13. Which two firewall features support floating IP addresses in an active/active HA pair? (Choose
two.)
A. data-plane traffic interfaces
B. source NAT
C. VPN endpoints
D. loopback interfaces
E. management port
14. How are firewall configurations in an active/passive HA pair synchronized if the firewalls are
not under Panorama control?
A. An administrator commits the changes to one, then commits them to the partner, at
which time the changes are sent to the other.
B. An administrator pushes the configuration file to both firewalls, then commits them.
C. An administrator commits changes to one, which automatically synchronizes with the
other.
D. An administrator schedules an automatic sync frequency in the firewall configurations.
Tap
A network tap is a device that provides a way to access data flowing across a computer network. TAP
mode deployment allows you to passively monitor traffic flows across a network using a switch SPAN or
mirror port.
A switch SPAN or mirror port permits the copying of traffic from ports on the switch to the tap interface
of the firewall, providing a one-way flow of copied network traffic into the firewall. This configuration
allows the firewall to perform detection of traffic and threats but prevents any enforcement action from
taking place because the traffic does not flow through the firewall back to the environment.
By deploying the firewall in TAP mode, you can get visibility into which applications are running on the
network without having to make any changes to your network design. When the firewall is in TAP mode,
it also can identify threats on your network. Remember, however, that the traffic is not running through
the firewall when the firewall is in TAP mode, so no action can be taken on the traffic, including blocking
traffic with threats or applying QoS traffic control.
©2016-2020, Palo Alto Networks, Inc. 36
Details about configuring tap interfaces are here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/configure-interfaces/tap-
interfaces.html
Virtual Wire
In a virtual wire deployment, you install a firewall transparently on a network segment by binding two
firewall ports (interfaces) together. The virtual wire logically connects the two interfaces; hence, the
virtual wire is internal to the firewall.
Use a virtual wire deployment only when you want to seamlessly integrate a firewall into a topology and
the two connected interfaces on the firewall need not do any switching or routing. For these two
interfaces, the firewall is considered a bump in the wire.
A virtual wire deployment simplifies firewall installation and configuration because you can insert the
firewall into an existing topology without assigning MAC or IP addresses to the interfaces, redesigning the
network, or reconfiguring surrounding network devices. The virtual wire supports blocking or allowing
traffic based on virtual LAN (VLAN) tags. It also supports Security policy rules, App-ID, Content-ID, User-ID,
decryption, LLDP, active/passive and active/active HA, QoS, zone protection (with some exceptions), non-
IP protocol protection, DoS protection, packet buffer protection, tunnel content inspection, and NAT.
Each virtual wire interface is directly connected to a Layer 2 or Layer 3 networking device or host. The
virtual wire interfaces have no Layer 2 or Layer 3 addresses. When one of the virtual wire interfaces
receives a frame or packet, it ignores any Layer 2 or Layer 3 addresses for switching or routing purposes
but applies your security or NAT policy rules before passing an allowed frame or packet over the virtual
wire to the second interface and on to the network device connected to it.
You wouldn’t use a virtual wire deployment for interfaces that need to support switching, VPN tunnels, or
routing because they require a Layer 2 or Layer 3 address. A virtual wire interface doesn’t use an
Interface Management Profile, which controls services such as HTTP and ping and therefore requires the
interface to have an IP address.
All firewalls shipped from the factory have two Ethernet ports (ports 1 and 2) preconfigured as virtual
wire interfaces, and these interfaces allow all untagged traffic.
Layer 2
In a Layer 2 deployment, the firewall provides switching between two or more networks. Devices are
connected to a Layer 2 segment; the firewall forwards the frames to the proper port, which is associated
with the MAC address identified in the frame. Configure a Layer 2 interface when switching is required.
Layer 3
In a Layer 3 deployment, the firewall routes traffic between multiple ports using TCP/IP addressing.
Before you can configure Layer 3 interfaces, you must configure the virtual routers that you want the
firewall to use to route the traffic for each Layer 3 interface.
Layer 3 deployments require more network planning and configuration preparation than do most other
firewall interfaces but still are the most widely used in firewall deployments. Palo Alto Networks supports
both IPv4 and IPv6 simultaneously through a dual stack implementation when IPv6 is required.
Each Layer 3 interface must be configured with an IPv4 and/or an IPv6 address, zone name assignment,
and the attached virtual router that services the traffic on the interface. Options available to meet other
connectivity requirements include:
• NetFlow integration
• MSS adjustment
• MTU adjustment
• Binding of firewall services (ping responses, web management interface availability, etc.)
• Neighbor discovery for IPv6
• Manual MAC address assignment
• LLDP enablement
• Dynamic DNS support
• Link negotiation settings
Details about configuring Layer 3 interfaces and its options can be found here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/configure-interfaces/layer-3-
interfaces/configure-layer-3-interfaces.html
Decrypt Mirror
Decrypt mirror is a special configuration supporting the routing of decrypted traffic copies through an
external interface to a data loss prevention (DLP) service. Data loss prevention is a product category for
products that scan internet-bound traffic for keywords and patterns that identify sensitive information.
Specific information is here:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGDCA0
Aggregate Interfaces
An aggregate Ethernet (AE) interface group uses IEEE 802.1AX link aggregation to combine multiple
Ethernet interfaces into a single virtual interface that connects the firewall to another network device or
another firewall. An AE interface group increases the bandwidth between peers by load balancing traffic
across the combined interfaces. It also provides redundancy: When one interface fails, the remaining
interfaces continue to support traffic.
Aggregate interface creation begins with the definition of an Aggregate Interface group, after which
individual interfaces are added to the group.
Virtual Interfaces
Palo Alto Networks firewalls also provide several virtual interface types for additional functionality:
VLAN Interfaces
VLANs are logical interfaces that specifically serve as interconnects between on-board virtual switches
(VLANs) and virtual routers, which allows traffic to move from Layer 2 to Layer 3 within the firewall.
Loopback Interfaces
Loopback interfaces are Layer 3 interfaces that exist only virtually and connect to virtual routers in the
firewall. Loopback interfaces are used for multiple network engineering and implementation purposes.
They can be destination configurations for DNS sinkholes, GlobalProtect service interfaces (portals and
gateways), routing identification, and more.
Tunnel Interfaces
In a VPN tunnel setup, the Layer 3 interface at each end must have a logical tunnel interface for the
firewall to connect to and establish a VPN tunnel. A tunnel interface is a logical (virtual) interface that is
used to deliver traffic between two endpoints. If you configure any proxy IDs, the proxy ID is counted
toward any IPsec tunnel capacity.
The tunnel interface must belong to a security zone to apply policy and it must be assigned to a virtual
router to use the existing routing infrastructure. Ensure that the tunnel interface and the physical
interface are assigned to the same virtual router so that the firewall can perform a route lookup and
determine the appropriate tunnel to use.
The Layer 3 interface that the tunnel interface is attached to typically belongs to an external zone, for
example, the untrust zone. Although the tunnel interface can be in the same security zone as the physical
interface, for added security and better visibility you can create a separate zone for the tunnel interface.
If you create a separate zone for the tunnel interface, such as a VPN zone, you will need to create Security
policies to enable traffic to flow between the VPN zone and the trust zone.
A tunnel interface does not require an IP address to route traffic between the sites. An IP address is
required only if you want to enable tunnel monitoring or if you are using a dynamic routing protocol to
route traffic across the tunnel. With dynamic routing, the tunnel IP address serves as the next hop IP
address for routing traffic to the VPN tunnel.
If you are configuring the Palo Alto Networks firewall with a VPN peer that performs policy-based VPN,
you must configure a local and remote proxy ID when setting up the IPsec tunnel. Each peer compares
the proxy IDs configured on it with what actually is received in the packet to allow a successful IKE phase
2 negotiation. If multiple tunnels are required, configure unique proxy IDs for each tunnel interface; a
tunnel interface can have a maximum of 250 proxy IDs. Each proxy ID counts toward the IPsec VPN tunnel
capacity of the firewall, and the tunnel capacity varies by the firewall model.
Specific information about configuring tunnel interfaces can be found in the reference for Layer 3
interfaces.
Traffic Forwarding
All traffic that arrives at the firewall will be delivered either to an internal firewall process (destination
traffic) or be passed through a traffic interface (transit traffic). All transit traffic must be handed off to the
egress interface by a traffic handling object that matches the interface type. Examples of these objects
are VLAN objects (VLANs) for Layer 2 traffic, virtual routers for Layer 3 traffic, and virtual wires for virtual
wire interfaces.
IPsec tunnels are considered Layer 3 traffic segments for implementation purposes and are handled by
virtual routers as is any other network segment. Forwarding decisions are made by destination address,
not by VPN policy.
Virtual Routers
Because Layer 3 interfaces and their associated virtual routers are the most widely used deployment
options, a review of virtual routers follows.
A virtual router is a function of the firewall that participates in Layer 3 routing. The firewall uses virtual
routers to obtain routes to other subnets after you manually define static routes or through participation
in one or more Layer 3 routing protocols (dynamic routes). The routes that the firewall obtains through
these methods populate the IP routing information base (RIB) on the firewall. When a packet is destined
for a different subnet than the one it arrived on, the virtual router obtains the best route from the RIB,
places it in the forwarding information base (FIB), and forwards the packet to the next hop router defined
in the FIB. The firewall uses Ethernet switching to reach other devices on the same IP subnet. (An
exception to adding only a single optimal route to the FIB occurs if you are using ECMP, in which case all
equal-cost routes go in the FIB.)
The Ethernet, VLAN, and tunnel interfaces defined on the firewall receive and forward Layer 3 packets.
The destination zone is derived from the outgoing interface based on the forwarding criteria, and the
firewall consults policy rules to identify the Security policies that it applies to each packet. In addition to
You can configure Layer 3 interfaces on a virtual router to participate with dynamic routing protocols
(BGP, OSPFv2, OSPFv3, or RIP) and add static routes. You also can create multiple virtual routers, each
maintaining a separate set of routes that aren’t shared between virtual routers, which enables you to
configure different routing behaviors for different interfaces.
Each Layer 3 Ethernet, loopback, VLAN, and tunnel interface defined on the firewall must be associated
with a virtual router. Although each interface can belong to only one virtual router, you can configure
multiple routing protocols and static routes for a virtual router.
A firewall can have more than one router instance with each model supporting a different maximum. An
interface can be attached to one virtual router at a time. Virtual routers can route directly to each other
within the firewall.
Administrative Distance
Within the virtual router configuration, set administrative distances for types of routes as required for
your network. A virtual router that has two or more different routes to the same destination uses
administrative distance to choose the best path from different routing protocols and static routes by
preferring a lower distance.
Route Redistribution
Route redistribution on the firewall is the process of making routes that the firewall learned from one
routing protocol (or a static or connected route) available to a different routing protocol, thereby
increasing the number of reachable networks. Without route redistribution, a router or virtual router
advertises and shares routes only with other routers that run the same routing protocol. You can
redistribute IPv4 or IPv6 BGP, connected, or static routes into the OSPF RIB and redistribute OSPFv3,
connected, or static routes into the BGP RIB.
Route distribution means, for example, you can make specific networks that were once available only by
manual static route configuration on specific routers available to BGP autonomous systems or OSPF
areas. You also can advertise locally connected routes, such as routes to a private lab network, into BGP
autonomous systems or OSPF areas.
You might want to give users on your internal OSPFv3 network access to BGP so they can access devices
on the internet. In this case you would redistribute BGP routes into the OSPFv3 RIB.
Conversely, you might want to give your external users access to some parts of your internal network, so
you can make internal OSPFv3 networks available through BGP by redistributing OSPFv3 routes into the
BGP RIB.
Enablement of ECMP functionality on a virtual router allows the firewall to have up to four equal-cost
paths to a destination in its forwarding table, which allows the firewall to:
• Load balance flows (sessions) to the same destination over multiple equal-cost links
• Efficiently use all available bandwidth on links to the same destination rather than leave some
links unused
• Dynamically shift traffic to another ECMP member to the same destination if a link fails, rather
than having to wait for the routing protocol or RIB table to elect an alternative path/route.
Dynamic failover can help reduce downtime when links fail.
GRE Tunnels
A GRE tunnel connects two endpoints (a firewall and another device) in a point-to-point, logical link. The
firewall can terminate GRE tunnels; you can route or forward packets to a GRE tunnel. GRE tunnels are
simple to use and often are the tunneling protocol of choice for point-to-point connectivity, especially to
services in the cloud or to partner networks.
Create a GRE tunnel when you want to direct packets that are destined for an IP address to take a certain
point-to-point path, for example, to a cloud-based proxy or to a partner network. The packets travel in
the GRE tunnel (over a transit network such as the internet) to the cloud service while on their way to the
destination address. Thus, the cloud service can enforce its services or policies on the packets.
After the firewall allows a packet (based on a policy match) and the packet egresses to a GRE tunnel
interface, the firewall adds GRE encapsulation; it doesn’t generate a session. The firewall does no Security
policy rule lookup for the GRE-encapsulated traffic; therefore, you don’t need a Security policy rule for
the GRE traffic the firewall encapsulates. However, after the firewall receives GRE traffic, it generates a
session and applies all policies to the GRE IP header in addition to the encapsulated traffic. The firewall
treats the received GRE packet as it would any other packet.
If the firewall receives the GRE packet on an interface that has the same zone as the tunnel interface
associated with the GRE tunnel (for example, tunnel.1), the source zone is the same as the destination
zone. By default, traffic is allowed within a zone (intrazone traffic), so the ingress GRE traffic is allowed by
default.
However, if you configured your own intrazone Security policy rule to deny such traffic, you must
explicitly allow GRE traffic.
Because the firewall encapsulates the tunneled packet in a GRE packet, the additional 24 bytes of GRE
header automatically results in a smaller maximum segment size (MSS) in the maximum transmission unit
(MTU). If you don’t change the IPv4 MSS Adjustment Size for the interface, by default the firewall reduces
the MTU by 64 bytes (40 bytes of IP header + 24 bytes of GRE header).
This reduction means if the default MTU is 1,500 bytes, the MSS will be 1,436 bytes (1,500 − 40 − 24 =
1,436). If you configure an MSS adjustment size of 300 bytes, for example, the MSS will be only 1,176
bytes (1,500 − 300 − 24 = 1,176).
Routing of a GRE or IPsec tunnel to a GRE tunnel is not supported. However, you can route a GRE tunnel
to an IPsec tunnel. A GRE tunnel does not support QoS. The firewall does not support a single interface
acting as both a GRE tunnel endpoint and a decryption broker. GRE tunneling does not support NAT
between GRE tunnel endpoints.
Routing Troubleshooting
The routing decisions made by a virtual router can be diagnosed easily. A virtual router maintains a RIB
and a FIB, which can be displayed any time in the management web interface using the Runtime Stats
link displayed on the virtual router summary line:
Click the More Runtime Stats link to get access to the routing table (RIB) and the forwarding table (FIB)
with additional displays that contain the status of any enabled dynamic routing protocols.
A firewall’s default behavior is to store these logs in locally available storage. Firewall appliances have
fixed storage that can’t be expanded (except the 7000 Series). This storage is used in a “circular” fashion,
meaning that log entries are written until storage fills, at which point the oldest entries are overwritten.
Because storage size is fixed and logging rates depend in part on Security policy rule settings and traffic
rates, a firewall’s log retention period before entries are overwritten is difficult to predict.
For centralized logging and reporting, you also can use the Cortex Data Lake that is designed to work
seamlessly with Panorama. The Cortex Data Lake allows your managed firewalls to forward logs to the
Cortex Data Lake infrastructure instead of to Panorama or to the managed Log Collectors, so you can
augment your existing distributed log collection setup or scale your current logging infrastructure.
The Application Command Center (ACC) on Panorama provides a single pane for unified reporting across
all the firewalls. It enables you to centrally monitor network activity to analyze, investigate, and report on
traffic and security incidents. On Panorama, you can view logs and generate reports from logs forwarded
to the Cortex Data Lake, to Panorama, or to the managed Log Collectors, if configured, or you can query
the managed firewalls directly.
For example, you can generate reports about traffic, threat, and/or user activity in the managed network
based on logs stored on Panorama (and the managed collectors) or by accessing the logs stored locally on
the managed firewalls, or on the Cortex Data Lake.
©2016-2020, Palo Alto Networks, Inc. 48
If you don’t configure Log Forwarding to Panorama or the Cortex Data Lake, you can schedule reports to
run on each managed firewall and forward the results to Panorama for a combined view of user activity
and network traffic. Although reports don’t provide a granular drill-down on specific information and
activities, they provide a unified monitoring approach.
Panorama uses Log Collectors to aggregate logs from managed firewalls. When Panorama generates
reports, it queries the Log Collectors for log information that provides you visibility into all the network
activity that your firewalls monitor. Because you use Panorama to configure and manage Log Collectors,
they also are known as managed collectors. Panorama can manage two types of Log Collectors:
• Local Log Collector: This type of Log Collector runs locally on the Panorama management server.
Only an M-600, M-500 appliance, M-200, M-100 appliance, or Panorama virtual appliance in
Panorama mode supports a local Log Collector.
Note: If you forward logs to a Panorama virtual appliance in Legacy mode, it stores the logs locally
without a Log Collector.
• Dedicated Log Collector: This is an M-600, M-500, M-200, M-100 appliance, or Panorama virtual
appliance in Log Collector mode. You can use an M-Series appliance in Panorama mode or a
Panorama virtual appliance in Panorama or Legacy (ESXi and vCloud Air) mode to manage
Dedicated Log Collectors. Before you can use the Panorama web interface for managing
Dedicated Log Collectors, you must add them as managed collectors. Otherwise, administrative
access to a Dedicated Log Collector is available only through its CLI using the predefined
administrative user (admin) account. Dedicated Log Collectors don’t support additional
administrative user accounts.
You can use either or both types of Log Collectors to achieve the best logging solution for your
environment.
A Log Collector Group is 1 to 16 managed collectors that operate as a single logical log collection unit. If
the Log Collector Group contains Dedicated Log Collectors, Panorama uniformly distributes the logs
across all the disks in each Log Collector and across all Log Collectors in the group. This distribution
optimizes the available storage space. To enable a Log Collector to receive logs, you must add it to a Log
Collector Group. You can enable log redundancy by assigning multiple Log Collectors to a Log Collector
Group. The Log Collector Group configuration specifies which managed firewalls can send logs to the Log
Collectors in the group.
If an HA pair of Panoramas is configured to include Log Collectors, the Log Collectors function
independently from the HA relationship and both are independently active. They can be added to
different Collector Groups or to the same Collector Group.
The choice of platform is driven by your anticipated logging volume and the network topology the logging
data will traverse.
A complete discussions of log sizing and its impact on design can be found here:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Clc8CAC
The Panorama solution allows for flexibility in design by assigning these functions to different physical
pieces of the management infrastructure. For example, device management may be performed from a
VM Panorama, while the firewalls forward their logs to collocated dedicated Log Collectors:
Sample Questions
26. How are log retention periods on Palo Alto Networks firewalls increased?
A. add storage to any firewall model
B. increase the allocation for overall log storage within the firewall
C. turn on log compression
D. forward logs to external Log Collectors
27. How do you access and view firewall log data sent to the Cortex Data Lake?
A. direct viewing and searching with the Cortex gateway
B. Panorama using a Log Collector configuration for access
C. reporting in a firewall using a “remote data source” configuration
D. reporting in a firewall equipped with a “Remote Logging” plugin
28. Log retention is increased when a Dedicated Log Collector is used to collect logs from firewalls
in which two ways? (Choose two.)
A. turning on “Log Compression” in the Log Collector
B. adding storage capacity to the Log Collector
C. enabling “Log Storage Sharing” between the Log Collector and Panorama
D. adding Log Collectors to the Log Collector Group
The Panorama management server provides centralized monitoring and management of multiple Palo
Alto Networks next-generation firewalls and of WildFire appliances and appliance clusters. It provides a
single location from which you can oversee all applications, users, and content traversing your network,
and then uses this knowledge to create application enablement policies that protect and control the
network. Use of Panorama for centralized policy and firewall management increases operational
efficiency in managing and maintaining a distributed network of firewalls.
The PCNSE certification requires the candidate taking the test to have knowledge of Panorama firewall
management functions. The following information reviews these management concepts but does not
cover the remaining Panorama features.
Panorama uses device groups and templates to group firewalls into logical sets that require similar
configuration. You use device groups and templates to centrally manage all configuration elements,
policies, and objects on the managed firewalls. Panorama also enables you to centrally manage licenses,
software (PAN-OS software, SSL-VPN client software, GlobalProtect agent/app software), and content
updates (Applications and threats, WildFire, and Antivirus).
Panorama’s web interface management interface looks very much like the firewall’s management web
interface.
You can use the Device and Network tabs in Panorama to deploy a common base configuration to
multiple firewalls that require similar settings using a template or a template stack (a combination of
templates). When you manage firewall configurations with Panorama, you use a combination of device
groups (to manage shared policies and objects) and templates (to manage shared device and network
settings).
Templates and template stacks both support variables. Variables allow you to create placeholder objects
with their value specified in the template or template stack based on your configuration needs. Create a
template or template stack variable to replace IP addresses, group IDs, and interfaces in your
configurations. Template variables are inherited by the template stack and can be overridden to create a
template stack variable. However, templates do not inherit variables defined in the template stack. When
a variable is defined in the template or template stack and pushed to the firewall, the value defined for
the variable is displayed on the firewall.
To accommodate firewalls that have unique settings, you can use templates to override the template
stack configuration. Or you can push a broader, common base configuration and then override certain
pushed settings with firewall-specific values on individual firewalls. When you override a setting on the
firewall, the firewall saves that setting to its local configuration and Panorama no longer manages the
setting.
When you define a template stack, consider assigning firewalls that are the same hardware model and
require access to similar network resources, such as gateways and syslog servers. Grouping enables you
to avoid the redundancy of adding every setting to every template stack. The following figure shows an
example configuration in which you assign data center firewalls in the Asia-Pacific (APAC) region to a
stack with global settings, one template with APAC-specific settings, and one template with data center-
specific settings. To manage firewalls in an APAC branch office, you then can re-use the global and APAC-
specific templates by adding them to another stack that includes a template with branch-specific settings.
Templates in a stack have a configurable priority order that ensures Panorama pushes only one value for
any duplicate setting. Panorama evaluates the templates listed in a stack configuration from top to
bottom with higher templates having priority. The following figure also illustrates a data center stack in
which the data center template has a higher priority than the global template: Panorama pushes the idle
timeout value from the data center template and ignores the value from the global template.
You can create a device group hierarchy to nest device groups in a hierarchy of up to four levels, with
lower-level groups inheriting the settings (policy rules and objects) of higher-level groups. At the bottom
level, a device group can have parent, grandparent, and great-grandparent device groups (ancestors). At
the top level, a device group can have child, grandchild, and great-grandchild device groups
(descendants). All device groups inheriting settings from the Shared location, a container at the top of the
hierarchy for configurations that are common to all device groups.
Creation of a device group hierarchy enables you to organize firewalls based on common policy
requirements without redundant configuration. For example, you could configure shared settings that are
global to all firewalls, configure device groups with function-specific settings at the first level, and
configure device groups with location-specific settings at lower levels. Without a hierarchy, you would
have to configure both function-specific and location-specific settings for every device group in a single
level under Shared.
Device groups provide a way to implement a layered approach for managing policies across a network of
managed firewalls. A firewall evaluates policy rules by layer (shared, device group, and local) and by type
(pre-rules, post-rules, and default rules) in the order from top to bottom shown in the following figure.
When the firewall receives traffic, it performs the action defined in the first evaluated rule that matches
the traffic and disregards all subsequent rules. To change the evaluation order for rules within a particular
layer, type, and rule base (for example, shared Security pre-rules). Whether you view rules on a firewall
©2016-2020, Palo Alto Networks, Inc. 56
or in Panorama, the web interface displays them in evaluation order. All the shared, device group, and
default rules that the firewall inherits from Panorama are shaded orange. Local firewall rules display
between the pre-rules and post-rules. The rules with the orange shading in the following figure were
provided by Panorama and can be managed only from Panorama. They are read-only in local firewall
displays.
Objects are configuration elements that policy rules reference, for example: IP addresses, URL categories,
Security Profiles, users, services, and applications. Rules of any type (pre-rules, post-rules, default rules,
and rules locally defined on a firewall) and any rulebase (Security, NAT, QoS, Policy Based Forwarding,
Decryption, Application Override, Captive Portal, and DoS Protection) can reference objects. You can
reuse an object in any number of rules that have the same scope as that object in the device group
hierarchy.
For example, if you add an object to the Shared location, all rules in the hierarchy can reference that
shared object because all device groups inherit objects from Shared. If you add an object to a particular
device group, only the rules in that device group and its descendant device groups can reference that
device group object. If object values in a device group must differ from those inherited from an ancestor
device group, you can override inherited object values. You also can revert to inherited object values at
any time. When you create objects for use in shared or device group policy once and use them many
times, you reduce administrative overhead and ensure consistency across firewall policies.
When new policy rules are entered into a Panorama device group the device group and the pre or post
designation must be decided. The pre and post designations are chosen through selection of the
appropriate policy menu item, as shown in the following figure.
A commit to Panorama commits either the changes made by a chosen admin or all staged changes, as
shown in the following figures.
More information about the commit and push operations can be found here:
https://docs.paloaltonetworks.com/panorama/9-1/panorama-admin/panorama-overview/panorama-
commit-validation-and-preview-operations.html
©2016-2020, Palo Alto Networks, Inc. 60
Sample Questions
32. Where in Panorama do you enter Security policy rules to ensure that your new rules will take
precedence over locally entered rule?
A. Security policy rules with a targeted firewall
B. default rules section of Security policy rules
C. pre-rules section of Security policy rules
D. post-rules section of Security policy rules
33. In Panorama, how would you make changes to a Security policy rule for a specific firewall?
A. log in to Panorama, clone the rule, modify the clone, and add a target firewall to the new
rule
B. select the rule, click the override button, and enter the changes
C. create a new locally defined Security policy rule that is placed higher in the rule list than
the rule to be overridden
D. log in to Panorama and modify the original rule
34. Which three firewall settings are stored in Panorama device groups? (Choose three.)
A. User Identification configuration
B. custom Application-ID signatures
C. services definitions
D. DoS Protection Profiles
E. data-plane interface configurations
F. Zone Protection Profiles
G. Server Profile for an external LDAP server
The VM-Series firewall is available in the following models: VM-50 (Lite), VM-50, VM-100, VM-200, VM-
300, VM-500, VM-700, and VM-1000-HV.
All models can be deployed as guest virtual machines on VMware ESXi and vCloud Air, Citrix NetScaler
SDX, KVM and KVM in OpenStack, and Microsoft Hyper-V. In the public cloud environments—Amazon
Web Services, Azure, Google Cloud Platform, Oracle Cloud, Alibaba Cloud, and Cisco ACI—all models
except the VM-50 are supported; on VMware NSX, only the VM-100, VM-200, VM-300, VM-500, and VM-
1000-HV firewalls are supported. The software package (.xva, .ova, or .vhdx file) that is used to deploy the
VM-Series firewall is common across all models.
All VM-Series firewalls require a capacity license to enable full firewall functionality. After you apply the
capacity license on the VM-Series firewall, the model number and the associated capacities are
implemented on the firewall. Capacity is defined in terms of the number of sessions, rules, security zones,
address objects, IPsec VPN tunnels, and SSL VPN tunnels that the VM-Series firewall is optimized to
handle. To make sure that you purchase the correct model for your network requirements, use the
following table to learn the maximum capacity for each model and the capacity differences by model:
Public Clouds
The virtual firewalls can be found in the public cloud marketplaces. Most public cloud marketplaces are
populated with three virtual firewall choices that differ in their license requirements. A Bring Your Own
License (BYOL) version is an unlicensed VM-Series firewall requiring the customer to provide their
separately purchased capacity code and feature licenses after provisioning. The VM-Series Bundle 1 and 2
both are prelicensed versions of VM-300s. Bundle 1 is prelicensed for Threat Prevention only. Bundle 2 is
pre-licensed for Threat Prevention, WildFire, URL Filtering, and GlobalProtect. Bundle 1 and 2 versions of
the VM-300 incur a usage charge per hour of operation paid to the cloud vendor. The BYOL configuration
contains no premium rates above the costs of the component cloud resources.
These preconfigured VM-Series firewalls provided by the cloud vendor application stores usually consist
of three interfaces: one for management and one each for trusted and untrusted network traffic
connections. Most cloud deployments provide a way to modify the configuration through addition of
interface connections subjected to the methods and capacities of the cloud vendor.
Each VM-Series virtual firewall has a VM-Series plugin for the cloud vendor that implements certain
functionality such as High Availability. See the deployment documentation specific to your cloud vendor
for specific information: https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment.html
Sample Questions
35. Which part of a VM-Series firewall should be updated to provide maximum feature support for
a public cloud?
A. latest PAN-OS update
B. latest VM-Series plugin
C. capacity license for the target public cloud
D. latest dynamic updates appropriate for the implemented PAN-OS version
36. Which two types of firewall interfaces are most likely to be supported in public cloud
deployments? (Choose two.)
A. tap
B. virtual wire
C. Layer 3
D. tunnel
E. aggregate Ethernet
Public and private cloud deployments each have their own design and deployment considerations that
must be considered individually. Regardless of the type of deployed environment, centralized monitoring,
reporting, and management must be considered. The Panorama management solution can be deployed
in either type of cloud and can manage across cloud boundaries if required communication channels are
implemented.
Connectivity Considerations
Firewalls and Panorama each have connectivity requirements to reach outside services such as WildFire
and to consume updates such as dynamic updates. When Panorama is used to manage firewalls, the
devices must have a compatible communication channel between them. Hybrid deployments do not add
any unique communication requirements of their own; each environment must be engineered to provide
appropriate connectivity through its virtual networking environments as required. Engineering might
include the use of the firewall to connect cloud environments with any required routing responsibility.
Site-to-site VPNs often are used to interconnect cloud-based virtual networks. The Palo Alto Networks
firewalls can act as endpoints for these VPN connections and are subjected to VPN design and
configuration considerations.
Sample Question
38. Which two conditions must be met to manage Palo Alto Networks firewalls deployed in
multiple cloud environments from a central Panorama? (Choose two.)
A. The Panorama and firewall must be able to communicate.
B. The Panorama must be licensed for each cloud environment containing managed
firewalls.
C. The firewalls must have the latest VM-Series plugin installed.
D. The firewalls and Panorama must be running the same version of PAN-OS software.
E. Firewalls must be running a version of PAN-OS software equal to or less that that on
Panorama.
Sample Questions
39. A private cloud has 20 VLANs spread over five ESXi hypervisors, managed by a single vCenter.
How many firewall VMs are needed to implement microsegmentation?
A. one
B. four
C. five
D. 20
40. When you deploy the Palo Alto Networks NGFW on NSX, packets coming to an application VM
from VMs running on different hardware go through which modules?
A. network, vSwitch, NSX firewall, Palo Alto Networks NGFW, application VM
B. network, vSwitch, Palo Alto Networks NGFW, NSX firewall, application VM
C. network, vSwitch, NSX firewall, Palo Alto Networks NGFW, NSX firewall, application VM
D. vSwitch, network, Palo Alto Networks NGFW, NSX firewall, application VM
41. Which option shows the interface types that ESXi supports in the VM-Series firewalls?
A. tap, Layer 2, Layer 3, virtual wire
B. Layer 3 only
C. tap, Layer 2, Layer 3
D. Layer 3, virtual wire
Administrative accounts specify roles and authentication methods for the administrators of Palo Alto
Networks firewalls and Panorama. Each device has a predefined default administrative account (admin)
that provides full read-write access (also known as superuser access) to the firewall. Other administrative
accounts can be created as needed.
You configure administrator accounts based on the security requirements of your organization, any
existing authentication services that your network uses, and the required administrative roles. A role
defines the type of system access that is available to an administrator. You can define and restrict access
as broadly or granularly as required, depending on the security requirements of your organization. For
example, you might decide that a data center administrator can have access to all device and networking
configurations, but a security administrator can control only Security policy definitions, while other key
individuals can have limited CLI or XML API access. The role types are:
• Dynamic Roles: These are built-in roles that provide access to Panorama and managed firewalls.
After new features are added, the firewall and Panorama automatically update the definitions of
dynamic roles; you never need to manually update them. The following table lists the access
privileges associated with dynamic roles.
• Admin Role Profiles: To provide more granular access control over the functional areas of the
web interface, CLI, and XML API, you can create custom roles. After new features are added to
the product, you must update the roles with corresponding access privileges: the firewall and
Panorama do not automatically add new features to custom role definitions
Authentication
Authentication is a method for protecting services and applications by verifying the identities of users so
that only legitimate users have access. Several firewall and Panorama features require authentication.
Administrators authenticate to access the web interface, CLI, or XML API of the firewall and Panorama.
End users authenticate through Captive Portal or GlobalProtect to access various services and
©2016-2020, Palo Alto Networks, Inc. 67
applications through the firewall. You can choose from several authentication services to protect your
network and to accommodate your existing security infrastructure while ensuring a smooth user
experience.
If you have a public key infrastructure, you can deploy certificates to enable authentication without users
having to manually respond to login challenges. Alternatively, or in addition to certificates, you can
implement interactive authentication, which requires users to authenticate using one or more methods.
When user or administrative access is configured, one or more authentication methods must be
specified. A user/administrator definition typically requires an Authentication Profile that specifies the
desired authentication method. When more than one method is desired, you can instead use an
Authentication Sequence, which is a list of Authentication Profiles. The first profile will be accessed. If it is
not available, the next option will be tried. An Authentication Profile specifies a single Server Profile. A
Server Profile contains specific configuration and access information necessary to reach the external
authentication service.
Detailed information about creating Authentication Profiles and sequences can be found here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/authentication/configure-an-
authentication-profile-and-sequence.html
The Multi-Factor Authentication Server Profile shown can be a part of multiple authentication challenges
that a user must respond to. For example, you can force users to enter a login password and then enter a
verification code that they receive by phone before they can access critical financial documents.
The firewall challenges a user with a Captive Portal. Captive Portal configuration includes an
Authentication Profile selected for base configuration that represents the first challenge a user must
negotiate.
Sample Questions
42. To configure multi-factor authentication for users accessing services through the firewall,
which three configuration pieces need to be addressed? (Choose three.)
A. GlobalProtect Portal
B. Captive Portal
C. Authentication Enforcement Profile
D. Authentication Profile
E. Response pages
In a typical public key infrastructure (PKI) scheme, the certificate issuer is a certificate authority (CA),
usually a company that charges customers to issue certificates for them. Certificate authorities also can
be created and managed by individuals and organizations requiring certificates for internal use.
A CA is responsible for signing certificates. These certificates act as an introduction between two parties,
which means that a CA acts as a trusted third party. A CA processes requests from people or
organizations requesting certificates (called subscribers), verifies the information, and potentially signs an
end-entity certificate based on that information. To perform this role effectively, a CA needs to have one
or more broadly trusted root certificates or intermediate certificates and the corresponding private keys.
CAs may achieve this broad trust by having their root certificates included in popular software, or by
obtaining a cross-signature from another CA delegating trust.
A receiving entity is responsible for validating the information contained in a certificate presented to it.
Among the potential verification tests is a validation that the certificate was issued by the issuing CA
information contained in the certificate. This verification requires the CA’s signing key contained in its
Root Certificate used to sign all issued certificates. This certificate must be locally available to the
receiving entity to run the validation test. These CA Root Certificates often are kept in locally stored
certificate caches in the hosting OS or a browser or program-managed certificate cache. The firewall also
contains a CA Root Certificate cache.
Included in this certificate information are settings that choose whether this certificate is self-signed or
signed by another certificate stored in the firewall (the Signed By field). The Certificate Authority check
box determines whether this certificate will have the rights to sign other certificates.
After you enter the appropriate data and click the Generate button, a new certificate is created and its
private and public keys are added to the firewall’s storage. The resultant certificate then can be exported
with or without the private key for external use.
In cases where a certificate needs to be generated by an external CA, a certificate signing request (CSR)
file can be created on the firewall that is exported and transferred to the CA. This file contains the
required information for certificate creation. Select the External Authority option in the Signed By field
to trigger this generation.
Sample Questions
45. A Palo Alto Networks firewall can obtain a certificate for its internal use through which three
methods? (Choose three.)
A. import a certificate file generated by an external CA
B. reference an externally stored certificate by a URL configured in an SSL/TLS Service
Profile
C. generate a certificate directly by manually entering certificate data
D. obtain a certificate from an SCEP server using an SCEP Profile
E. import a certificate from an external CA by using an Authentication Profile
46. Which two resources must be available to successfully run certificate validation tests on a
certificate received from an external source? (Choose two.)
A. Root Certificate of the issuing CA
B. public key for the received certificate
C. OCSP connection address
D. existing Certificate Profile that matches the received certificate’s CA identity
These routing protocols are implemented on TCP/IP networks and are supported as optional
configurations in a firewall’s virtual router.
Each virtual router instance can be configured separately for dynamic routing, with each router
maintaining separate routing tables (RIBs). Each router instance has a RIB and forwarding table (FIB) that
are used during packet processing to identify the appropriate interface for packet egress.
A virtual router can share routes between router protocols using Redistribution Profiles. You can
redistribute IPv4 or IPv6 BGP, connected, or static routes into the OSPF RIB and redistribute OSPFv3,
connected, or static routes into the BGP RIB.
Administrative Distance
Within the virtual router configuration, set administrative distances for types of routes as required for
your network. A virtual router that has two or more different routes to the same destination from
different routing protocols uses administrative distance to choose the best path from different routing
protocols and static routes by preferring a lower distance.
©2016-2020, Palo Alto Networks, Inc. 78
Sample Questions
47. The firewall uses which information to determine which interface to use for a packet’s egress?
A. manually configured static routes
B. routing information base (RIB)
C. appropriate Redistribution Profile
D. ECMP destination monitoring results
48. A virtual router can use a Redistribution Profile to share routes between which three routing
protocols? (Choose three.)
A. static routes
B. IGRP
C. RIP
D. OSPF
E. multicast
49. How does a firewall determine which route to use when its RIB is populated with multiple
routes to the same location, but the routes were added by different routing protocols?
A. according to the following precedence of route type: static, RIP, OSPF, BGP
B. using the virtual router’s FIB
C. using the associated route’s metric and choosing the lowest value
D. using the route’s administrative distance and choosing the lowest value
Zone design itself provides segmentation of networks, which magnifies the protection of Zone Protection
Profiles. A discussion of zone design through the lens of protection can be found here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/zone-protection-and-dos-protection/how-
do-zones-protect-the-network.html
Zone Protection Profiles provide a broad defense of the entire zone based on the aggregate traffic
entering the zone, thus protecting against flood attacks and undesirable packet types and options. Zone
Protection Profiles don’t control traffic between zones, they control traffic only at the ingress zone. Zone
Protection Profiles don’t consider individual IP addresses because they apply to the aggregate traffic
entering the zone (DoS Protection policy rules defend individual IP addresses in a zone). This protection
occurs early in the traffic processing flow, thus minimizing firewall resource use.
DoS Protection is resource-intensive, so use it only for critical systems. As is the case with Zone Protection
Profiles, DoS Protection Profiles specify flood thresholds. DoS Protection policy rules determine the
devices, users, zones, and services to which DoS Profiles apply.
DoS Protection Profiles set the protection thresholds to provide DoS protection against flooding of new
sessions for IP floods (CPS limits) to provide resource protection (maximum concurrent session limits for
specified endpoints and resources) and to configure whether the profile applies to aggregate or classified
traffic. DoS Protection policy rules control where to apply DoS protection and which action to take when
traffic matches the criteria defined in the rule.
Unlike a Zone Protection Profile, which protects only the ingress zone, DoS Protection Profiles and policy
rules can protect specific resources inside a zone and traffic flowing between different endpoints and
areas. Unlike the case with a Zone Protection Profile, which supports only aggregate traffic, you can
configure aggregate or classified DoS Protection Profiles and policy rules.
An exploration of DoS attacks and defending against them using Palo Alto Networks firewalls is here:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClOGCA0
Sample Questions
50. For which two reasons are denial-of-service protections applied by zone? (Choose two.)
A. because denial-of-service protections are applied early in the processing, before much
information is known about the connection but when the ingress interface already is
known
B. because denial-of-service protections are applied only when manually turned on to avoid
quota overload (which would make denial of service easier)
C. because denial-of-service protections can depend on only the zone, and never on port
numbers or IP addresses
D. because denial-of-service protections on a Layer 3 interface are different from the denial-
of-service protections available on a Layer 2 interface and interfaces on virtual wires
51. SYN flood protection provides flood protection from which protocol?
A. UDP
B. TCP
C. ICMP
D. GRE
52. To which two protocols does port scan reconnaissance protection apply? (Choose two.)
A. UDP
B. TCP
C. GRE
D. ICMP
E. IPX
53. In which two places do you configure flood protection? (Choose two.)
A. DoS Protection Profile
B. QoS Profile
C. Zone Protection Profile
D. SYN Protection Profile
E. XOFF Profile
54. Which two firewall features should be used to provide tailored DoS protection to a specific
address? (Choose two.)
A. Zone Protection Profiles
B. virtual routers
C. Server Profiles
D. DoS policy rules
E. DoS Protection Profiles
Decryption
The Secure Sockets Layer (SSL) and Secure Shell (SSH) encryption protocols secure traffic between two
entities, such as a web server and a client. SSL encapsulates traffic, encrypting data so that it is
meaningless to entities other than the client and server with the certificates to affirm trust between the
devices and the keys to decode the data. (SSH does not use certificates to encrypt or decrypt traffic.)
Decrypt SSL and SSH traffic to:
• Prevent malware concealed as encrypted traffic from being introduced into your network. For
example, an attacker compromises a website that uses SSL encryption. Employees visit that
website and unknowingly download an exploit or malware. The malware then uses the infected
employee endpoint to move laterally through the network and compromise other systems.
• Prevent sensitive information from moving outside the network
• Ensure the appropriate applications are running on a secure network
• Selectively decrypt traffic; for example, create a Decryption policy and profile to exclude traffic
for financial or healthcare sites from decryption
Palo Alto Networks firewall decryption is policy-based and can decrypt, inspect, and control inbound and
outbound SSL and SSH connections. A Decryption policy enables you to specify traffic to decrypt by
destination, source, service, or URL category, and to block, restrict, or forward the specified traffic
according to the security settings in the associated Decryption Profile. A Decryption Profile controls SSL
protocols, certificate verification, and failure checks to prevent traffic that uses weak algorithms or
unsupported modes from accessing the network. The firewall uses certificates and keys to decrypt traffic
to plaintext, and then enforces App-ID and security settings on the plaintext traffic, including Decryption,
Antivirus, Vulnerability, Anti-Spyware, URL Filtering, WildFire, and File Blocking Profiles. After decrypting
and inspecting traffic, the firewall re-encrypts the plaintext traffic as it exits the firewall to ensure privacy
and security.
The firewall provides three types of Decryption policy rules: SSL Forward Proxy to control outbound SSL
traffic, SSL Inbound Inspection to control inbound SSL traffic, and SSH Proxy to control tunneled SSH
traffic. You can attach a Decryption Profile to a policy rule to apply granular access settings to traffic, such
as checks for server certificates, unsupported modes, and failures.
SSL decryption (both forward proxy and inbound inspection) requires certificates to establish the firewall
as a trusted third party, and to establish trust between a client and a server to secure an SSL/TLS
connection. You also can use certificates when excluding servers from SSL decryption for technical
reasons (the site breaks decryption for reasons such as certificate pinning, unsupported ciphers, or
mutual authentication). SSH decryption does not require certificates.
©2016-2020, Palo Alto Networks, Inc. 84
A review of decryption concepts can be found here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/decryption/decryption-concepts.html
Decryption Broker
A firewall acting as a decryption broker uses dedicated decryption forwarding interfaces to send
decrypted traffic to a security chain—a set of inline, third-party security appliances—for additional
analysis. Two types of security chain networks are supported with a decryption broker (Layer 3 security
chains and Transparent Bridge security chains), and you also can configure the firewall to direct traffic
through the security chain unidirectionally or bidirectionally. A single firewall can distribute decrypted
sessions among up to 64 security chains and can monitor security chains to ensure that they are
effectively processing traffic.
Decryption Mirror
Palo Alto Networks firewalls can automatically send a copy of decrypted traffic to a specified interface
using the Decryption Mirroring feature. This option can be licensed at no cost for midrange and high-end
firewalls that can automatically forward copies of decrypted traffic to external DLP products.
Palo Alto Networks firewall decryption is policy-based and can be used to decrypt, inspect, and control
both inbound and outbound SSL and SSH connections. Decryption policies allow you to specify traffic for
decryption according to destination, source, or URL category and to block or restrict the specified traffic
according to your security settings. The firewall uses certificates and keys to decrypt the traffic specified
After traffic is decrypted and inspected on the firewall, the plaintext traffic is re-encrypted as it exits the
firewall to ensure privacy and security.
Central to this discussion is the role of digital certificates to secure SSL encrypted data. Your
understanding of this role and planning for proper certificate needs and deployment are important
considerations in decryption use.
The use of certificates is central to other important firewall functions in addition to decryption. This need
led to the implementation of extensive certificate management capabilities on the firewall.
Decryption Policies
Ingress traffic decryption is controlled by Decryption policies. Palo Alto Networks firewalls automatically
will detect encrypted traffic and react by evaluating the Decryption policy rules. If a matching policy rule
is found, the firewall will attempt to decrypt the traffic according to the policy rule’s specified decryption
action. Normal packet processing resumes afterward.
Note that SSL Forward Proxy replaces the original certificate from the server with one signed by a
different key that then is delivered to the client.
Decryption Exclusions
A developer of a solution using SSL decryption can take extra programmatic steps to interrogate the
certificate received at the client for specific characteristics present in the original certificate. When these
characteristics are not found, the author often assumes that a decrypting process is in the middle of the
conversation and may act to prevent full functionality and consider this presence a security risk. These
products typically are not fully functional in a decrypting environment and must be added as exceptions
to Decryption policy rules.
Palo Alto Networks recognizes this fact and provides a mechanism to mark certain encrypted traffic for
decryption bypass. A list of SSL sites with known decryption issues is predefined on the Palo Alto
Networks firewall. You can add sites to this list using the SSL Decryption Exclusion option in the
management web interface. The firewall does not attempt to decrypt traffic to or from these sites.
Sample Questions
55. Which feature is not negatively affected by the lack of a Decryption policy?
A. antivirus
B. App-ID
C. file blocking
D. network address translation
56. How can the next-generation firewall inform web browsers that a web server’s certificate is
from an unknown CA?
A. show a “the certificate is untrusted, are you SURE you want to go there” response page
before accessing the website
B. relay the untrusted certificate directly to the browser
C. have two certificates in the firewall, one used for sites whose original certificate is
trusted, and the other for sites whose original certificate is untrusted
D. have two certificate authority certificates in the firewall, one used to produce certificates
for sites whose original certificate is trusted and the other used for certificates for sites
whose original certificate is untrusted
57. Which two firewall features can be used to support an organization’s requirement of
decrypting and recording all encrypted traffic? (Choose two.)
A. Decryption Broker
B. Policy Based Forwarding
C. Default Router setting of Forward Cleartext
D. Interface setting of Decryption Port Mirroring
E. Decryption policy rule action set to Forward Cleartext
Unlike the App-ID engine, which inspects application packet contents for unique signature elements, the
Application Override policy’s matching conditions are limited to header-based data only. Traffic matched
by an Application Override policy is identified by the App-ID entered in the Application field.
Choices are limited to applications currently in the App-ID database. Because an existing App-ID must be
chosen for the policy, the administrator should add a new App-ID to the database for this purpose.
Details about creating an App-ID entry for this purpose can be found here:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClVLCA0
Because this traffic bypasses all Layer 7 inspection, the resulting security is that of a Layer 4 firewall.
Thus, this traffic should be trusted without the need for Content-ID inspection. The resulting application
assignment can be used in other firewall functions such as Security policy rules and QoS.
Use Cases
Three primary uses cases for Application Override policy are:
• To identify “Unknown” App-IDs with a different or custom application signature
• To re-identify an existing application signature
• To bypass the Signature Match Engine (within the SP3 architecture) to improve processing times
Name is displayed in
ACC, logs, and reports
Sample Questions
58. An App-ID used in an Application Override policy rule should have which characteristic?
A. existing App-ID that uses the same decoder
B. new App-ID with no signature information
C. new App-ID with the “custom” property set to yes
D. any existing App-ID with compatible characteristics
59. Which type of identification is disabled by Application Override?
A. Protocol-ID
B. User-ID
C. Content-ID
D. URL Filtering
If you configure Authentication policy, your firewalls also must redistribute the authentication
timestamps that are generated when users authenticate to access applications and services. Firewalls use
the timestamps to evaluate the timeouts for Authentication policy rules. The timeouts allow a user who
successfully authenticates to later request services and applications without authenticating again within
the timeout periods. Redistribution of timestamps enables you to enforce consistent timeouts across all
the firewalls in your network.
Firewalls share user mappings and authentication timestamps as part of the same redistribution flow; you
don’t have to configure redistribution for each information type separately.
References
• Redistribute User Mappings and Authentication Timestamps
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/user-id/deploy-user-id-in-a-large-
scale-network/redistribute-user-mappings-and-authentication-timestamps.html
• User-ID Redistribution Using Panorama
https://docs.paloaltonetworks.com/panorama/9-1/panorama-admin/panorama-overview/user-
id-redistribution-using-panorama.html
Sample Questions
61. Which configuration must be made on the firewall before it can read User-ID-to-IP-address
mapping tables from external sources?
A. Group Mapping Settings
B. Server Monitoring
C. Captive Portal
D. User-ID Agents
VM-Series Bootstrapping
Bootstrapping allows you to create a repeatable and streamlined process of deploying new VM-Series
firewalls on your network because it allows you to create a package with the model configuration for
your network and then use that package to deploy VM-Series firewalls anywhere. You can bootstrap the
VM-Series firewall off an external device (such as a virtual disk, a virtual CD-ROM, or a storage bucket
such as AWS S3 or Google Cloud bucket) to complete the process of configuring and licensing the VM-
Series firewall. You can either bootstrap the firewall with basic initial configuration and licenses so that
the firewall can register with Panorama and then retrieve its full configuration from Panorama, or you can
bootstrap the complete configuration so that the firewall is fully configured on boot-up.
Bootstrap Package
The bootstrap process is initiated only when the firewall starts up in a factory default state. After you
attach the virtual disk, virtual CD-ROM, or storage bucket to the firewall, the firewall scans for a bootstrap
package and, if one exists, the firewall uses the settings defined in the bootstrap package. If you have
included a Panorama server IP address in the file, the firewall connects with Panorama. If the firewall has
internet connectivity, it contacts the licensing server to update the UUID and obtain the license keys and
subscriptions. The firewall then is added as an asset in the Palo Alto Networks Support Portal. If the
firewall does not have internet connectivity, it either uses the license keys you included in the bootstrap
package or it connects to Panorama, which retrieves the appropriate licenses and deploys them to the
managed firewalls.
The bootstrap package that you create must include the /config, /license, /software, and /content
folders, even if empty:
• /config folder: Contains the configuration files. The folder can hold two files: init-cfg.txt and the
bootstrap.xml.
Note: If you intend to pre-register VM-Series firewalls with Panorama with bootstrapping, you
must generate a VM auth key on Panorama and include the generated key in the init-cfg file.
• /license folder: Contains the license keys or auth codes for the licenses and subscriptions that you
intend to activate on the firewalls. If the firewall does not have internet connectivity, you must
either manually obtain the license keys from the Palo Alto Networks Support portal or use the
Licensing API to obtain the keys and then save each key in this folder.
The bootstrapping volume must be prepared according to the specific information outlined here:
https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/bootstrap-the-vm-series-
firewall.html
Sample Questions
64. When will a firewall check for the presence of bootstrap volume?
A. each time it cold-boots
B. each time it boots from a factory default state
C. when a firewall is started in maintenance mode
D. each time it warm-boots
65. Where in the bootstrap volume directories is a required dynamic update file?
A. /config
B. /license
C. /software
D. /content
66. Can a firewall’s PAN-OS software be updated by the bootstrap process?
A. Yes, by including a copy of the desired PAN-OS software in the /software folder of the
bootstrap volume.
B. Yes, by including a copy of the desired PAN-OS software in the /content folder of the
bootstrap volume.
C. No, it must be updated by an administrator after the firewall starts.
D. No, the firewall must be licensed first.
You must commit your firewall configuration after you have created a DUG and added it to a policy rule.
However, you do not have to perform a commit when users are added to or removed from a DUG. User
membership in a DUG is dynamic and controlled through tagging and untagging of usernames. Because
updates to DUG membership are automatic, the use of DUGs instead of a static group (like an LDAP
group) enables you to respond to changes in user behavior or potential threats without manual policy
changes.
Several methods are available to tag or untag usernames. As shown in the following screenshot, you can
manually tag and untag usernames using the web interface:
DUG Operation
DUGs enable you to create a Security policy that provides autoremediation in response to user behavior
and activity. Autoremediation reduces administrative burden by automating the firewall’s response to
user activity. Autoremediation using DUGs also reduces the firewall’s response time to malicious activity,
which provides better security for your environment.
In the illustration shown in the following screenshot, a user’s traffic is recorded in the firewall logs. You
can analyze these logs directly on the firewall or you can configure log forwarding to forward the logs to a
third-party system for analysis. If logs are being analyzed locally on the firewall, the log forwarding
configuration can invoke a new built-in action that will associate a tag with a username based on one or
more events in a log. A third-party system also can associate a tag with a username using the PAN-OS
XML API. Username-tag registrations are recorded in and maintained by a User-ID agent.
The firewall uses these username-tag pairs to determine which users are currently members of a DUG.
When you configure a DUG you associate it with one or more tags. Any user that also is associated with a
tag configured in a DUG becomes a member of the DUG. DUG membership then is used to determine
future policy rule matches. As examples, a Security policy could block a user, an Authentication policy
could force the user to use MFA, or a Decryption policy could force the user’s traffic to be decrypted.
All this data can be analyzed in the firewall’s logs, on a SIEM, in a user and entity behavior analytics
system, or using a variety of tools available to a SOC. Any of these tools can be configured to tag or untag
a username, depending on the results of the analysis. Tagging and untagging of a username determines
whether it is a member of a DUG. Then DUG membership and policy configuration determine how the
firewall should treat the user’s network traffic.
The second example illustrates how to use a DUG to implement time-based access controls for workers
that might require only short-term access to network resources. In this case, you create a DUG and add it
to policies that control user access to network resources. You then can add a time-based tag to a
username. A tagged username is a member of the DUG and network access is permitted by the DUG.
When the time-based tag expires, the user’s membership in the DUG is terminated along with the
network access that was provided by the DUG.
You also must configure User-ID on your firewalls. The dynamic tags are registered and unregistered from
the User-ID agent either on the local firewall, a remote firewall, or Panorama.
To use DUGs to invoke autoremediation, you will need to create at least two Security policy rules: one to
allow initial traffic to populate the DUG and another rule to deny traffic for the activity you want to
prevent. To ensure that users are tagged, the rule to allow traffic must have a higher rule number in your
rulebase than the rule that denies traffic. The following screenshot illustrates how the two rules would be
configured. The application is “any” for illustration purposes, but this configuration is not a
recommended best practice:
For additional information about configuring and using DUGs, see the PAN-OS® 9.1 Administrator’s Guide
at https://docs.paloaltonetworks.com.
Software-defined wide-area network (SD-WAN) is a technology that enables you to use multiple internet
services and private services to create an intelligent and dynamic WAN. The SD-WAN plugin is integrated
with PAN-OS 9.1, which provides you with the security features of a PAN-OS 9.1 firewall combined with
SD-WAN functionality. You can install the SD-WAN plugin on the Panorama management server.
Panorama provides the means to centrally configure and manage your firewalls and SD-WAN
environment. Panorama enables you to change and monitor your network configuration from a
centralized location rather than configuring and monitoring each firewall individually. You can configure
and manage your SD-WAN environment from the Panorama web interface or the Panorama REST API.
Initial Planning
Planning is a critical part of deploying your SD-WAN environment. In your SD-WAN configuration, you
must configure one or more VPN clusters to determine which branch offices will communicate with which
hub. A VPN creates a secure connection between the branch and hub devices. VPN clusters are a logical
grouping of devices, and you should consider geographical location or function when you group your
devices.
You also may have cloud-based services for which you want the internet traffic to flow directly from
branch office to the cloud using direct internet access (DIA). Use of DIA can prevent SaaS, web browsing,
or heavy-bandwidth applications from having to flow from branch office to the hub to the cloud and back.
During the initial planning stages, you will need to determine the ISP link types and maximum
upload/download bandwidth that will be used at each branch and hub. ISP link types include ADSL/DSL,
cable modem, Ethernet, fiber, LTE/3G/4G/5G, MPLS, microwave/radio, satellite, and WiFi.
You will need to gather the public IP addresses, private network prefixes, and serial numbers of your
branch and hub firewalls. The firewall must have an internet-routable, public IP address to initiate and
As part of the planning process you will decide on the naming conventions for your sites and SD-WAN
devices. If you already have zones in place before configuring SD-WAN, you should decide how to map
those zones to the predefined zones that SD-WAN uses for path selection. You will map an existing zone
to a predefined zone named zone-internal, To_Hub, To_Branch, or zone-internet.
You can create Panorama templates using a CSV file and then push the configuration to the branch or hub
firewalls. From Panorama you can export an empty SD-WAN device CSV file and then populate the CSV
file with the branch and hub information. The information you will enter in to a CSV includes serial
number, type of device (branch or hub), names of zones to map to predefined zones, loopback address,
prefixes to redistribute, AS number if you use BGP dynamic routing, router ID, and virtual router name.
Next, identify the applications that require QoS policies so you can prioritize bandwidth. The applications
that require QoS policies should be the same applications you identified as critical or latency-sensitive.
Start with the most critical and latency-sensitive applications first because you can add applications after
your SD-WAN is functioning smoothly.
Link Failover
Link failover enables you to determine how and when a link will fail over to a different link if the original
link degrades or fails. You can determine which path monitoring mode to use for each link, although we
recommend that you use the default setting for the link type:
• Aggressive: The firewall sends probe packets to the opposite end of the SD-WAN link at a
constant frequency, five probes per second by default. Aggressive mode is appropriate for links
where monitoring path quality is critical or where you need fast detection and failover for
brownout and blackout conditions. Aggressive mode provides subsecond detection and failover.
• Relaxed: The firewall observes a configurable idle time between sending probe packets at the
probe frequency you configure. Use relaxed mode to make path monitoring less frequent than
aggressive mode. Relaxed mode is appropriate for links that have very low bandwidth, links that
are expensive to operate, such as satellite or LTE, or when fast detection is not as important as
preserving cost and bandwidth.
©2016-2020, Palo Alto Networks, Inc. 102
When you plan link failover, you should prioritize the order in which the firewall selects the first link for a
new session and the order in which links should be a candidate to replace a link that is failing over, if
there is more than one candidate.
For the applications and services, you should plan your path health thresholds at which you consider a
path to have degraded enough in quality that you want the firewall to select a new path or fail over. The
quality characteristics are latency (range is 10 to 2,000ms), jitter (range is 10 to 1,000ms), and packet loss
percentage.
Routing
When you plan your SD-WAN environment, you should determine how your traffic will be routed
between the branches and hubs. You can choose to use dynamic routing with BGP or static routing. If you
choose dynamic routing, then plan BGP route information, including the four-byte autonomous system
number (ASN). Each firewall site is in a separate AS and therefore must have a unique ASN. Each firewall
also must have a unique Router ID. Panorama will push BGP configurations to the branches and hubs to
dynamically route traffic between them.
If you do not want to use BGP dynamic routing, then plan to use the Panorama network configuration
features to push out static routing configurations between the branches and hubs. Omit all of the BGP
information in the Panorama plugin and use normal virtual router static routes to configure static routing.
References
• Planning Your SD-WAN Configuration
https://docs.paloaltonetworks.com/sd-wan/1-0/sd-wan-admin/sd-wan-overview/plan-sd-wan-
configuration.html
App-ID enables visibility into the applications on the network so you can learn how they work and
understand their behavioral characteristics and their relative risk. This knowledge about applications
allows you to create and enforce Security policy rules to enable, inspect, and traffic shape desired
applications and block unwanted applications. After you define policy rules to allow traffic, App-ID begins
to classify traffic without any additional configuration.
App-ID is a patented traffic classification system available only in Palo Alto Networks firewalls. It
determines what an application is, irrespective of port, protocol, encryption (SSH or SSL), or any other
evasive tactic used by the application. It applies multiple classification mechanisms—application
signatures, application protocol decoding, and heuristics—to your network traffic stream to accurately
identify applications.
The App-ID engine is driven by pattern recognition features in the hardware and software of PAN-OS
firewalls. It is based on scanning payloads and application headers only. Port numbers are used only as a
secondary application recognition tool.
The signature database used by the App-ID scanning engine is updated periodically by Palo Alto Networks
through the Applications and Threats updates.
The App-ID engine is fundamental to PAN-OS software and cannot be turned off. Even when App-ID is not
being used as a part of Security policy rules, the Traffic logs show traffic classified by App-ID.
The App-ID engine also can look inside of protocols for “tunneling” applications. For example, the firewall
recognizes the HTTP protocol as the App-ID “web-browsing.” But HTTP traffic that belongs to a specific
application (e.g., Facebook) will be identified as such by App-ID.
After the application is identified, the policy check determines how to treat the application, for
example—block, or allow and scan for threats, inspect for unauthorized file transfer and data patterns, or
shape using QoS.
Over the course of a session each packet is evaluated for its App-ID. The state of App-ID recognition
changes as a session progresses, and these states can be found in Traffic logs:
• incomplete: Either the three-way TCP handshake did not complete or the three-way TCP
handshake did complete but there was no data after the handshake to identify the application.
Traffic being seen is not really an application.
For example, if a client sends a server a TCP SYN packet and the Palo Alto Networks device creates
a session for that SYN packet, but the server never sends a SYN ACK packet back to the client, then
that session is “incomplete.”
• insufficient data: Not enough data to identify the application. So, for example, if the three-way
TCP handshake completed and there was one data packet after the handshake but there was not
enough data to match any signature, then the user will see “insufficient data” in the Application
field of the Traffic log.
• unknown-tcp: The firewall captured the three-way TCP handshake, but the application was not
identified, perhaps because of the use of a custom application for which the firewall does not have
signatures.
• unknown-udp: Unknown UDP traffic
• unknown-p2p: Matches generic peer-to-peer (P2P) heuristics
• not-applicable: The Palo Alto Networks device has received data that will be discarded because
the port or service that the traffic is coming in on is not allowed, or no rule or policy allows that
port or service.
For example, if only one rule was on the Palo Alto Networks device and that rule allowed the
application of web-browsing only on port/service 80, and traffic (web-browsing or any other
application) is sent to the Palo Alto Networks device on any other port/service besides 80, then
the traffic will be discarded or dropped and sessions with “not-applicable“ will be in the
Application field.
SaaS Applications
The App-ID engine identifies SaaS applications and provides additional functionality. A dedicated SaaS
Application Usage report under Monitor > PDF Reports > SaaS Application Usage will help your
©2016-2020, Palo Alto Networks, Inc. 105
organization identify applications storing your data in external locations. The App-IDs for SaaS
applications contain additional data about these applications and their providers to help you make
decisions allowing access to them at the organizational level.
Palo Alto Networks firewalls include a feature within the URL Filtering engine that provides HTTP Header
Insertion for certain SaaS applications that can prevent users from accessing private instances of a SaaS
application while having access to the organization’s sanctioned environment. A discussion of this feature
can be found here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/objects/objects-security-
profiles-url-filtering/http-header-insertion
Security Profiles are not used in the match criteria of a traffic flow. The Security Profile is applied to scan
traffic after the application or category is allowed by the Security policy.
The firewall provides default Security Profiles that you can use out-of-the-box to begin protecting your
network from threats. The Security Profiles attached to Security policy “allow” rules determine the type
of threat detection performed on the traffic.
You can add Security Profiles that are commonly applied together to create a Security Profile Group; this
set of profiles can be treated as a unit and added to Security policy rules in one step (or included in
Security policy rules by default, if you choose to set up a default Security Profile Group).
Antivirus Profiles
Antivirus Profiles protect against viruses, worms, trojans, and spyware downloads. The Palo Alto
Networks antivirus solution uses a stream-based malware prevention engine, which inspects traffic the
moment the first packet is received, to provide protection for clients without significantly impacting the
performance of the firewall. This profile scans for a wide variety of malware in executables, PDF files,
HTML, and JavaScript viruses, and includes support for scanning inside compressed files and data
encoding schemes. If you have enabled Decryption on the firewall, the profile also enables scanning of
decrypted content.
Customized profiles can be used to minimize antivirus inspection for traffic between trusted security
zones, and to maximize the inspection of traffic received from untrusted zones, such as the internet,
along with the traffic sent to highly sensitive destinations, such as server farms.
The Palo Alto Networks WildFire® system also provides signatures for persistent threats that are more
evasive and have not yet been discovered by other antivirus solutions. As threats are discovered by
WildFire, signatures are quickly created and then integrated into the standard Antivirus signatures that
can be downloaded daily by Threat Prevention subscribers (sub-hourly for WildFire subscribers).
Anti-Spyware Profiles
Anti-Spyware Profiles block spyware on compromised hosts from trying to phone-home or beacon out to
external command-and-control (C2) servers, thus allowing you to detect malicious traffic leaving the
network from infected clients. You can apply various levels of protection between zones. For example,
you may want to have custom Anti-Spyware Profiles that minimize inspection between trusted zones
while maximizing inspection on traffic received from an untrusted zone such as an internet-facing zone.
You can define your own custom Anti-Spyware Profiles or choose one of the following predefined profiles
when applying anti-spyware to a Security policy rule:
• Default: Uses the “default” action for every signature, as specified by Palo Alto Networks when
the signature is created
• Strict: Overrides the “default” action of critical, high, and medium-severity threats to the block
action, regardless of the action defined in the signature file. This profile still uses the default
action for low and informational severity signatures.
After the firewall detects a threat event, you can configure the following actions in an Anti-Spyware
Profile:
• default: For each threat signature and Anti-Spyware signature that is defined by Palo Alto
Networks, a “default” action is specified internally. The default action typically is an “alert” "or a
You also can enable the DNS Sinkholing action in Anti-Spyware Profiles to enable the firewall to forge a
response to a DNS query for a known malicious domain, thus causing the malicious domain name to
resolve to an IP address that you define. This feature helps to identify infected hosts on the protected
network using DNS traffic. Infected hosts then can be easily identified in the Traffic logs and Threat logs
because any host that attempts to connect to the sinkhole IP address most likely is infected with
malware.
The procedure to configure Anti-Spyware Profiles and Vulnerability Protection Profiles is similar within
the management web interface.
After the firewall detects a threat event, you can configure the following actions in an Anti-Spyware Profile:
• default: For each threat signature and Anti-Spyware signature that is defined by Palo Alto
Networks, a “default” action is specified internally. The “default” action typically is an “alert” or a
“reset-both.” The “default” action is displayed in parenthesis, for example, “default” (alert) in the
threat or Antivirus signature.
• allow: Permits the application traffic
• alert: Generates an alert for each application traffic flow. The alert is saved in the Threat log.
• drop: Drops the application traffic
You can create custom data pattern objects and attach them to a Data Filtering Profile to define the type
of information about which you want to filter. Create data pattern objects based on:
• Predefined patterns: Filter for credit card numbers and Social Security numbers (with or without
dashes) using predefined patterns
• Regular expressions: Filter for a string of characters
• File properties: Filter for file properties and values based on file type
Note: If you’re using a third-party, endpoint data loss prevention (DLP) solution to populate file
properties to indicate sensitive content, this option enables the firewall to enforce your DLP
policy.
You can define your own custom File Blocking Profiles or choose one of the following predefined profiles
when applying file blocking to a Security policy rule. The predefined profiles, which are available with
content release version 653 and later, allow you to quickly enable best practice file blocking settings:
• Basic file blocking: Attach this profile to the Security policy rules that allow traffic to and from less
sensitive applications to block files that commonly are included in malware attack campaigns or
that have no real use case for upload or download. This profile blocks upload and download of PE
files (.scr, .cpl, .dll, .ocx, .pif, .exe), Java files (.class, .jar), Help files (.chm, .hlp), and other
potentially malicious file types, including .vbe, .hta, .wsf, .torrent, .7z, .rar, and .bat. It also
prompts users to acknowledge when they attempt to download encrypted-rar or encrypted-zip
files. This rule alerts on all other file types to give you complete visibility into all file types
entering and leaving your network.
• Strict file blocking: Use this stricter profile on the Security policy rules that allow access to your
most sensitive applications. This profile blocks the same file types as the basic file blocking
profile, and blocks flash, .tar, multi-level encoding, .cab, .msi, encrypted-rar, and encrypted-zip
files.
You also can use the WildFire Analysis Profiles to set up a WildFire hybrid cloud deployment. If you are
using a WildFire appliance to analyze sensitive files locally (such as PDFs), you can specify for less sensitive
file types (such as PE files) or file types that are not supported for WildFire appliance analysis (such as
APKs) to be analyzed by the WildFire public cloud. Use of both the WildFire appliance and the WildFire
cloud for analysis allows you to benefit from a prompt verdict for files that already have been processed
by the cloud and for files that are not supported for appliance analysis, and frees the appliance capacity
to process sensitive content.
You can enable both types of protection mechanisms in a single DoS Protection Profile.
The DoS Profile is used to specify the type of action to take and the details on matching criteria for the
DoS policy. The DoS Profile defines threshold settings for SYN, UDP, and ICMP floods; can enable resource
protection; and defines the maximum number of concurrent connections. After you configure the DoS
Protection Profile, you attach it to a DoS policy rule.
When you configure DoS protection, you should analyze your environment to set the correct thresholds
based on your actual traffic rather than use the default values provided.
Sample Questions
70. Which profile do you use for DLP based on file content?
A. Antivirus
B. Anti-Spyware
C. Vulnerability Protection
D. URL Filtering
E. File Blocking
F. WildFire Analysis
G. Data Filtering
71. Which profile do you use to monitor DNS resolution lookups for sites associated with threat
activity?
A. Antivirus
B. Anti-Spyware
C. Vulnerability Protection
D. URL Filtering
E. File Blocking
F. WildFire Analysis
G. Data Filtering
With URL filtering enabled, all web traffic is compared against the URL filtering database, which contains
a list of millions of categorized websites. You can use these URL categories as a match criterion to enforce
Security policy and to safely enable web access and control the traffic that traverses your network. You
also can use URL filtering to enforce safe search settings for your users and to prevent credential phishing
based on URL category.
Credential phishing prevention works by scanning username and password submissions to websites and
comparing those submissions against valid corporate credentials. You can choose which websites you
want to either allow or block corporate credential submissions based on the URL category of the website.
When the firewall detects a user credential being transmitted to a site in a category you have restricted, it
either displays a block response page that prevents the user from submitting credentials or presents a
continue page that warns users against submitting credentials to sites classified in certain URL categories.
But the firewall still allows the user to continue with the credential submission. You can customize these
block pages to educate users against reusing corporate credentials, even on legitimate, non-phishing
sites.
Credential Detection
Before you configure credential phishing protection, decide which method you want the firewall to use to
identify credentials. Each method requires the configuration of User‐ID technology. The IP address-to-
username mapping and group mapping methods check for valid username submissions only. In these
cases, the firewall blocks or allows the submission, based on your settings, regardless of the
accompanying password submitted. The domain credential filter method checks for valid usernames and
passwords submitted to a webpage:
• IP address-to-username mapping: The firewall uses IP‐address‐to‐user mappings that the PAN-OS
integrated User‐ID collects to check if a username submitted to a webpage matches the
username of the logged‐in user.
• Group mapping: The PAN-OS integrated User‐ID agent collects group mapping information from a
directory server and retrieves a list of groups and the corresponding group members. It compares
usernames submitted to a webpage against the group member usernames.
• Domain credential filter: The Windows-based User‐ID agent is installed on a Read-Only Domain
Controller (RODC). The User‐ID agent collects password hashes that correspond to users for
which you want to enable credential detection and sends these mappings to the firewall. The
firewall then checks if the source IP address of a session matches a username and if the password
submitted to the webpage belongs to that username. With this mode, the firewall blocks or alerts
on the submission only when the password submitted matches a user password.
Sample Questions
75. Which credential phishing prevention action allows users to choose to submit credentials to a
site anyway?
A. alert
B. allow
C. block
D. continue
76. Which user credential detection method would work if multiple users share the same client IP
address (for example, because of dynamic address translation done by a device on the internal
side of the firewall)?
A. IP-to-user mapping
B. group mapping
C. domain credential filter
D. IP-and-port-to-user mapping
77. Which type of user credential detection must be used by a firewall administrator that wants to
enable credential phishing prevention that blocks an attempt by a user to enter the
organization’s user ID and password?
A. IP-to-user mapping
B. domain credential filter
C. group mapping
D. Citrix mapping
Step 3: Review the Apps Seen on Port-Based Rules, Starting with the Highest Priority Rules
On No Apps Specified, click Compare or the number in Apps Seen to open Applications & Usage, which
lists applications that matched a port-based rule over a specified time frame, with each application’s Risk,
the date it was First Seen, the date it was Last Seen, and the amount of traffic over the last 30 days.
You can check Applications seen on port-based rules over the past 7, 15, or 30 days, or over the rule’s
lifetime (Anytime). For migrating rules, Anytime provides the most complete assessment of applications
that matched the rule.
You can search and filter the Apps Seen but remember that an hour or more is required to update Apps
Seen. You also can order the Apps Seen by clicking the column headers. For example, you can click Traffic
(30 days) to bring the applications with the most recent traffic to the top of the list or click Subcategory
to organize the applications by subcategory.
Cloning is the safest way to migrate rules, especially when Applications & Usage shows more than a few
well-known applications matching the rule. Cloning preserves the original port-based rule and places it
below the cloned application-based rule, which eliminates the risk of losing application availability
because traffic that doesn’t match the cloned rule flows through to the port-based rule. When traffic
from legitimate applications hasn’t hit the port-based rule for a reasonable period of time, you can
remove it to complete that rule’s migration.
In the Clone window, the green row is the selected application to clone. The container
application (slack) is in the gray row. The applications listed in italics are applications in the same
container as the selected application but that have not been seen on the rule. Individual
applications that have been seen on the rule are in normal font. All the applications are included
in the cloned rule by default to help prevent the rule from breaking.
After you clone a rule and Commit the configuration, the applications you select for the cloned rule are
removed from the original port-based rule’s Apps Seen list. For example, if a port-based rule has 16 Apps
Seen and you select two individual applications and one dependent application for the cloned rule, after
cloning, the port-based rule shows 13 Apps Seen because the three selected applications have been
removed from the port-based rule (16 − 3 = 13). The cloned rule shows the three added applications in
Apps on Rule.
Creation of a cloned rule with a container app works a bit differently. For example, a port-based rule has
16 Apps Seen and you select one individual application and a container app for the cloned rule. The
container app has five individual applications and has one dependent application. After cloning, the
cloned rule shows seven Apps on Rule—the individual application, the five individual applications in the
container app, and the dependent application for the container app. However, in the original port-based
rule, Apps Seen shows 13 applications because only the individual application, the container app, and the
container app’s dependent application are removed from the port-based rule.
Unlike with cloning, addition of applications to a port-based rule replaces the rule with the resulting
application-based rule. Addition of applications to a rule is simpler than cloning, but riskier because you
may inadvertently miss applications that should be on the rule, and the original port-based rule isn’t in
the rulebase to identify accidental omissions. However, addition of applications to port-based rules that
apply to only a few well-known applications migrates the rule quickly to an application-based rule. For
example, for a port-based rule that controls only traffic to TCP port 22, the only legitimate application is
SSH, so it’s safe to add applications to the rule.
There are three ways to add applications to replace a port-based rule with an application-based rule: Add
to Rule, Match Usage in Apps Seen, and Add in Apps on Rule:
• Add to Rule applications from Apps Seen (applications that matched the rule). Remember that
an hour or more is required to update Apps Seen.
1. Select applications from Apps Seen on the rule.
2. Click Add to Rule. In the Add to Rule dialog, add other applications in the same container app
and application dependencies, if required. For example, to add slack-base to a rule:
Sample Questions
78. Which security risk is elevated when port-based Security policy rules are used?
A. The firewall’s resources will be negatively impacted by processing unwanted traffic.
B. Unwanted applications can get through the firewall, bringing their vulnerabilities with
them.
C. The network is more vulnerable to TCP DoS attacks.
D. The firewall is more vulnerable to UDP DoS attacks.
Palo Alto Networks App-ID technology provides for positive identification of applications regardless of
port usage. App-ID allows you to safely enable access to only those applications that you want users to
reach. This practice reduces your attack surface by eliminating unauthorized applications and their
potential vulnerabilities.
As with any technology, usually there is a gradual approach to a complete implementation that consists
of carefully planned deployment phases to make the transition as smooth as possible, with minimal
impact to your end users. The general workflow for implementing a best practice internet gateway
Security policy is as follows:
• Assess your business and identify what you need to protect: The first step in deploying a security
architecture is to assess your business and identify your most valuable assets and the greatest
threats to those assets. For example, if you are a technology company, your intellectual property
is your most valuable asset. In this case, one of your biggest threats would be source code theft.
• Segment your network using interfaces and zones: Traffic cannot flow between zones unless
there is a Security policy rule to allow it. One of the easiest defenses against lateral movement of
an attacker that has made its way into your network is to define granular zones and allow access
only to the specific user groups that need to access an application or resource in each zone. By
segmenting your network into granular zones, you can prevent an attacker from establishing a
communication channel within your network (either via malware or by exploiting legitimate
applications), thereby reducing the likelihood of a successful attack on your network.
• Identify whitelist applications: Before you can create an internet gateway best practice Security
policy, you must have an inventory of the applications you want to allow on your network and
you must distinguish between those applications you administer and officially sanction and those
that you want users to be able to use safely. After you identify the applications (including general
types of applications) you want to allow, you can map them to specific best practice rules.
See section 2.4 Implement and maintain the App-ID lifecycle for a complete description of features and
their usage for converting port-based rules to use App-ID.
A web-based App-ID listing of all the existing App-IDs can be found here:
https://applipedia.paloaltonetworks.com/
Sample Questions
81. Which firewall tool provides settings and tools to convert policies from port-based to App-ID?
A. Network Monitor display under App Scope
B. Policy Optimizer under Policies
C. Application Hit Count under Policies
D. View Applications as Groups under Policies
82. An administrator creates a Security policy rule that allows office-on-demand traffic through
the firewall. After the change is committed, the firewall issues the following warning:
“vsys1: Rule 'Allow Office apps' application dependency warning:
Application 'office-on-demand' requires 'ms-office365-base' be allowed
Application 'office-on-demand' requires 'sharepoint-online' be allowed
Application 'office-on-demand' requires 'ssl' be allowed
Application 'office-on-demand' requires 'web-browsing' be allowed”
Which action should the administrator take?
A. create an application chain that include the dependencies
B. add the listed applications to the same Security policy rule
C. set the Service action of the rule to “dependent application default”
D. create a new Security policy rule for each listed application with an “allow” action higher
in the rule list
Note: In an HA pair, when both the Panorama VMs are operating in Panorama mode, the same log (from
the firewalls) is sent to the active and passive Panorama appliances. Therefore, the log basically is
replicated between the active and the passive appliances of the HA pair. This deployment option is
recommended if the firewalls generate up to 10,000 logs per second.
Log Collectors must be made a member of a Log Collector Group to be configured and receive forwarded
log events. (Note that “Logging Service” shown in the following figure is now called “Cortex Data Lake.”)
Log Collectors in a Log Collector Group appear as a single logical entity to devices forwarding logs. The
Log Collector Group makes local log storage location decisions when multiple platforms are present, thus
eliminating the need for an administrator to configure specific log storage behavior other than the
optional use of log redundancy within the Collector Group.
Cortex Data Lake is the central repository of all the logs generated from firewalls and the Traps endpoint
server. It initiates queries, generates reports, and analyzes logs stored in the cloud via Panorama. It also
You can activate licenses first on the Palo Alto Networks Support website and then communicate them to
the firewall (assuming internet connectivity from the Management port). If connectivity is not available,
you can enter licenses directly.
Dynamic Updates
Activated subscription licenses provide access to PAN-OS software updates and subscription data files
(dynamic updates). The following information explains these licenses and the process for updating files
and PAN-OS software:
Firewall Configuration
After these initial deployment steps are taken, configuration becomes a task of implementing network
connectivity and security settings to meet your specific requirements. These next steps can vary widely.
A complete discussion with implementation guidance is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/getting-started/register-the-firewall.html
Sample Questions
86. Which configuration is performed first on a firewall with factory default settings, according to
Palo Alto Networks best practices?
A. add licenses
B. update PAN-OS software
C. configure the management network port
D. update dynamic update files
87. You finished configuring the firewall’s basic connectivity in the lab and are ready to put it in
the data center. What do you have to remember to do before you power down the firewall?
A. Save the changes.
B. Commit the changes.
C. Create a restore thumb drive in case the configuration is deleted.
D. Verify that the configuration is correct. You do not need to do anything else if it is
correct; the configuration is updated automatically.
88. The firewall’s MGT port can be configured as which type of interface?
A. Layer 2
B. Layer 3
C. virtual wire
D. serial
The preceding figure identifies the firewall being viewed as the passive partner of an active/passive HA
configuration.
After the user authenticates for all factors, the firewall evaluates Security policy to determine whether to
allow access to the service or application.
To reduce the frequency of authentication challenges that interrupt the user workflow, you can specify a
timeout period during which a user authenticates only for initial access to services and applications, not
for subsequent access. Authentication policy integrates with Captive Portal to record the timestamps
used to evaluate the timeout and to enable user-based policies and reports.
Based on user information that the firewall collects during authentication, User-ID creates a new IP
address-to-username mapping or updates the existing mapping for that user (if the mapping information
has changed). The firewall generates User-ID logs to record the additions and updates. The firewall also
generates an Authentication log for each request that matches an Authentication rule. If you favor
centralized monitoring, you can configure reports based on User-ID or Authentication logs and forward
the logs to Panorama or external services as you would for any other log types.
• End the session for the service or URL you just accessed.
• Start a new session for the same service or application. Be sure to perform this step within
the Timeout period you configured in the Authentication rule.
The firewall allows access without re-authenticating.
• Wait until the Timeout period expires and request the same service or application.
The firewall prompts you to re-authenticate.
8. (Optional) Redistribute user mappings and authentication timestamps to other firewalls that
enforce Authentication policy to ensure they all apply the timeouts consistently for all users.
Sample Questions
95. How are updates made to the cache of root certificates that is used for certificate verification
purposes and maintained by Palo Alto Networks?
A. The administrator reviews certificate status and replaces them manually.
B. The firewall automatically updates the certificates as it updates the associated CRL list.
C. The administrator installs PAN-OS software and dynamic content updates.
D. The firewall automatically installs new certificates using OCSP.
96. How does a firewall administrator that creates a certificate on the firewall mark it for use in an
SSL Forward Proxy configuration?
A. add a certificate tag in the Decryption policy rule
B. configure a trust certificate in the Decryption Profile
C. set the Forward Trust Certificate property of the certificate itself
D. map the certificate to the URL in the SSL/TLS Service Profile
97. Administrators within the enterprise want to replace the default certificate used by the
firewall to secure the management web interface traffic with a certificate generated by their
existing certificate authority. Which certificate property must be set for their new certificate to
function?
A. Certificate CN set to a domain name that resolves to any traffic port address of the
firewall.
B. Certificate must be signed by the firewall root certificate.
C. Certificate must have the Forward Trust Certificate property set.
D. CN must be set to the management port of the firewall.
User-ID
Content-ID
Block IPv6 in IPv4 tunneling (via App-
ID)
Zone protection
Packet-based attack protection
—
Reconnaissance protection
URL filtering
SSL decryption
SSH decryption
DoS rulebase
IPv6 access to PAN-DB
DNS Sinkhole
External Dynamic List (EDL)
DNS
RADIUS
LDAP
SYSLOG
SNMP
NTP
Device DNS (device only)
DNS proxy
Reporting and visibility into IPv6
Networking
IPv6 static routes
PBF
PBF next hop monitor (v6 endpoint)
OSPFv3
MP-BGP —
GRE tunneling support
— — —
ECMP
Dual stack support for L3 interfaces
QoS policy
QoS marking
DSCP (session based)
VPN
GlobalProtect —
IKE/IPsec
IKEv2
IPv6 over IPv4 IPsec tunnel
DHCPv6 relay
SLAAC (router advertisements)
SLAAC (RDNSS) —
Device
High Availability (HA) - active/active
User-ID
Map IPv6 address to users
Sample Questions
98. Which two configuration conditions must be met for a firewall to NAT between IPv4 and IPv6?
(Choose two.)
A. select NAT64 in the Session tab under Device > Setup > Session
B. choose the NAT Type of nat64 in the General tab of a NAT policy rule
C. add an IPv6 addresses to the Translated Packet tab
D. add an IPv6 prefix in the nat64 configuration in the NAT policy rule
99. Which two configuration conditions must be met for a Palo Alto Networks firewall to send and
receive IPv6 traffic? (Choose two.)
A. Enable IPv6 check box in the virtual router configuration is checked.
B. An Ethernet interface is configured for virtual wire.
C. An Ethernet interface is configured for Layer 3.
D. Enable IPv6 Firewalling check box under Session Settings is turned on.
Different platform levels also can support varying numbers of virtual routers. The virtual router
configuration is meant to match the existing routing infrastructure. In addition to protocol configuration,
Redistribution Profiles can support protocol interoperability.
Troubleshooting Routing
The CLI has advanced troubleshooting of routing functions. Output from the debug routing …
command provides insight into router processing, including advanced debugging logs and routing-
specific packet captures.
Sample Questions
100. Under which condition can Layer 3 interfaces in the same firewall have the same IP
address?
A. They must be connected to different virtual routers.
B. They must be connected to the same Ethernet network through a switch.
C. They must be subinterfaces of the same physical interface.
D. They must be in different zones.
Before you can enable a firewall interface to transmit DHCP messages between clients and servers, you
must configure the firewall as a DHCP relay agent. The interface can forward messages to a maximum of
eight external IPv4 DHCP servers and eight external IPv6 DHCP servers. A client DHCPDISCOVER message
is sent to all configured servers, and the DHCPOFFER message of the first server that responds is relayed
back to the requesting client.
Before you can configure a DHCP relay agent, make sure that you have configured a Layer 3 Ethernet or
Layer 3 VLAN interface, and that the interface is assigned to a virtual router and a zone.
1. Select DHCP Relay.
Select Network > DHCP > DHCP Relay.
2. Specify the IP address of each DHCP server with which the DHCP relay agent will communicate.
• In the Interface field, select the interface you want to be the DHCP relay agent.
• Select either IPv4 or IPv6, which indicates the type of DHCP server address you will
specify.
• If you checked IPv4, in the DHCP Server IP Address field, Add the address of the DHCP
server to and from which you will relay DHCP messages.
• If you checked IPv6, in the DHCP Server IPv6 Address field, Add the address of the DHCP
server to and from which you will relay DHCP messages. If you specify a multicast
address, also specify an outgoing Interface.
• (Optional) Repeat the steps in the prior three sub-bullets to enter a maximum of eight
DHCP server addresses per IP address family.
3. Commit the configuration.
Click OK and Commit.
Sample Questions
105. In a site-to-site VPN configuration, what is an alternate method to the use of pre-shared
keys to authenticate each device during connection setup?
A. certificates
B. expected IP address of the partner’s interface
C. known hexadecimal string configured in both endpoints
D. matching proxy ID definitions configured in both endpoints
Every Palo Alto Networks firewall can provide GlobalProtect connectivity support to Windows and Mac
clients with no additional license requirement. Client software can be downloaded directly from the
Portal.
Gateway traffic (SSL or IPsec encryption) can be terminated on a tunnel interface in a separate zone,
which allows for specific policies to be enabled for that zone and user(s).
The firewall can extract information from these reports and use them as part of the Security policy. In this
way the firewall provides appropriate access, depending on endpoint configuration.
HIP fields are used to define HIP objects. For example, a HIP object might apply to all devices using
Android 5.0, or all Samsung devices using Android 6.0.
References
A discussion of GlobalProtect with links to configuration specifics can be found here:
https://docs.paloaltonetworks.com/globalprotect/9-1/globalprotect-admin/globalprotect-overview
HIP checking implementation and use is explored in detail here:
https://docs.paloaltonetworks.com/globalprotect/9-1/globalprotect-admin/host-information/about-
host-information
Reference
• Policies > NAT
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/policies/policies-nat
Sample Questions
111. Which two source address translation types can use a single IP address to NAT multiple IP
addresses? (Choose two.)
A. Static IP
B. Dynamic IP
C. Dynamic IP and Port
D. Translated Address
E. Address Override
112. Which NAT type can be used to translate between IPv4 and IPv6?
A. ipv4
B. nat64
C. nptv6
D. ipv6
113. How does a firewall process a packet that has more than one NAT policy rule that matches
the packet?
A. Each matching rule in the list is applied from the top down, with cumulative changes
being processed at the end of the list.
B. The first rule matching the packet is applied and processed, skipping the others.
C. The firewall issues an error when committing NAT policy rules that can affect the same
packet.
D. The last matching rule in the list is applied and processed.
Reference
• Policies > Security
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/policies/policies-
security.html
Sample Questions
114. A server on the DMZ with a private NIC address has network access provided by a NAT
policy rule whose Bi-directional check box is selected in the Translated Packet settings for
static IP source address translation. Which Security policy rule must be created to allow
bidirectional traffic to and from the DMZ server?
A. a rule for each direction of travel using the pre-NAT server IP address
B. a rule with the post-NAT source IP address
C. a rule for each direction of travel using the post-NAT server IP address
D. a rule with the pre-NAT source IP address
115. An internal web browser sends a packet to a server. The browser’s connection has the
source IP address 192.168.5.3, port 31415. The destination is 209.222.23.245, port 80. The
firewall translates the source to 75.22.21.54, port 27182. Which three of these source IP
addresses would cause a NAT policy rule to apply to this traffic? (Choose three.)
A. 192.168.5.0/24
B. 75.22.21.0/24
C. 192.168.4.0/23
D. 192.168.0.0/16
E. 75.22.0.0/17
F. 75.22.128.0/17
A Palo Alto Networks firewall also can act as a Decryption Broker for other external security services. This
feature will decrypt traffic and forward it out of the selected interface to a specific security device or
service (or chain of devices) that examines the cleartext traffic. The last service in the chain returns the
packet to the firewall, which then encrypts it and forward it to the original destination.
Information about the use and configuration of this capability can be found here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/decryption/decryption-broker/decryption-
broker-concepts
Special Decryption Implementations
Palo Alto Networks firewalls also can automatically send a copy of decrypted traffic to a specified
interface using the Decryption Mirroring feature. This option is available at no cost to midrange and high-
end firewalls that automatically forward copies of decrypted traffic to external DLP products. A
description of this feature can be found here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/decryption/decryption-
concepts/decryption-mirroring.html
Sample Questions
117. Which protocol is supported for traffic decryption matching a Decryption policy rule?
A. IPsec
B. SP3
C. SSH
D. NLSP
118. Where do you specify that a certificate is to be used for SSL Forward Proxy?
A. Certificate properties
B. Decryption Profile
C. Decryption policy
D. Security policy
119. Which feature must be configured to exclude sensitive traffic from decryption?
A. Security policy rule that includes the specific URL with an “allow” action
B. Decryption policy rule with the specific URL and “no decrypt” action
C. Application Override policy that matches the application URL and port number
D. Decryption Profile that includes the site’s URL
Note that the App-ID bypass characteristic of Application Override also skips essential Content-ID
processing, which could result in undetected threats. This feature should be used for trusted traffic only.
References
• Policies > Application Override
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/policies/policies-
application-override.html
• Objects > Applications
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/objects/objects-
applications/defining-applications
Sample Questions
120. Which option is not a parameter used to identify applications in an Application Override
policy?
A. protocol
B. port number
C. first characters in the payload
D. destination IP address
121. How does the firewall resolve conflicting App-ID assignments to the same traffic between
an Application Override policy rule and the firewall’s built-in App-ID?
A. The firewall’s regular App-ID is assigned.
B. The Application Override’s App-ID is assigned.
C. The App-ID is set to duplicate definitions.
D. The App-ID is set to not available.
122. Which firewall process is bypassed when an Application Override policy matches traffic
and assigns an App-ID?
A. QoS
B. IPsec
C. Content-ID
D. User-ID
Regardless of the deployed environment, every VM-Series firewall runs the same PAN-OS software. Some
environments have specific limits and requirements (i.e., supported interface types).
Details for implementation in each of these environments and a review of their specific requirements and
limitations are here:
https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment.html
Sample Questions
123. Which virtual interface is used for management on a VM-Series firewall running on ESXi?
A. vNIC #1
B. vNIC #2
C. vNIC #9
D. vNIC #10
124. Which three items of information are required at a minimum to install and configure VM-
Series firewalls? (Choose three.)
A. VLANs to be connected through the firewall
B. management port IP address
C. IP addresses for the data interfaces
D. management port default gateway
E. management port netmask
F. IP address for the external (internet-facing) interface
125. Compared to a physical firewall, VM-Series firewalls require you to apply which additional
license?
A. Base Capacity
B. Cloud Services
C. Site License
D. VM Update
126. A VM-Series firewall being deployed in Azure can be automatically configured by
bootstrapping. Azure requires which features for Bootstrapping to work?
A. Storage Account configured for Azure Files Service
B. PowerShell script that feeds a configuration file to the firewall
C. XML configuration file included in the base firewall provisioning
D. Azure Backup services configured with a config file and included in the firewall
provisioning
Log forwarding of any event type can send copies of log events to external destinations supporting the
following data formats:
• SNMP
• Email
• Syslog
• HTTP
Each log forwarding destination is configured in the firewall with a Server Profile of the appropriate type.
Navigate to Device > Server Profiles and create a profile for each specific destination.
After the destination’s Server Profile is created, it can be used in a Log Forwarding Profile.
Steps:
1. Configure a Server Profile for each external service that will receive logs from the firewall. The
profiles define how the firewall connects to the services.
For example, to configure an HTTP Server Profile, select Device > Server Profiles > HTTP and Add
the profile.
©2016-2020, Palo Alto Networks, Inc. 168
2. Select Objects > Log Forwarding and Add a Log Forwarding Profile to define the destinations for
Traffic, Threat, WildFire Submissions, URL Filtering, Data Filtering, Tunnel, and Authentication
logs.
In each Log Forwarding profile, Add one or more match list profiles to specify log query filters,
forwarding destinations, and automatic actions such as tagging.
In each match list profile, select Filter > Filter Builder and Add filters based on log attributes.
Add or remove a tag to the source or destination IP address in a log entry automatically and register the
IP address and tag mapping to a User-ID agent on the firewall or Panorama, or to a remote User-ID agent
so that you can respond to an event and dynamically enforce Security policy. The ability to tag an IP
address and dynamically enforce policy using Dynamic Address Groups gives you better visibility, context,
and control for consistently enforcing Security policy irrespective of where the IP address moves across
your network.
Sample Questions
127. Dynamic tags can be assigned to which kind of data in a log event?
A. source and destination address, source and destination zone name
B. source and destination address
C. interface, zone name
D. DNS name, zone name
128. How can the firewall use dynamically tagged objects to block traffic?
A. Add the object to an enforcement list of a Data Filtering object that then is attached to a
Security policy rule.
B. Assign the object to a dynamic list, which then is included in the destination address
matching condition of a Security policy rule.
C. Assign the object to a Dynamic Address Group object, which then is added to the
destination address matching condition of a Security policy rule.
D. Add the object to an Application Group and use it in Security policy rules.
129. A tag can be dynamically assigned to data in which four types of logs? (Choose four.)
A. Traffic
B. Threat
C. URL Filtering
D. HIP Match
E. Tunnel Inspection
F. Configuration
G. System
Previous PAN-OS versions starting with 8.1 included HTTP header insertion. New in PAN-OS version 9.1 is
a specific new header named X-Authenticated-User that enables you to communicate user and domain
information to a secondary, downstream security device of your choice. Using this new header to send
username and domain name information to a secondary security device assumes that the device is
programmed to read and interpret the information and to take action on it.
Note the following conditions about use of the new HTTP header insertion feature:
• You must enable User-ID on the firewall.
• Only HTTP version 1.x is supported. You cannot use the feature with HTTP version 2.
• Encrypted traffic must be decrypted before the firewall can insert a new header, which means
that you must configure your Decryption policy to decrypt any traffic to a service or application
for which you want to receive an inserted header.
The firewall inserts a header and value under specific conditions. First, the traffic must match a Security
policy rule with HTTP header insertion configured in an attached URL Filtering Security Profile. Header
insertion will not happen if either a Security policy rule or Security Profile blocks or denies the traffic.
When you configure HTTP header insertion in the URL Filtering Security Profile, you specify the domain
name of the destination service or application. The header is inserted only if the firewall determines that
the traffic is being sent to the domain name specified in the URL Filtering Security Profile. The firewall
determines the destination domain of the traffic by using the domain value found in the HTTP request’s
Host: header. For example, the Host: header could be Host: www.google.com, which means the
destination domain is google.com. If google.com is the domain configured in the URL Filtering Security
Profile, then the firewall would insert the configured HTTP header.
The following screenshot shows the result of browsing to Objects > Security Profiles > URL Filtering,
Automatic commit recovery enables you to configure the firewall to attempt a specified number of
connectivity tests and the interval at which each test occurs before the managed firewall automatically
reverts its configuration to the previous running configuration after you push a configuration from
Panorama or commit a configuration change locally on the firewall. The firewall also checks connectivity
to Panorama every hour to ensure consistent communication if unrelated network configuration changes
have disrupted connectivity between the firewall and Panorama or if implications to a pushed committed
configuration have affected connectivity. If an hourly connectivity check fails, the firewall generates a
system log to alert an administrator of a potential configuration or network connectivity issues.
Steps:
1. Log in to the Panorama web interface.
2. Select Device > Setup > Management.
3. In the Template context drop-down list, select the template or template stack that manages the
devices for which you want to configure the automated commit recovery parameters. Configure
the automated commit recovery settings:
a. Edit ( ) the Panorama Settings.
b. Verify that Enable automated commit recovery is selected.
c. Enter a value in the Number of attempts to check for Panorama connectivity field.
d. Enter a value in the Interval between retries field.
b. Click OK to save your configuration changes.
4. Select Commit and Commit and Push your configuration changes.
References
Enable Automatic Commit Recovery:
https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/panorama/9-1/panorama-
admin/panorama-admin.pdf
Then configure the custom tags to use as match conditions for DUG membership. In the web interface,
browse to Objects > Tags and create one or more custom tags that can be dynamically assigned to users.
After you have created custom tags, create the DUGs.
To create and configure a DUG, in the web interface browse to Objects > Dynamic User Groups. Then
click Add to create a new group. Provide a Name for the new group, optionally provide a Description, and
then in the Match field type one or more tags as match conditions. In the following example, the Name is
sneaky-users, there is no Description, and the only Match condition is the tag named anonymous. If you
click Add Match Criteria, then you can use the logical AND and OR operators to join multiple tags as
match conditions. The Tags field value is the tag that is statically assigned to the DUG object itself and
that is not assigned to a user and is not used as a match condition to identify users to add as members of
the DUG.
After you create the DUG, you must configure the firewall to use the DUG. Four options are available. To
dynamically register a tag with a username, you can use Panorama, the XML API, a remote User-ID agent,
or the web interface. A firewall can forward username and tag registration information to Panorama, and
Panorama can distribute this information to other firewalls. Other applications can invoke firewall XML
API commands to register username and tag associations. A remote User-ID agent can forward username
and tag registrations to Panorama or other firewall User-ID agents. You also can use the web interface to
register (or unregister) tags with usernames.
For example, the following screenshot illustrates use of the web interface to register or unregister tags
from a username. Browse to Objects > Dynamic User Groups and click more next to a group name. In the
window that opens click Register New Users to register a tag with a username. In the next window that
©2016-2020, Palo Alto Networks, Inc. 177
opens, select the Registration Source. You can choose the local User-ID agent, a remote User-ID agent, or
Panorama. In the following example, the Local User-ID agent was selected. Then select the Tags to
register with the user. The example uses the anonymous tag. If you want the tag to time out, which
means the tag will be disassociated with the user, then choose a Timeout value in minutes. Then click
Add and add one or more users to which to register the tag. To disassociate a tag from a username, start
by clicking the Unregister Users button.
As a second example, you also can use a Log Forwarding Profile attached to a Security policy rule to
autotag a username in response to a user’s network behavior. In the following example, a Log Forwarding
Profile named tag-users has been created. The profile is attached to a Security policy rule. If the rule
matches an HTTP session and the URL Filtering log logs an entry where the URL category equals
anonymous-proxy, then the Log Forwarding Profile invokes the built-in action that associates the tag
anonymous with the username. The username is tagged and becomes a member of a DUG. Assuming that
the DUG is used in the Security policy as a match condition, the firewall will modify what the user has
access to.
Simplified management of multiple SD-WAN-enabled firewalls is enabled by installing the SD-WAN plugin
on your Panorama management server. When Panorama is connected to the internet, you can download
and install the SD-WAN plugin directly from the Panorama web interface. To install the SD-WAN plugin on
Panorama when the internet is not connected, download the plugin from the Palo Alto Networks
Customer Support Portal and upload the plugin to Panorama. The plugin needs to be installed only on the
Panorama management server managing your SD-WAN firewalls, and not on the individual hub and
branch firewalls.
A tag name of your choice identifies a link; you apply the tag to the link (interface) by applying an
Interface Profile to the interface. A link can have only one tag. Tags allow you to control the order that
interfaces are used for traffic distribution. Tags allow Panorama to systematically configure many firewall
interfaces with SD-WAN functionality.
When you plan how to group your links, consider the use or purpose of the links and group them
accordingly. For example, if you are configuring links intended for low-cost or non-business-critical traffic,
create a link tag and group these interfaces together to ensure that the intended traffic flows primarily on
these links, and not on more expensive links that may impact business-critical applications or services.
An SD-WAN Interface Profile specifies the tag that you apply to the physical interface, and the type of Link
that interface is (ADSL/DSL, cable modem, Ethernet, fiber, LTE/3G/4G/5G, MPLS, microwave/radio,
satellite, WiFi, or other). You create an SD-WAN Interface Profile to define the characteristics of ISP
connections and to specify the speed of the links, how frequently the firewall monitors the link, and to
specify a link tag for the link. When you specify the same link tag on multiple links, you are grouping those
physical links into a link bundle. You must configure an SD-WAN Interface Profile and specify it for an
Ethernet interface enabled with SD-WAN before you can save the Ethernet interface.
A virtual SD-WAN interface is a VPN tunnel or DIA group of one or more interfaces that go to the same
destination, such as to a specific hub or to the internet. All links in a virtual SD-WAN interface must be the
same type, either all VPN tunnel links or all DIA links.
You create a Path Quality Profile for business-critical and latency-sensitive applications, application filters,
application groups, services, service objects, and service group objects that have unique network quality
or health requirements. A Path Quality Profile specifies maximum latency, jitter, and packet loss
thresholds. Exceeding a threshold indicates that the path has deteriorated and the firewall needs to
select a new path to the target. A sensitivity setting of high, medium, or low lets you indicate to the
firewall which path monitoring parameter is more important for the applications. You can specify
different thresholds for rules applied to packets that have different applications, services, sources,
destinations, zones, and users.
In an SD-WAN topology, the firewall detects a brownout, a blackout, and path deterioration
per application and selects a new path to ensure that you experience the best performance for your
critical business applications. A Traffic Distribution Profile specifies how the firewall determines a new
best path if the current preferred path exceeds a path quality threshold. You specify which tags the
distribution method uses to narrow its selection of a new path. A Traffic Distribution Profile specifies the
distribution method for the rule.
An SD-WAN policy rule specifies the application(s) and/or service(s) and a Traffic Distribution Profile to
determine how the firewall selects the preferred path for an incoming packet that doesn’t belong to an
existing session and that matches all other criteria, such as source and destination zones, source and
Local log storage on Palo Alto Networks firewalls is strictly allocated between different log files to ensure
that no log is overrun by another. This allocation is user-controlled. Navigate to Device > Setup >
Management > Logging and Reporting Settings for access to the following configuration settings:
Each log functions as a first-in, first-out log. When the physical storage space is filled, new entries will
overwrite old ones. Space is cleared in blocks and messages are added to the System log.
Before you can use Panorama or external systems to monitor the firewall, you must configure the firewall
to forward its logs. Before the firewall forwards to external services, it automatically converts the logs to
the necessary format: syslog messages, SNMP traps, HTTP, or email notifications. Before you start this
procedure, ensure that Panorama or the external server that will receive the log data is running and can
receive this traffic.
Any log event redirection causes a copy of the log event to be forwarded as specified. It is logged on the
firewall as usual.
The second method is the use of a Log Forwarding Profile to route Traffic, Threat, WildFire®, and other
log events to other systems such as Panorama, SIEM products, and syslog server:
All forwarded events are sent to their destination as they are generated on the firewall. A complete
discussion of log forwarding configuration is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/configure-log-forwarding
Palo Alto Networks also offers a cloud-based Cortex Data Lake (formerly Logging Service) that can be a
central repository for forwarded logs from multiple Palo Alto Networks devices. This central pool of log
data is fully accessible to the owner and acts as an optional base for further third-party security
applications through the Palo Alto Networks Cortex API.
Sample Questions
131. A firewall can forward log events to which two types of log formats? (Choose two.)
A. XES
B. SNMP
C. Http
D. databases using xml format
E. NCSA
132. How does a firewall forward log events to an external destination?
A. They are sent in batches at the frequency specified in the destination’s Server Profile.
B. They are queued and sent in batches at differing intervals, depending on the event
severity.
C. They are sent as quickly as the required QoS policy rule governing log event traffic allows.
D. They are sent in real time as the firewall generates them.
133. Which two firewall logs can be exported using the Scheduled Log Export function? (Choose
two.)
A. Configuration
B. System
C. Traffic
D. URL
A discussion of available log data and making it into information that can be acted on is here:
https://www.paloaltonetworks.com/apps/pan/public/downloadResource?pagePath=/content/pan/en_U
S/resources/whitepapers/actionable-threat-intelligence
Log information generally is in the Monitor tab of the web interface. The reporting sections align with the
general use of these reports. The Log section presents both detailed, real-time data and historical data
(subjected to available storage). It is subdivided into sections that segment log data into related
information. PAN-OS 9.1 includes a Unified log that collects copies of events from the Traffic, Threat, URL
Filtering, Data Filtering, WildFire Submissions,
Tunnel Inspection, Authentication, and IP-Tag logs into a single location for easy parsing of related data.
Each log provides similar features, which results in an organized presentation of desired data. Displayed
log data can be exported in CSV format at any time.
The following figure shows the CSV export option available on any detailed log display:
This export will include all detail for the displayed record even if it isn’t visible in the chosen column
displays.
You can see the entries in various logs using Monitor > Logs. You can configure the columns to display
and their order and width:
Filters can be built and even stored for future use. Specific data about this functionality is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/view-and-manage-logs
While this log data is stored in detail in log storage, a firewall summarizes new log entries and adds the
results to separate on-board reporting databases used as default sources by Application Command
Center (ACC), App Scope, PDF Reports, and Custom Reports.
By default, these reports typically run once per day and summarize all activity on the firewall. A report
browser of predefined reports appears on the right. In the following figure, chosen reports display their
results for the previous day’s traffic. The predefined report browser shows choices of categories and
specific reports on the right:
The PDF Reports section offers other important reporting tools. Custom reports can be created, stored,
and run on-demand and/or a schedule basis. More information is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/view-and-manage-
reports/generate-custom-reports
Other reports and displays on the firewall often support click-through of data items to enable you to
uncover more detail. This practice often results in a switch to the ACC with preset filters to focus only on
the previously displayed data. Detailed use data is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/use-the-application-
command-center.html
Sample Questions
134. Which filter finds all log entries for traffic that originates from the internal device whose IP
address is 172.17.1.3 and according to the header appears to be HTTP or HTTPS?
A. ( addr.src in 172.17.1.3 ) and ( ( port.dst eq 80 ) or ( port.dst eq 443 ) )
B. ( ( addr.src in 172.17.1.3 ) and ( port.dst eq 80 ) ) or ( port.dst eq 443 )
C. ( src.addr in 172.17.1.3 ) and ( ( dst.port eq 80 ) or ( dst.port eq 443 ) )
D. ( ( src.addr in 172.17.1.3 ) and ( dst.port eq 80 ) ) or ( dst. port eq 443 )
135. Which two log files would you use if you suspect that a rogue administrator is modifying
the firewall’s rulebase to allow and hide illicit traffic? (Choose two.)
A. Traffic
B. Threat
C. Data Filtering
D. Configuration
E. System
136. Which product is required to use event correlation?
A. next-generation firewall, PA-220
B. Advanced Endpoint Protection
C. Panorama
D. GlobalProtect
References
• Manage Custom or Unknown Applications
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/app-id/manage-custom-or-
unknown-applications
• Create a Custom Application
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/app-id/use-application-objects-in-
policy/create-a-custom-application
Sample Questions
137. How would you configure the firewall to control access to a custom DNS application that
operates differently from the standard DNS application?
A. You cannot do it with the next-generation firewall. You need to manually configure a
proxy.
B. Create specific rules for the sources and destinations that run this application.
C. Create a custom DNS application and add it to separate Security policy rules.
D. Create an Application Override policy and specify the sources and destinations that run
this application.
138. What are two results of using Application Override policies? (Choose two.)
A. prevent matching traffic from entering VPN tunnels
B. apply a specified App-ID label to matching traffic
C. prevent matching traffic from being logged
D. cause matching traffic to bypass Content-ID processing
E. route traffic to WildFire for scanning
139. Which two types of entities can have custom signatures? (Choose two.)
A. services
B. URL categories
C. user groups
D. applications
E. vulnerabilities
Subscription updates are enabled through application of various licenses to the firewall. These updates
are managed under Device > Dynamic Updates. Updates can be transferred directly from Palo Alto
Networks on demand or by schedule control. In cases where the firewall does not have internet
connectivity, these updates can be downloaded from the Palo Alto Networks Dynamic Update section of
the Support portal site onto an administrator’s system and uploaded through a management web
interface connection and then applied.
PAN-OS updates are managed in the Device > Software section of the web interface. New PAN-OS
versions can be downloaded and even installed without user disruption. A final system reboot must be
performed to put the new PAN-OS software into production. This reboot is disruptive and should be done
during a change control window.
A firewall does not need to upgrade to each released PAN-OS software in sequence. Considerations for
skipping releases are outlined here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-new-features/upgrade-to-pan-os-91/upgrade-
the-firewall-to-pan-os-91/determine-the-upgrade-path.html#id85bdf6f4-2e83-49f0-8525-3eb2163f2d2e
To ensure that software upgrades function as expected, you are required to install the latest dynamic
updates before upgrading PAN-OS software.
Updates to App-ID signature information sometimes can reclassify previously labeled traffic, which might
impact user access to critical applications. The firewall provides several mechanisms to review changes to
App-IDs prior to or immediately after their installation.
HA Firewalls
Dynamic updates are the responsibility of the individual firewalls to manage, even when they are in
passive mode. This task can be difficult if dynamic updates have no network path to the Palo Alto
©2016-2020, Palo Alto Networks, Inc. 196
Networks update servers. Dynamic updates in HA clusters include an option to “Sync-to-peer” for use
when the secondary firewall has no network route to the update server. Further discussion is here:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClrnCAC
Firewalls in HA clusters must upgrade PAN-OS software individually. In active/passive clusters a firewall
typically is put into suspend mode and then upgraded. After the upgrade is complete, the firewall is
made active and the partner enters suspend mode and is upgraded.
Sample Questions
140. Match the upgrade step description with the correct step number.
Upgrade PAN-OS software Step 3
Reboot the firewall Step 4
Update dynamic content Step 2
Activate subscription licenses Step 1
141. Match each component with the order in which the component should be upgraded to a
new version of PAN-OS software.
HA active firewall Step 4
Panorama Step 1
Log Collector Step 2
HA passive firewall Step 3
If you back up versions of the running or candidate configuration, you can later restore those versions on
the firewall. A discussion about the basic process is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/firewall-administration/manage-
configuration-backups
Sample Questions
143. What is the format of the firewall configuration files?
A. YAML
B. JSON
C. XML
D. CSV
144. Which method can be used to restore the previous configuration when a new
configuration committed on a firewall has undesired consequences?
A. Use the Load configuration version to restore the previous configuration settings, and
follow with a commit.
B. Use the Rollback commit link in the commit completion message.
C. Use the Import device state to restore the pre-commit configuration.
D. Use the Load named configuration snapshot to restore the previous configuration, and
follow with a commit.
145. Which CLI command do you use to move a configuration file from an external server to a
firewall’s local storage?
A. rdist
B. ssh
C. scp
D. rcp
References
• HA Concepts (including the subtopics)
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/high-availability/ha-concepts
• What is HA-Lite on Palo Alto Networks PA-200?
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClUzCAK
• HA Links and Backup Links
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/high-availability/ha-concepts/ha-
links-and-backup-links
• Set Up Active/Passive HA
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/high-availability/set-up-
activepassive-ha.html
• Set Up Active/Active HA
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/high-availability/set-up-
activeactive-ha.html
• See additional information in section 1.3 Given a scenario, identify how to design an
implementation of firewalls in High Availability to meet business requirements that leverage the
Palo Alto Networks Security Operating Platform.
Sample Question
146. Which feature is an intended advantage of an active/passive firewall pair versus an
active/passive pair?
A. increased throughput
B. support of asynchronous routing
C. increased session count
D. shared dynamic updates
Panorama includes Managed Device Health Monitoring which displays limited HA status information in
the summary display in the Panorama management web interface.
References
• SNMP Support
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/snmp-monitoring-
and-traps/snmp-support
• Monitor Statistics Using SNMP
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/snmp-monitoring-
and-traps/monitor-statistics-using-snmp
• Supported MIBs
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/snmp-monitoring-
and-traps/supported-mibs
• Using Device Health Monitoring from Panorama
https://docs.paloaltonetworks.com/panorama/9-1/panorama-admin/manage-firewalls/device-
monitoring-on-panorama/monitor-device-health.html
Sample Questions
147. Which configuration object does a firewall use to forward HA-related events to an external
monitoring technology?
A. Device > Log Settings > System Log settings
B. Objects > Log Forwarding Profile > System Log Type
C. Device > High Availability > General > Event Forwarding
D. Dashboard > High Availability widget > Notification
148. Which two Panorama objects can display current HA state information about a managed
firewall? (Choose two.)
A. firewall listings in Monitor > HA Status
B. firewall specific information in Managed Devices > Health
C. firewall listings in Managed Devices > Summary
D. firewall HA Status widget in Dashboard > Widgets
E. firewall HA status in Panorama > High Availability
AutoFocus is a threat intelligence service that provides an interactive, graphical interface for analyzing
threats in your network. You can use AutoFocus to compare threats in your network to threat
information collected from other networks in your industry or across the globe, within specific time
frames. AutoFocus statistics are updated to include the most recent threat samples analyzed by Palo Alto
Networks. Access to this information allows you to stay current with threat trends and to take a
preventive approach to securing your network.
AutoFocus is a separately licensed product that is accessed in two primary ways: directly through the
AutoFocus Portal, or by viewing AutoFocus-provided data in a firewall’s web interface. The AutoFocus
Portal is the primary access method for the evaluation of overall trends and characteristics of historical
and current threats. This data can be used to characterize traffic seen on your network(s). Threats found
by the firewall can be enriched by AutoFocus-provided contextual data. Additional threat context can be
displayed for threats reported in your firewall logs.
References
• AutoFocus at a glance
https://www.paloaltonetworks.com/resources/datasheets/autofocus-at-a-glance
• AutoFocus Administrator’s Guide, especially the dashboard
https://docs.paloaltonetworks.com/autofocus/autofocus-admin
App-ID updates have a special impact because new application definitions might affect current Security
policy rules. PAN-OS software provides features to review the App-ID updates and modify the Security
policy rules.
If your firewalls are managed by Panorama, the Panorama device can be the source of dynamic updates
for managed firewalls and can configure the update schedule.
References
• Configure Content and Software Updates
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/software-and-content-
updates/app-and-threat-content-updates/configure-app-threat-updates
• Manage New App-IDs Introduced in Content Releases
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/app-id/manage-new-app-ids-
introduced-in-content-releases.html
• Managing dynamic updates from Panorama
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/panorama-web-
interface/panorama-device-deployment/manage-software-and-content-updates
Sample Questions
151. After an Applications and Threats dynamic update is downloaded to the firewall, where
can information about changes to the App-IDs be found?
A. Summary link in the log event detail reporting the dynamic update file download
B. Review Policies link at the bottom of the Security policy rules display
C. Review Apps link appearing next to the downloaded Applications and Threats file
D. Details link in the dynamic file availability announcement appearing in the News Feed
widget on the dashboard
152. The GlobalProtect Data File dynamic update contains which kinds of data?
A. GlobalProtect client package software updates for Windows and Macintosh
B. list of available connection points for Prisma Access
C. HIP check detection data for the GlobalProtect clients
D. updates to cypher suites used by the GlobalProtect client
Panorama notifies the devices (firewalls, Log Collectors, and WildFire appliances) that updates are
available. The devices then retrieve the update packages from Panorama. By default, devices retrieve
updates over the management (MGT) interface on Panorama. However, you can configure Panorama to
use multiple interfaces if you want to reduce the traffic load on the MGT interface by using another
interface for devices to retrieve updates.
HA firewalls are expected to have the same version content updates. Firewalls that are in an HA pair each
implement an update process. In cases of Panorama management of update files, Panorama should
schedule an update for both HA peers individually.
Firewalls in an HA configuration normally automatically sync their configurations with each other. When
one firewall performs a commit, the changes are communicated to the other firewall and a commit is
automatically triggered, thus keeping them in sync. When Panorama manages an HA firewall set, this
automatic update is disabled, with the sync responsibility now belonging to Panorama. An administrator
must include the HA pair in any changes made and committed on Panorama.
Reference
• Managing dynamic updates from Panorama
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/panorama-web-
interface/panorama-device-deployment/manage-software-and-content-updates
Sample Questions
154. How are HA firewall pairs kept in sync when Panorama pushes dynamic updates?
A. Panorama delivers the dynamic update to the active firewall(s) of the HA pair and
updates the passive partner when a failover occurs in active/passive pairs.
B. Panorama delivers the update to one firewall, which syncs with its HA partner.
C. Panorama delivers the dynamic update to both firewalls simultaneously.
D. Panorama delivers the dynamic update to the active firewall, which triggers the passive
partner to request the file from Panorama.
155. Which type of device can receive the Antivirus content update?
A. Log Collector
B. firewall
C. AutoFocus
D. MindMeld
©2016-2020, Palo Alto Networks, Inc. 206
156. Which requirement must a Panorama meet to update a managed firewall’s antivirus
signatures?
A. The PAN-OS versions on the firewall and Panorama must be the same.
B. Panorama and the firewall must be able to connect to the Palo Alto Networks update
server.
C. The update must be installed on Panorama before it is installed on any firewalls.
D. Panorama must download an antivirus file version compatible with the target firewall’s
PAN-OS version.
Note: The App Dependency tab does not appear in the Commit Status window if there are no
dependency warnings. Also note that the commit completed successfully even with an application
missing a dependent application.
Another method to determine applications and their dependencies while creating or updating a Security
policy rule is to use the Depends On panel on the Applications tab:
To determine applications that specifically are used, navigate to Objects > Applications. The Implicitly
Uses field will list the applications that are implicitly allowed as part of the application:
References
Resolve Application Dependencies:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/app-id/use-application-objects-in-
policy/resolve-application-dependencies.html
• Link Performance:
Error: One or more sites in the VPN cluster have connectivity issues such as when a tunnel or a
virtual interface (VIF) is down
Warning: Number of VPN clusters, hubs, and branches that have links with jitter, latency, or
packet loss performance measurements that exceed the moving seven-day average value of
the metric
OK: Number of VPN clusters, hubs, and branches that are experiencing no jitter, latency, or
packet loss performance issues
From the landing dashboard, you can narrow the view to impacted applications or links that have the
Error or Warning status. You then can select an affected site to view site-level details.
Select Panorama > SD-WAN > Monitoring on the landing dashboard to view health status summaries of
your VPN clusters, hubs, and branches:
For more detailed information, click an App Performance or Link Performance summary that indicates
Impacted, Error, or Warning counts to view a list of sites and their status based on latency, jitter, and
packet loss:
©2016-2020, Palo Alto Networks, Inc. 211
Click a site that displays Warning or Error to view the VPN cluster. The site data displays App
Performance and Link Performance, including the impacted applications. Also use the Sites filter to view
VPN clusters based on link notifications, latency deviations, jitter deviations, packet loss deviations, or
impacted applications.
On the App Performance or Link Performance window, click PDF/CSV to export the detailed health
information for the application or link in the VPN cluster in PDF or CSV format.
If you believe that the traffic to be evaluated has been received by the firewall, initial investigation should
begin with the Traffic log. The Traffic log can be found at Monitor > Logs > Traffic. The default behavior of
the firewall is to create a summary entry for each session when it ends. This behavior is controlled by the
Log Setting field included on the Actions tab of each Security policy rule. Because each Security policy
rule has its own logging configuration, different rules can be configured to log information in different
ways.
If the traffic in question includes at least one closed session, then an entry for the session should appear
in the Traffic log. You can display detailed information about that session by clicking the magnifying glass
icon in the left column:
The presence of a log entry confirms that properly formed traffic has reached the firewall and has been
evaluated by a Security policy rule. Traffic could be processed without reaching a session end, which
would result in no log entry yet. The Session Browser allows troubleshooting of open sessions that might
not have been logged yet.
The detailed session information should be used to evaluate the handling of the traffic. The Source and
Destination sections display header data and confirm potential NATs being applied. The General section
confirms the action taken by the Security policy rule and the rule’s name, App-ID, protocol, time seen.
and the reason the session ended. The Details section shows the packet summary for the reported
session, including counts and size.
Examination of this information often confirms the firewall’s handling of the traffic and might show
unexpected behavior to correct, as required.
When troubleshooting requires the examination of actual packet contents, a packet capture can be
performed on the firewall and subsequently downloaded as a pcap-formatted file ready for external
software consumption. Packet capture settings are found under Monitor > Packet Capture.
Warning: If you manually clear just the filters while another firewall administrator is actively running a
capture, the running capture will start to capture all packets, with no filters. Before you clear any existing
filters, confirm that the filters are not being used. If another administrator has saved filters that are
meant to be used later, you can disable those filters rather than delete them. Use of Clear All Settings will
clear all filters and turn off all captures.
You can, for example, configure your filters, turn them on, and then monitor them using CLI commands
for session volume before you complete the rest of the configuration. To monitor the number of marked
sessions, use the CLI command show counter global filter delta yes packet-filter yes.
Execute the command once and then a second time to see the difference (the delta) from the prior
execution of the command.
Tip: To analyze “inside” and “outside” sessions within a single file, you can configure the receive and
transmit stages to write to the same filename, which will result directly in a merged pcap file.
When you configure a capture stage, you can specify the maximum number of bytes and/or the
maximum number of packets, after which capturing stops.
The receive stage will not capture both flows of a session unless the filter configuration matches
to traffic in each direction.
• Firewall stage: On firewalls running PAN-OS 8.0 and earlier, packets captured at the firewall and
transmit stages will be captured when the corresponding session has been matched to a capture-
filter statement. Firewalls running PAN-OS 8.1 and later capture packets at the firewall and
©2016-2020, Palo Alto Networks, Inc. 216
transmit stages by the same effective logic (though not exactly the same) as the receive stage,
that is, only if the individual flow (c2s or s2c) matches the filter configuration.
Firewall-stage capture shows you what is inside the box. The firewall-stage capture point is post-
ingress, post-session-setup, and pre-NAT.
The flow logic of the firewall stage itself applies NAT as the last or nearly last step of Layer 2-to-
Layer 4 packet processing and before any Layer 7 packet-payload content analysis begins. The IP
addresses of packets captured by the firewall stage will match the pre-NAT addressing as defined
in the session table. Also, packets that the firewall drops because of Layer 2-to-Layer 4 processing
(such as packets dropped because of a session-closed status) will appear in the drop-stage pcap
with pre-NAT addressing.
Packets that the firewall drops because of a “deny” action triggered by a Security policy or Security
Profile will appear in the drop-stage pcap with post-NAT addressing.
A packet dropped in the receive stage will appear in both the drop-stage pcap and the receive-
stage pcap. You also typically will find packets that fail the initial session setup process in both the
receive-stage and drop-stage pcaps. Packets dropped by or subsequent to the firewall stage will be
found in both the drop-stage and firewall-stage pcaps.
Drop-stage pcaps comprise copies of individual packets that are dropped. Drop-stage pcaps do not
include prior or subsequent packets for contextual analysis. Drop-stage pcaps include only the
exact packets dropped. If you want to better understand why a packet has been dropped, query
the global counters, review log data, and run additional debug-level packet-diagnostic features
such as flow basic.
• Transmit stage: Capture of packets at the transmit stage shows you packets as they egress from
the firewall’s logical interface. In transmit-stage pcaps you can see block pages, resets, TCP MSS
adjustments, and any other packets or packet transformations created by the firewall itself,
including post-NAT addressing.
Pre-Parse-Match Option
After a packet enters the ingress port, the firewall performs several basic pre-processing tests to ensure
that the packet is viable before it is received for subsequent session setup and/or additional firewall
processing. The firewall discards packets that fail these basic tests before the packet reaches the point
To capture packets that normally would be discarded before the filter match, the system emulates an
initial, “pre-parse” positive match for every packet entering the system. This initial “match” allows all
packets to be filtered subsequently by the normal receive-stage filtering process. The pre-parse match
option is resource intensive. You should consider using it only for advanced or otherwise rare
troubleshooting purposes. Palo Alto Networks recommends that you use this option only under direct
advice and guidance from technical support.
Troubleshooting of route-lookup failures is the typical use case that may require use of the pre-parse
option. However, such errors typically are easy to identify using the firewall’s interface counters.
To enable the pre-parse match option in the CLI, use the command debug dataplane packet-diag
set filter pre-parse-match yes.
Turning On Capture
After you turn on packet capture, you can monitor the capture in other ways to see if you are actively
capturing any traffic:
• Refresh the Packet Capture page in the web interface and look first for the existence of new
capture files, and then for their file size. You can refresh the page repetitively to monitor any
growth in the file size.
• Use the CLI to show the current packet-diagnostics settings by running the debug dataplane
packet-diag show setting command. The bottom of the settings summary includes the
same data displayed in the Captured Files section of the Packet Capture page in the web
interface.
• Monitor currently marked sessions, in addition to verifying that the capture-stage files are
growing
The Palo Alto Networks firewall CLI offers access to more debugging information and often is used by
experienced administrators for troubleshooting. This section provides only a brief mention of basic CLI
tools. See the “References” section for more complete information sources.
After you log in to the CLI, the command prompt by default is in operational mode. The commands
available within the context of operational mode include basic networking commands such as ping and
traceroute, basic system commands such as show, and more advanced system commands such as
debug. Debug commands allow you to set parameters that, if improperly used, can cause system failure.
Commands to shut down and restart the system also are available from within operational mode.
Configuration mode enables you to display and modify the configuration parameters of the firewall,
verify candidate configuration, and commit the configuration. Access it by typing the command
configure while in operational mode.
CLI mode offers access to data not available in the web interface. Additional log files written by various
subsystems of the firewall are available. Large files such as log files can be displayed with four principle
commands: show, tail, less, and grep. A partial list of useful log files for troubleshooting can be
found in the “References” section.
The show command is the main method to display values and settings. In operational mode begin by
typing show, a space, and then press the Tab key to invoke the autocomplete function, which show all
available options for the show command. Examine this list and explore options to become familiar with
accessing settings and values for troubleshooting. The command show interface all displays a
summary of all configured interfaces, their link status, and assigned zones. The command show system
resources displays the overall resources utilization status of the firewall. For troubleshooting purposes,
the test command shows the results when simulated traffic is presented to various subsystems. For
example, the command test security-policy-match… shows the security processing of the
simulated traffic described at the end of the command. The command test routing… predicts the
virtual router’s handling of the simulated traffic. Many test commands are available that can be found
by entering test followed by a space and then the Tab key for the autocomplete listing of options.
Packet captures also can be performed at the command line level. The same packet capture engine
explored earlier through the web interface can be accessed from the CLI. Each configuration step used in
the web interface has a command line equivalent. See the “References” section for the location of a
detailed discussion.
References
• Log Types and Severity Levels
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/view-and-manage-
logs/log-types-and-severity-levels.html
• Monitor > Logs
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/monitor/monitor-
logs.html
Sample Questions
157. If users cannot access their Gmail accounts through the firewall, which log and filter do
you use to troubleshoot the problem?
A. Traffic, (app eq gmail)
B. Traffic, (app in gmail)
C. Configuration, (app eq gmail)
D. Configuration, (app in gmail)
158. You cannot access the firewall web interface. From the firewall CLI, how do you check to
see if the web service is running?
A. ps -aux | grep appweb
B. ps -aux | match appweb
C. show system software status | grep appweb
D. show system software status | match appweb
159. Which firewall log displays information about connection failures to an external LDAP
authentication server?
A. Traffic
B. System
C. User-ID
D. Authentication
Information about configuring threat detection packet captures and accessing the captured data is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/take-packet-captures/take-a-
threat-packet-capture.html
Data Filtering Security Profiles can take captures of configured patterns. Because this data might be
highly sensitive, special password protections are provided for these stored packet captures. Details are
here:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClvlCAC
The PAN-OS web interface provides access to traffic packet captures. Additional pcap and debug tools are
available through the CLI.
Complete information about the configuration and use of this feature is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/take-packet-captures/take-a-
custom-packet-capture.html
Note: Some Palo Alto Networks firewalls include a Hardware Offload feature that optimizes the handling
of traffic. Offloaded traffic will not appear in packet captures in either the web interface or the CLI. PA-
3050, PA-3060, PA-5000 Series, PA-5200 Series, and PA-7000 Series firewalls have this feature. To
guarantee that all packets are available for capture, a CLI command must be run to temporarily disable
Hardware Offload. See the following information for details and disclosures about CPU impact.
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/take-packet-captures/disable-
hardware-offload.html
Note: Management interface traffic cannot be captured by the previously mentioned CLI tools. The
tcpdump command is the only tool with visibility to this traffic.
Traffic Ports
Traffic ports provide multiple configuration options with the ability to pass traffic through to other ports
via traffic-handling objects (virtual routers, virtual wires, and VLANs).
Management Port
The management port is isolated from internal connectivity for security purposes. If the management
port requires internet access, its traffic must be routed out of the firewall and through other network
infrastructure that provides this connectivity. The traffic often is routed back to a traffic port on the
firewall requiring appropriate Security policy rules for access. This traffic is treated like any other transit
traffic, which means that you must configure Security policy rules to allow the traffic to pass.
This management traffic can be routed through alternate ports. A discussion is here:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGJCA0
Troubleshooting Tools
There are several important tools for troubleshooting traffic flow through the firewall. A best practice in
troubleshooting is to separate general connectivity issues from those of security. Connectivity issues
should be resolved before security processing is evaluated.
The temporary enabling of logging session initiation time can aid in troubleshooting.
You also can display open sessions using the Monitor > Session Browser display:
The Clear check box at the end of a session summary line can be used to end the session immediately,
which often generates the desired log entry.
The CLI show commands will assist with troubleshooting. The web interface traffic capture and CLI pcap
and debug functions give greater visibility to system-level operation for troubleshooting. A complete
discussion about packet captures is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/take-packet-captures.html
©2016-2020, Palo Alto Networks, Inc. 226
Connectivity issues often arise from unexpected traffic forwarding decisions. You can view forwarding
decisions after you display the Layer 3 routing and forwarding tables in the web interface:
Display the specific virtual router’s routing and forwarding tables with the More Runtime Stats link.
Note that policy-based forwarding (PBF) policy rules can override routing decisions and must be
considered when you troubleshoot connectivity. The routing and forwarding tables mentioned do not
show the effects of existing PBF policy rules. PBF troubleshooting is best done on the CLI; show
commands can display existing PBF policies and whether they are active. The test pbf-policy-match
command will show the application of existing PBF policies on modeled traffic.
Sample Questions
163. Where in the firewall web interface can you see whether sessions are going through a
specific interface?
A. Dashboard
B. Application Command Center (ACC)
C. Session Log node on the Monitor tab
D. Session Browser on the Monitor tab
164. Communication through a specific interface works most of the time but fails when traffic
throughput is at its highest. Which policy do you consult to identify the problem?
A. Security
B. DoS Protection
C. QoS
D. Application Override
165. Which interface type allows you to add a firewall with the least disruption to a network?
A. tap
B. Layer 3
C. Layer 2
D. virtual wire
References
• Decryption Overview
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/decryption/decryption-
overview.html
• How to Implement and Test SSL Decryption
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClEZCA0
Sample Questions
166. Why would SSL decryption that has been working for a customer suddenly stop?
A. The firewall’s CA certificate expired.
B. The firewall’s IP address, which is encoded in the certificate, changed.
C. The firewall has been upgraded to a different model.
D. The firewall’s decryption subscription expired.
167. A company uses a small SaaS application provider. This application is accessed through
HTTPS but suddenly stops working through the firewall. However, when the application is
accessed from home, users receive an error about the certificate. Which two situations would
explain this behavior? (Choose two.)
A. The SaaS's certificate had expired. The firewall's decryption policy is configured to block
connections with expired certificates.
B. The SaaS's certificate had expired. The firewall's decryption policy is configured to use
the untrusted CA with expired certificates.
C. The SaaS's certificate was replaced with one whose certificate authority is not known to
the firewall. The firewall's decryption policy is configured to block connections with
certificates whose CA is not trusted.
D. The SaaS's certificate was replaced with one whose certificate authority is not known to
the firewall. The firewall's decryption policy is configured to use the untrusted certificate
for certificates whose CA is not trusted.
E. The firewall's own CA certificate needs to be updated.
168. Which encryption algorithm is not supported by the firewall and causes the firewall to
drop the connection?
A. DES
B. 3DES
C. AES252-CBC
D. AES256-GCM
X.509 certificates are used to establish trust between a client and a server to establish an SSL connection.
The certificate contains either the FQDN of the server or its IP address in the common name (CN) field. All
certificates must be issued by a certificate authority (CA). After the CA verifies a client or server, the CA
issues the certificate and signs it with the CA’s private key. The client already has the CA’s public key to
verify those signatures.
With a Decryption policy configured, a session between the client and the server is established only if the
firewall trusts the CA that signed the server certificate. To establish trust, the firewall must have the
server root CA certificate in its certificate trust list (CTL) and use the public key contained in that root CA
certificate to verify the signature. The firewall then presents a copy of the server certificate signed by the
Forward Trust certificate for the client to authenticate. You also can configure the firewall to use an
enterprise CA as a forward trust certificate for SSL Forward Proxy. If the firewall does not have the server
root CA certificate in its CTL, the firewall will present a copy of the server certificate signed by the
Forward Untrust certificate to the client. The Forward Untrust certificate ensures that clients are
prompted with a certificate warning when they attempt to access sites hosted by a server with untrusted
certificates.
References
• Keys and Certificates for Decryption Policies
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/decryption/decryption-
concepts/keys-and-certificates-for-decryption-policies.html
• Certificate Management
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/certificate-management.html
• How to Install a Chained Certificate Signed by a Public CA
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClkoCAC
Sample Questions
169. Which condition could be a symptom of a certificate chain-of-trust issue?
A. The firewall no longer decrypts HTTPS traffic.
B. The firewall no longer decrypts HTTPS traffic from a specific site.
C. The firewall still decrypts HTTPS traffic from all sites, but it re-encrypts it using the
Forward Untrust certificate instead of the Forward Trust certificate.
D. The firewall still decrypts HTTPS traffic from a specific site, but it re-encrypts it using the
Forward Untrust certificate instead of the Forward Trust certificate.
References
• Virtual Routers
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/virtual-routers.html
Site-to-Site VPN with Static and Dynamic Routing
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/vpns/site-to-site-vpn-quick-
configs/site-to-site-vpn-with-static-and-dynamic-routing.html
• Static Routes
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/static-routes/static-
route-overview.html
• RIP
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/rip.html
• OSPF
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/ospf.html
• BGP
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/bgp.html
Bootstrapping enables you to create a repeatable and streamlined process of deploying new firewalls on
your network because it enables you to create a package and then use that package to deploy firewalls
anywhere. You can bootstrap a physical or VM-Series firewall off an external device to complete the
process of configuring and licensing the firewall. External devices include a USB thumb drive, virtual disk,
virtual CD-ROM, or a storage bucket such as AWS S3 or Google Cloud bucket.
For security reasons, you can only bootstrap a firewall when it is in factory default state. If your firewall
will not bootstrap, ensure that it is in factory default mode. The following link contains the procedure to
reset a firewall to its factory default settings. https://docs.paloaltonetworks.com/pan-os/9-0/pan-os-
admin/firewall-administration/reset-the-firewall-to-factory-default-settings.html
If you intend for the firewall to receive a complete configuration at boot up rather than only a partial
network configuration, ensure that you have created the optional bootstrap.xml file in the /config
directory along with the init-cfg.txt file. The init-cfg.txt file contains only a partial firewall configuration
that provides the basic information the firewall needs to connect to your network.
If any of the required network parameters are missing in the init-cfg.txt file, the firewall exits the
bootstrap process and boots up using the default IP address, 192.168.1.1.
If you intend for Panorama to manage the bootstrapped firewall, then generate the VM auth key on
Panorama and ensure that you place the key in the init-cfg.txt file. Otherwise Panorama will not be able
to connect to and configure the bootstrapped firewall.
If your firewall is not licensed properly after bootstrapping, then ensure that you have used an auth
code bundle in the /license directory instead of individual auth codes. Using a bundle enables the
firewall or orchestration service to simultaneously fetch all license keys associated with a firewall. If you
use individual auth codes instead of a bundle, the firewall will retrieve only the license key for the first
auth code included in the file.
If you are bootstrapping a VM-Series firewall in KVM using the user-data method and a tar ball, then
ensure that your version of OpenStack Platform 5 (Icehouse based) has been patched appropriately.
Without the patch, use of a tar ball with the user-data method causes the nova boot command to fail.
The patch is located at https://bugs.launchpad.net/python-novaclient/+bug/1419859.
Reference
• Bootstrap error messages
https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/bootstrap-the-vm-
series-firewall/bootstrap-errors
Network Activity
The Network Activity tab displays an overview of traffic and user activity on your network, including the
top applications in use, the top users who generate traffic, and the most used security rules against which
traffic matches occur. You also can view network activity by source or destination zone, region, IP
address, ingress or egress interfaces, and GlobalProtect host information such as the operating systems
of the devices most commonly used on the network:
Threat Activity
The Threat Activity tab displays an overview of the threats on the network, focusing on the top threats:
vulnerabilities, spyware, viruses, hosts visiting malicious domains or URLs, top WildFire® submissions by
file type and application, and applications that use non-standard ports. The Compromised Hosts widget
in this tab (the widget is supported on some platforms only), supplements detection with better
visualization techniques; it uses the information from the correlated events tab (Automated Correlation
Engine > Correlated Events) to present an aggregated view of compromised hosts on your network by
source users and IP addresses and sorted by severity:
Blocked Activity
The Blocked Activity tab focuses on traffic that was prevented from coming into the network. The
widgets in this tab allow you to view activity denied by application name, username, threat name,
blocked content (files and data that were blocked by a File Blocking Profile). It also lists the top security
rules that were matched on to block threats, content, and URLs.
©2016-2020, Palo Alto Networks, Inc. 237
The Tunnel Activity tab displays the activity of tunnel traffic that the firewall inspected based on your
tunnel inspection policies. Information includes tunnel usage based on tunnel ID, monitor tag, user, and
tunnel protocols such as Generic Routing Encapsulation (GRE), general packet radio service (GPRS)
Tunneling Protocol for User Data (GTP-U), and non-encrypted IPsec.
With the release of PAN-OS 9.1, the ACC displays a graphical view of user activity in your GlobalProtect
deployment on the GlobalProtect Activity tab.
The GlobalProtect Host Information widget under the Network Activity tab displays information about
the state of the hosts on which the GlobalProtect agent is running; the host system is a GlobalProtect
endpoint. This information is sourced from entries in the HIP match log that are generated when the data
submitted by the GlobalProtect app matches a HIP object or a HIP Profile you have defined on the
firewall. If you do not have HIP Match logs, this widget is blank.
References
Use the Application Command Center:
https://docs.paloaltonetworks.com/pan-os/9-0/pan-os-admin/monitoring/use-the-application-
command-center.html
GlobalProtect Activity Charts:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-new-features/globalprotect-features/enhanced-
logging-for-globalprotect.html
With PAN-OS 9.1, the new log category eliminates the need for using log queries to filter and locate
GlobalProtect log entries. You can sort, filter, and query the GlobalProtect logs directly.
References
New GlobalProtect Log Category:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-new-features/globalprotect-features/enhanced-
logging-for-globalprotect.html
You must understand the cause of a degraded link performance to ensure the user experience during use
of an app or service that is not impacted. Also, your understanding of why your VPN clusters have links
that are impacted helps in fine-tuning your SD-WAN configuration to ensure the user experience during
the use of apps and services that are not affected by links with degraded health.
Steps:
1. Select Panorama > SD-WAN > Monitoring and view the Impacted VPN clusters:
2. Filter the VPN clusters based on your preferred metric from the Site drop-down list and select the
time frame. In this example, we are viewing All Sites containing impacted VPN clusters in the last
24 hours:
4. In the App Performance section, click an app to view detailed Traffic Characteristic information
about the app traffic such as the internet service(s) and links used:
• Review the pie chart to understand the breakdown of app traffic across your internet services.
• Review the Links Used section to understand which links the app traffic used and to understand
how many bytes were impacted out of the total bytes in the selected time frame:
Details about using the management web interface for testing can be found here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/policy/test-policy-rule-traffic-
matches.html
A dated but still useful article with examples for running the test command from the CLI is here:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClQSCA0
Sample Questions
178. What is the correct order of evaluation between the Security policy and the NAT policy?
A. NAT policy evaluated, Security policy evaluated, NAT policy applied, Security policy
applied
B. NAT policy evaluated, NAT policy applied, Security policy evaluated, Security policy
applied
C. NAT policy evaluated, Security policy evaluated, Security policy applied, NAT policy
applied
D. Security policy evaluated, NAT evaluated, NAT policy applied, Security policy applied
179. Which two statements are true regarding firewall policy? (Choose two.)
A. All policy rules are evaluated, and the most specific rule will match.
B. Policy rules are evaluated from the top down, and the first rule matched processes the
traffic.
C. Interzone traffic is allowed by default.
D. Intrazone traffic is allowed by default.
E. Outbound traffic is allowed by default. Only inbound traffic is evaluated.
The completion of these steps provides only a basic setup that is not comprehensive enough to protect
your network. The next phase is here:
https://docs.paloaltonetworks.com/best-practices/9-1/internet-gateway-best-practices.html
Security Profiles are an important aspect of protection, detection, and prevention for specific types of
threats. See the following document for more details:
https://docs.paloaltonetworks.com/best-practices/9-1/internet-gateway-best-practices/best-practice-
internet-gateway-security-policy/create-best-practice-security-profiles.html
Sample Questions
181. A URL Filtering Profile is part of which type of identification?
A. App-ID
B. Content-ID
C. User-ID
D. Service
182. Which stage of the attack lifecycle is most likely to be stopped by dividing the network into
separate security zones and enabling packet-based zone?
A. Reconnaissance
B. Execution
C. Lateral movement
D. Data exfiltration
183. Which component can tell you if an attack is an APT or a broad attack designed to produce
a botnet for future abuse?
A. next-generation firewall
B. WildFire
C. MindMeld
D. AutoFocus
©2016-2020, Palo Alto Networks, Inc. 248
5.3 Identify methods for identifying users
User-ID and Mapping Users
The User-ID feature of the Palo Alto Networks NGFW enables you to create policy rules and perform
reporting based on users and groups rather than on individual IP addresses.
User-ID seamlessly integrates Palo Alto Networks firewalls with a range of enterprise directory and
terminal services offerings, thus enabling you to associate application activity and policy rules to users
and groups, not just IP addresses. Furthermore, with User-ID enabled, the Application Command Center
(ACC), App Scope, reports, and logs all include usernames in addition to user IP addresses.
For user-based and group-based policies, the firewall requires a list of all available users and their
corresponding group mappings that you can select when defining your policies. The firewall collects
group mapping information by connecting directly to your LDAP directory server. No other types of
directory services are supported for group mapping.
Before the firewall can enforce user-based and group-based policies, it must be able to map the IP
addresses based in the packets it receives to usernames. User-ID provides many mechanisms to collect
this user-based mapping information.
A User-ID agent process runs either on the firewall (agentless implementation) or is installed as a
separate process on a Microsoft Windows-based host. This User-ID agent monitors various network
technologies for authentication events and gathers the data, creating a master IP-address-to-user
mapping table stored in the firewall. For example, the User-ID agent monitors server logs for login events,
probes clients, and listens for syslog messages from authenticating services. To identify mappings for IP
addresses that the agent didn’t map, you can configure the firewall to redirect HTTP requests to a Captive
Portal login. You can customize the user mapping mechanisms to suit your environment, and even use
different mechanisms at different sites.
In complex environments, multiple User-ID agents can be deployed to work collaboratively on a master
User-ID IP address-to-username mapping table. The following figure shows the main functionality of the
User-ID agent:
References
A complete overview of User-ID is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/user-id.html
Sample Questions
184. User-ID maps users to which type of information?
A. MAC addresses
B. IP addresses
C. IP address and port number
D. port numbers
185. User-ID uses which protocol to map between user identities and groups?
A. NetBIOS
B. LDAP
C. syslog
D. HTTPS
186. Which format do you use when calling the API to inform the firewall of a new IP address-
to-username mapping?
A. XML
B. JSON
©2016-2020, Palo Alto Networks, Inc. 250
C. YAML
D. Base64
Palo Alto Networks maintains the management plane and data-plane separation to protect system
resources.
Every Palo Alto Networks firewall assigns a minimum of these functions to the management plane:
• Configuration management
• Logging
• Reporting functions
• User-ID agent process
• Route updates
The data plane connects directly to the traffic interfaces. As more computing capability is added to more
powerful firewall models, the management planes and data planes gain other functionality as required,
sometimes implemented on dedicated cards. Several core functions gain field-programmable gate arrays
(FPGAs) or custom application-specific integrated circuits (ASICs) for flexible high-performance
processing. Additional management plane functions might include:
• First packet processing
• Switch fabric management
Sample Questions
187. On a PA-7000 Series firewall, which management function runs on a separate, dedicated
card?
A. configuration management
B. logging
C. reporting
D. management web service
188. Do some next-generation firewall models use FPGA chips?
A. no, never
B. yes, on the data plane, but only on higher-end models
C. yes, on the management plane, but only on higher-end models
D. on both data the data plane and the management plane, but only on higher-end models
189. Which function resides on the management plane?
A. App-ID matching
B. route lookup
C. policy match
D. logging
Palo Alto Networks QoS provides an “Application Aware” QoS service that can be driven by the traffic’s
App-ID. The firewall’s QoS implementation is a self-contained system local to the firewall that can
consider existing QoS packet markings but does not act directly on them. Traffic is evaluated against QoS
policy rules that include existing QoS packet markings, App-ID, and other matching conditions to assign a
traffic classification value of 1 through 8. These values are the basis for QoS decision making. QoS control
of traffic is limited to egress traffic for the configured interface(s) only. Ingress traffic cannot be managed.
The method available to write QoS marking into packet headers is an additional action found in Security
policy rules that applies to traffic that they process. This marking is not directly related to QoS processing
in the firewall.
QoS implementation on a Palo Alto Networks firewall begins with three primary configuration
components that support a full QoS solution: a QoS policy, a QoS Profile, and configuration of the QoS
egress interface. Each option in the QoS configuration task facilitates a broader process that optimizes
and prioritizes the traffic flow and allocates and ensures bandwidth according to configurable
parameters.
QoS Profiles describe the priority to be given to the specified traffic when the interface becomes
constrained. As priority decreases, more packets are randomly dropped until the constraint is cleared.
The number of packets dropped is determined by their assigned Priority. A real-time Priority setting
means no packet dropping will be performed. High-, medium-, and low-priority settings indicate that
greater levels of random packet dropping are performed during movement down the scale. No packets
are dropped until the egress traffic on the managed interface becomes constrained, meaning that
outbound traffic queues for the interface are filling faster than they can be emptied.
Profiles also specify the maximum bandwidth enforcement that is applied at all times. Bandwidth
configured as the maximum limit can be used by all traffic until the interface becomes constrained. After
an interface is constrained, then sessions might receive no more than their guaranteed bandwidth.
To apply a QoS Profile, assign it to an interface. All traffic on an interface is split between VPN (tunnel
interface) and everything else (cleartext). Each requires a QoS Profile assignment when present. Tabs are
available for optional QoS management that include source interface, source subnet, and tunnel interface
as matching conditions for the application of a QoS Profile.
Profiles are applied to interfaces to control their egress traffic. The following example shows a profile that
has been applied with the interface ethernet1/4:
Reference
A detailed discussion of QoS is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/quality-of-service.html
Sample Questions
190. Which parameter is important for QoS policy match decisions?
A. App-ID
B. Content-ID
C. User-ID
D. Ingress interface
191. What is the maximum number of QoS classes supported by the next-generation firewall?
A. 4
B. 8
C. 16
D. 32
WildFire is implemented in a Palo Alto Networks managed public cloud or a WF-500 appliance installed
on a user’s network.
WildFire looks within files or URLs for malicious activities and renders a verdict with an analysis report.
WildFire analyzes files and URLs using the following methods:
• Static analysis: Detects known threats by analyzing the characteristics of samples prior to
execution
WildFire operates analysis environments that replicate the following operating systems:
• Microsoft Windows XP 32-bit
• Microsoft Windows 7 32-bit (supported as an option for the WildFire appliance only)
• Microsoft Windows 7 64-bit
• Microsoft Windows 10 64-bit (WildFire cloud analysis only)
• Mac OSX (WildFire cloud analysis only)
• Android (WildFire cloud analysis only)
• Linux (WildFire cloud analysis only)
The WildFire public cloud also analyzes samples using multiple versions of software to accurately identify
malware that targets specific versions of client applications. The WildFire private cloud does not support
multi-version analysis and does not analyze application-specific samples across multiple versions.
Files that are sent to WildFire for analysis are not quarantined in the firewall during the analysis process.
They are forwarded normally to their destination. If WildFire detects malware, a notification can be sent,
which should then be treated as an Incident Response appropriate to the organization’s policies.
WildFire is available to every Palo Alto Networks firewall for use at no charge. A WildFire license is
available that provides additional WildFire features.
References
• A detailed description of WildFire is here:
https://docs.paloaltonetworks.com/wildfire/9-1/wildfire-admin.html
• The use of WildFire in firewall profiles is outlined here:
https://docs.paloaltonetworks.com/wildfire/9-1/wildfire-admin/submit-files-for-wildfire-
analysis/forward-files-for-wildfire-analysis.html
For end-user authentication via Authentication policy, the firewall directly integrates with several MFA
platforms (Duo v2, Okta Adaptive, PingID, and RSA SecurID) and integrates through RADIUS with other
MFA platforms.
MFA is driven by an Authentication policy that allows precise application of appropriate authentication.
These policy rules can invoke simple Captive Portal challenge pages for one-time authentication or can
include one (or more) integrated MFA vendor Server Profiles that are included in Authentication Profiles
for additional challenges.
Once a user successfully completes all challenges, an appropriate Security policy rule will be evaluated
that allows access to that protected service.
References
• Multi-Factor Authentication
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/authentication/authentication-
types/multi-factor-authentication.html
• Authentication Policy
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/authentication/authentication-
policy.html
The following figure shows the relationship of the required objects to configure the Authentication policy
rule.
• Authentication Enforcement object: Specifies the Authentication Profile to use and is assigned to
an Authentication policy rule. A Captive Portal authentication method also must be specified. A
custom message can be included for the user that explains how to respond to the challenge.
References
• Configure Multi-Factor Authentication
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/authentication/configure-multi-
factor-authentication.html
• Map IP Addresses to Usernames Using Captive Portal
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/user-id/map-ip-addresses-to-
users/map-ip-addresses-to-usernames-using-captive-portal.html
Sample Questions
198. What are the two Captive Portal modes? (Choose two.)
A. proxy
B. transparent
C. web form
D. certificate
E. redirect
In a Layer 3 deployment, the firewall uses virtual routers to obtain routes to other subnets by manually
defining static routes or through participation in one or more Layer 3 routing protocols (dynamic routes).
The routes that the firewall obtains through these methods populate the firewall’s IP routing information
base (RIB).
An interface configured as virtual wire will forward all traffic that meets the optional VLAN filter to its
partner virtual wire interface. This packet handling is done invisibly to the packet (also known as a Bump
in the Wire), which allows a firewall to be placed in an existing traffic path without requiring traffic
engineering of the infrastructure.
Palo Alto Networks firewalls also support Policy Based Forwarding. A Policy Based Forwarding rule can be
created that identifies specific traffic to forward to a specified interface bypassing any virtual router
lookup.
References
• Layer 2 Interfaces
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/configure-
interfaces/layer-2-interfaces.html
• Virtual Routers
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/networking/virtual-routers.html
• PBF (Policy-Based Forwarding)
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/policy/policy-based-
forwarding/pbf.html
• Use Case: PBF for Outbound Access with Dual ISPs
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/policy/policy-based-
forwarding/use-case-pbf-for-outbound-access-with-dual-isps.html
Sample Questions
201. A company has strict security requirements that require inspection of every connection
between two internal computers. Those internal computers are connected and disconnected
by non-technical users in an environment without a DHCP server. How does traffic get
forwarded between those internal computers?
A. a switch
B. a firewall configured as a switch, with Layer 2 interfaces
C. a firewall configured as a router, with Layer 3 interfaces
D. a firewall in TAP mode or Virtual Mirror mode
The completion of these steps provides only a basic setup that is not comprehensive enough to protect
your network. The next phase is here:
https://docs.paloaltonetworks.com/best-practices/9-1/internet-gateway-best-practices.html
Security Profiles are an important aspect of protection detection and prevention for specific types of
threats. See the following document for more details:
https://docs.paloaltonetworks.com/best-practices/9-1/internet-gateway-best-practices/best-practice-
internet-gateway-security-policy/create-best-practice-security-profiles.html
Security policy rules are matched from the top down. Up to two processing steps are in each Security
policy match. Step 1 confirms that a match has been made based on the matching conditions provided in
the Security policy. If a match is found in Step 1, the traffic is logged (based on that policy rule’s
configuration) and the chosen action (deny, allow, drop, reset) is performed. Once processing is
complete, there will be no further matching in the Security policy rulebase.
Security policy should use App-ID for match criteria rather than solely use services (ports) as match
criteria.
At the end of the list are two default policy rules: one for an intrazone allow and one for an interzone
deny. Taken together they implement the default security behavior of the firewall to block interzone
traffic and allow intrazone traffic. By default, traffic logging is disabled in both rules.
Security policy rules in PAN-OS software are configured by type: universal (default), interzone, and
intrazone. (All policy rules – regardless of type – are evaluated top down, first match, then exit.) The
universal type covers both interzone and intrazone.
Security policy “rule type” selects the type of traffic the policy applies to.
Throughput performance is not changed based on how quickly a match is made. Because evaluation is
top down, first match, then exit, exceptions to policy rules must appear before the general policy. Beyond
this policy, order is based on administrative preference. Use tags, a Policy search bar, or a global find to
quickly navigate to the policy or policy rules needed for moves, adds, changes, deletes, clones, and
troubleshooting.
Content scanning it consumes firewall resources after it is enabled. Consult a firewall comparison chart to
identify the model with appropriate “Threat Enabled” throughput.
Note: Files are not quarantined pending WildFire evaluation. In cases of positive malware findings, the
security engineer must use information collected on the firewall and by WildFire to locate the file
internally for remediation.
WildFire Profiles indicate which files are to be forwarded according to system-wide WildFire
configuration settings. WildFire typically renders a verdict on a file within 5 to 10 minutes of receipt.
WildFire analysis results in a detailed report including all aspects of the original file and the contained
malware. This report is a valuable tool that describes the exact nature of the detected threat. Discussion
of the report is here:
https://docs.paloaltonetworks.com/wildfire/9-1/wildfire-admin/monitor-wildfire-activity/wildfire-
analysis-reportsclose-up.html
URL filtering requires a URL Filtering subscription that keeps URL category classification information
current. This subscription provides descriptive data as to which type of information is at a given URL.
Profiles can implement various actions against categories that reflect the organization’s use policies and
risk posture.
After URL Filtering Profiles invoke an action, the user can be notified directly, thus reducing user
confusion about the cause. These response pages can be modified to meet an organization’s particular
need:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/url-filtering/customize-the-url-filtering-
response-pages.html
URL filtering databases from Palo Alto Networks and BrightCloud are available for the firewall, but only
one can be active at a given moment. Although they provide similar support to URL Filtering Profiles, the
way each approach works within the firewall differs. A brief discussion of the two methods is here:
https://docs.paloaltonetworks.com/pan-os/9-0/pan-os-admin/url-filtering/url-filtering-overview/url-
filtering-vendors.html
Specific information about implementing URL Filtering Profiles and their allowed actions is here:
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/url-filtering/configure-url-filtering.html
A complete firewall configuration can be read and applied via the Bootstrapping feature. You create a
package with the model configuration for your network and then use that package to deploy firewalls
(physical or virtual) anywhere. For physical firewalls, you use a USB drive. For virtual firewalls, you can use
a virtual disk, a virtual CD-ROM, an Azure Storage Account, or an AWS S3 bucket. You either can bootstrap
the firewall with basic initial configuration and licenses so that the firewall can register with Panorama
and then retrieve its full configuration from Panorama, or you can bootstrap the complete configuration
so that the firewall is fully configured on bootup.
References
• Prepare the Bootstrap Package
https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/bootstrap-the-vm-
series-firewall/prepare-the-bootstrap-package.html
• Bootstrap a Firewall using a USB Flash Drive
https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/firewall-administration/bootstrap-
the-firewall/bootstrap-a-firewall-using-a-usb-flash-drive.html
• Bootstrap the VM-Series Firewall in Azure
https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/bootstrap-the-vm-
series-firewall/bootstrap-the-vm-series-firewall-in-azure.html
• Bootstrap the VM-Series Firewall in AWS
https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-deployment/bootstrap-the-vm-
series-firewall/bootstrap-the-vm-series-firewall-in-aws.html
• AWS CloudFormation
https://aws.amazon.com/cloudformation/
• Working with Managed Policies
https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_manage.html#_create-
managed-policy-console
You can create Panorama templates using a CSV file and then push the configuration to the branch or hub
firewalls. From Panorama you can export an empty SD-WAN device CSV file and then populate the CSV
file with the branch and hub information. The information you will enter into a CSV includes serial
number, type of device (branch or hub), names of zones to map to predefined zones, loopback address,
prefixes to redistribute, AS number if you use BGP dynamic routing, router ID, and virtual router name.
Before you deploy your SD-WAN environment, you should determine the role of each firewall, either hub
or branch, and determine which branches will communicate with which hubs. Branches and hubs that will
communicate with each other are functionally grouped into a VPN cluster. You also may have cloud-
based services and want the internet traffic to flow directly from branch office to the cloud using DIA. Use
of DIA can prevent SaaS, web browsing, or heavy-bandwidth applications from having to flow from
branch office to the hub to the cloud and back.
A link bundle enables you to combine multiple physical links into one virtual SD-WAN interface for
purposes of path selection and failover protection. If you create a bundle with more than one physical
link, you maximize application quality if a physical link deteriorates. You create a bundle by applying the
same link tag to multiple links through an SD-WAN Interface Profile. The link tag identifies a bundle of
links that have a similar type of access and a similar type of SD-WAN policy handling.
The SD-WAN subscription supports dynamic, intelligent link selection based on applications and services
and the conditions of links that each application or service is allowed to use. The path health monitoring
for each link includes latency, jitter, and packet loss. Dynamic path selection avoids brownout and node
failure problems because sessions fail over to a better performing path in less than one second.
Link failover enables you to determine how and when a link will fail over to a different link if the original
link degrades or fails. When you plan link failover, you should prioritize the order in which the firewall
selects the first link for a new session and the order in which links should be a candidate to replace a link
that is failing over, if there is more than one candidate.
For the applications and services, you should plan your path health thresholds at the point where you
consider a path to have degraded enough in quality that you want the firewall to select a new path or fail
over. The quality characteristics are latency (range is 10 to 2,000ms), jitter (range is 10 to 1,000ms), and
packet loss percentage.
You can monitor the application and link performance of your VPN clusters to troubleshoot issues by
©2016-2020, Palo Alto Networks, Inc. 279
viewing summary information across all VPN clusters. You can gather more detailed information by
drilling down to isolate the issues to affected sites, applications, and links.
References
SD-WAN Administrator’s Guide:
https://docs.paloaltonetworks.com/sd-wan/1-0/sd-wan-admin.html
Automatic commit recovery enables you to configure the firewall to attempt a specified number of
connectivity tests after you push a configuration change from Panorama or commit a configuration
change locally on the firewall. Automatic commit recovery is enabled by default, thus enabling the
managed firewalls to locally test the configuration pushed from Panorama to verify that the new changes
do not break the connection between Panorama and the managed firewall. If the committed
configuration breaks the connection between Panorama and a managed firewall, then the firewall
automatically fails the commit and the configuration is reverted to the previous running configuration.
The firewall also checks connectivity to Panorama every hour to ensure consistent
communication if unrelated network configuration changes have disrupted connectivity between the
firewall and Panorama or if implications to a pushed committed configuration may have affected
connectivity. If an hourly connectivity check fails, the firewall generates a system log to alert
administrators of potential configuration or network connectivity issues. An event is generated in the
system log when you disable the setting, a connectivity test fails, or when a firewall configuration reverts
to the last running configuration.
In high availability (HA) firewall configurations, each HA peer performs connectivity tests independently
of each other, and HA config syncs may occur only after each HA successfully tests connectivity to
Panorama and verifies its connection.
References
Panorama Commit, Validation, and Preview Operations:
https://docs.paloaltonetworks.com/panorama/9-1/panorama-admin/panorama-overview/panorama-
commit-validation-and-preview-operations.html#id1657d230-91b0-4ef0-99d2-dc344e5cf50f
1.2 Given a scenario, identify how to design an implementation of the firewall to meet business
requirements that leverage the Palo Alto Networks Security Operating Platform
8. A potential customer says it wants to maximize the threat detection capability of its next-
generation firewall. Which three additional services should it consider implementing to
enhance its firewall’s capability to detect threats? (Choose three.)
A. Traps
B. WildFire
C. URL Filtering
D. Expedition
E. DNS Security
9. A VM-Series virtual firewall differs from a physical Palo Alto Networks firewall in which way?
A. A VM-Series firewall cannot be managed by Panorama.
B. A VM-Series firewall supports fewer traffic interface types.
C. A VM-Series firewall cannot terminate VPN site-to-site tunnels.
D. A VM-Series firewall cannot use dynamic routing protocols.
10. Which product would best secure east-west traffic within a public cloud implementation?
A. Prisma Cloud
B. MineMeld
C. VM-Series firewall
D. Cortex
1.3 Given a scenario, identify how to design an implementation of firewalls in High Availability to
meet business requirements that leverage the Palo Alto Networks Security Operating Platform
11. Why would you recommend an active/active firewall cluster instead of an active/passive
firewall cluster?
A. Active/active is the preferred solution when the firewall cluster is behind a load
balancer that randomizes routing, thus requiring both firewalls to be active.
B. Active/active usually is the preferred solution because it allows for more bandwidth while
both firewalls are up.
C. Active/active is the preferred solution when the PA-7000 Series is used. Use
active/passive with the PA-5200 Series or smaller form factors.
D. Active/active is the preferred solution when the PA-5200 Series or smaller form factors
are used. Use active/passive with the PA-7000 Series.
1.4 Identify the appropriate interface type and configuration for a specified network deployment
16. Without having to make network address configuration changes, you would use which type
of network interface to insert a Palo Alto Networks firewall in front of a legacy port-based
firewall to collect application information from incoming network traffic?
A. VLAN
B. tunnel
C. tap
D. virtual wire
E. Layer 2
F. Layer 3
1.5 Identify strategies for retaining logs using Distributed Log Collection
22. In a Panorama environment, how do you create and view enterprise-wide reports that include
data from all managed firewalls?
A. Run Panorama reports normally. Firewall summary reporting information is gathered
automatically once the firewalls are managed by Panorama.
B. Configure log forwarding on the managed firewalls to forward logs to Panorama using
syslog formatting.
C. Run custom Panorama reports and select remote logs as the information source.
D. Run custom Panorama reports and select log collector as the information source.
1.6 Given a scenario, identify the strategy that should be implemented for Distributed Log
Collection
26. How are log retention periods on Palo Alto Networks firewalls increased?
A. add storage to any firewall model
B. increase the allocation for overall log storage within the firewall
C. turn on log compression
D. forward logs to external Log Collectors
27. How do you access, and view firewall log data sent to the Cortex Data Lak?
A. direct viewing and searching with the Cortex gateway
B. Panorama using a Log Collector configuration for access
C. reporting in a firewall using a “remote data source” configuration
D. reporting in a firewall equipped with a “Remote Logging” plugin
28. Log retention is increased when a Dedicated Log Collector is used to collect logs from firewalls
in which two ways? (Choose two.)
A. turning on “Log Compression” in the Log Collector
B. adding storage capacity to the Log Collector
C. enabling “Log Storage Sharing” between the Log Collector and Panorama
D. adding Log Collectors to the Log Collector Group
1.8 Identify how to use device group hierarchy for administering Palo Alto Networks firewalls as a
scalable solution using Panorama
32. Where in Panorama do you enter Security policy rules to ensure that your new rules will take
precedence over locally entered rule?
A. Security policy rules with a targeted firewall
B. default rules section of Security policy rules
C. pre-rules section of Security policy rules
D. post-rules section of Security policy rules
33. In Panorama, how would you make changes to a Security policy rule for a specific firewall?
A. log in to Panorama, clone the rule, modify the clone, and add a target firewall to the
new rule
B. select the rule, click the override button, and enter the changes
C. create a new locally defined Security policy rule that is placed higher in the rule list than
the rule to be overridden
D. log in to Panorama and modify the original rule
1.9 Identify planning considerations unique to deploying Palo Alto Networks firewalls in a public
cloud
35. Which part of a VM-Series firewall should be updated to provide maximum feature support for
a public cloud?
A. latest PAN-OS update
B. latest VM-Series plugin
C. capacity license for the target public cloud.
D. latest dynamic updates appropriate for the implemented PAN-OS version
36. Which two types of firewall interfaces are most likely to be supported in public cloud
deployments? (Choose two.)
A. tap
B. virtual wire
C. Layer 3
D. tunnel
E. aggregate Ethernet
37. From where can you buy and download a VM-Series virtual firewall appliance for a public
cloud deployment?
A. Palo Alto Networks Support Portal
B. cloud vendor’s “Solution Marketplace”
C. Using the download link supplied on the same site as the license server
D. Palo Alto Networks Product Download portal
1.10 Identify planning considerations unique to deploying Palo Alto Networks firewalls in a hybrid
cloud
38. Which two conditions must be met to manage Palo Alto Networks firewalls deployed in
multiple cloud environments from a central Panorama? (Choose two.)
A. The Panorama and firewall must be able to communicate.
B. The Panorama must be licensed for each cloud environment containing managed firewalls.
C. The firewalls must have the latest VM-Series plugin installed.
D. The firewalls and Panorama must be running the same version of PAN-OS software.
E. Firewalls must be running a version of PAN-OS software equal to or less that that on
Panorama.
1.17 Identify the impact of application override to the overall functionality of the firewall
58. An App-ID used in an Application Override policy rule should have which characteristic?
A. existing App-ID that uses the same decoder
B. new App-ID with no signature information
C. new App-ID with the “custom” property set to yes
D. any existing App-ID with compatible characteristics
59. Which type of identification is disabled by Application Override?
A. Protocol-ID
B. User-ID
C. Content-ID
D. URL Filtering
60. Application Override is triggered by which configuration setting?
A. Custom App-ID
B. Application Override policy rule
C. Application Override definition in Custom Objects
D. Application Filters
2.2 Given a scenario, identify the set of Security Profiles that should be used
70. Which profile do you use for DLP based on file content?
A. Antivirus
B. Anti-Spyware
C. Vulnerability Protection
D. URL Filtering
E. File Blocking
F. WildFire Analysis
G. Data Filtering
71. Which profile do you use to monitor DNS resolution lookups for sites associated with threat
activity?
A. Antivirus
B. Anti-Spyware
C. Vulnerability Protection
D. URL Filtering
E. File Blocking
F. WildFire Analysis
G. Data Filtering
72. Which profile do you use to analyze files for zero-day malware?
A. Antivirus
B. Anti-Spyware
C. Vulnerability Protection
D. URL Filtering
E. File Blocking
F. WildFire Analysis
G. Data Filtering
2.3 Identify the relationship between URL filtering and credential theft prevention
75. Which credential phishing prevention action allows users to choose to submit credentials to a
site anyway?
A. alert
B. allow
C. block
D. continue
76. Which user credential detection method would work if multiple users share the same client IP
address (for example, because of dynamic address translation done by a device on the internal
side of the firewall)?
A. IP-to-user mapping
B. group mapping
C. domain credential filter
D. IP-and-port-to-user mapping
77. Which type of user credential detection must be used by a firewall administrator that wants to
enable credential phishing prevention that blocks an attempt by a user to enter the
organization’s user ID and password?
A. IP-to-user mapping
B. domain credential filter
C. group mapping
D. Citrix mapping
2.5 Identify how to create security rules to implement App-ID without relying on port-based rules
81. Which firewall tool provides settings and tools to convert policies from port-based to App-ID?
A. Network Monitor display under App Scope
B. Policy Optimizer under Policies
C. Application Hit Count under Policies
D. View Applications as Groups under Policies
2.11 Identify how to configure and maintain certificates to support firewall features
95. How are updates made to the cache of root certificates that is used for certificate verification
purposes and maintained by Palo Alto Networks?
A. The administrator reviews certificate status and replaces them manually.
B. The firewall automatically updates the certificates as it updates the associated CRL list.
C. The administrator installs PAN-OS software and dynamic content updates.
D. The firewall automatically installs new certificates using OCSP.
96. How does a firewall administrator that creates a certificate on the firewall mark it for use in an
SSL Forward Proxy configuration?
A. add a certificate tag in the Decryption policy rule
B. configure a trust certificate in the Decryption Profile
C. set the Forward Trust Certificate property of the certificate itself
D. map the certificate to the URL in the SSL/TLS Service Profile
2.14 Given a scenario, identify how to configure an interface as a DHCP relay agent
103. A Palo Alto Networks firewall can forward DHCP packets to servers connected to which
two kinds of networks? (Choose two.)
A. virtual wire
B. Layer 2
C. Layer 3
D. aggregate
104. How does a Palo Alto Networks firewall configured to forward DHCP packets to multiple
server destinations choose which reply to forward to the sender?
A. The first server listed in the “Server Priority” DHCP configuration is forwarded until it fails
to respond, then the next one is chosen.
B. A request is sent to all servers on the list, and the first responder is forwarded.
C. All DHCP server responses are forwarded, and the receiving client chooses which to
accept.
D. The server that is the fewest network hops from the requesting client is chosen. When
more than one server has the same hop count, all packets from the servers are
forwarded to the client.
2.15 Identify the configuration settings for site‐to‐site VPN
105. In a site-to-site VPN configuration, what is an alternate method to the use of pre-shared
keys to authenticate each device during connection setup?
A. certificates
B. expected IP address of the partner’s interface
C. known hexadecimal string configured in both endpoints
D. matching Proxy ID definitions configured in both endpoints
106. Which type of firewall interface can be associated with a tunnel interface?
A. tap
B. virtual wire
C. Layer 2
D. Layer 3
2.19 Given a configuration example including DNAT, identify how to configure security rules
114. A server on the DMZ with a private NIC address has network access provided by a NAT
policy rule whose Bi-directional check box is selected in the Translated Packet settings for
static IP source address translation. Which Security policy rule must be created to allow bi-
directional traffic to and from the DMZ server?
A. a rule for each direction of travel using the pre-NAT server IP address
B. a rule with the post-NAT source IP address
C. a rule for each direction of travel using the post-NAT server IP address
D. a rule with the pre-NAT source IP address
115. An internal web browser sends a packet to a server. The browser’s connection has the
source IP address 192.168.5.3, port 31415. The destination is 209.222.23.245, port 80. The
firewall translates the source to 75.22.21.54, port 27182. Which three of these source IP
addresses would cause a NAT policy rule to apply to this traffic? (Choose three.)
A. 192.168.5.0/24
B. 75.22.21.0/24
C. 192.168.4.0/23
D. 192.168.0.0/16
E. 75.22.0.0/17
F. 75.22.128.0/17
116. A NAT policy rule is created to change the destination address of any packets with a
source of any address and a destination address of 10.10.10.10 (in the DMZ zone) to
192.168.3.45 (in the Trust zone). Which Security policy rule components are required for a
packet that has this rule applied to match and allow this traffic?
A. source address any, source zone any, destination address 192.168.3.45, destination zone
Trust, action = allow
B. source address any, source zone any, destination address 10.10.10.10, destination zone
Trust, action = allow
C. source address any, source zone any, destination address 192.168.3.45, destination zone
DMZ, action = allow
D. source address any, source zone any, destination address 10.10.10.10, destination zone
DMZ, action = allow
2.21 Given a scenario, identify an application override configuration and use case
120. Which option is not a parameter used to identify applications in an Application Override
policy?
A. protocol
B. port number
C. first characters in the payload
D. destination IP address
121. How does the firewall resolve conflicting App-ID assignments to the same traffic between
an Application Override policy rule and the firewall’s built-in App-ID?
A. The firewall’s regular App-ID is assigned.
B. The Application Override’s App-ID is assigned.
C. The App-ID is set to duplicate definitions.
D. The App-ID is set to not available.
122. Which firewall process is bypassed when an Application Override policy matches traffic
and assigns an App-ID?
A. QoS
B. IPsec
C. Content-ID
D. User-ID
2.23 Identify how to configure firewalls to use tags and filtered log forwarding for integration
with network automation
127. Dynamic tags can be assigned to which kind of data in a log event?
A. source and destination address, source and destination zone name
B. source and destination address
C. interface, zone name
D. DNS name, zone name
128. How can the firewall use dynamically tagged objects to block traffic?
A. Add the object to an enforcement list of a Data Filtering object that then is attached to a
Security policy rule.
B. Assign the object to a dynamic list, which then is included in the destination address
matching condition of a Security policy rule.
C. Assign the object to a Dynamic Address Group object, which then is added to the
destination address matching condition of a Security policy rule.
D. Add the object to an Application Group and use it in Security policy rules.
3.2 Interpret log files, reports, and graphs to determine traffic and threat trends
134. Which filter finds all log entries for traffic that originates from the internal device whose IP
address is 172.17.1.3 and according to the header appears to be HTTP or HTTPS?
A. ( addr.src in 172.17.1.3 ) and ( ( port.dst eq 80 ) or ( port.dst eq 443 ) )
B. ( ( addr.src in 172.17.1.3 ) and ( port.dst eq 80 ) ) or ( port.dst eq 443 )
C. ( src.addr in 172.17.1.3 ) and ( ( dst.port eq 80 ) or ( dst.port eq 443 ) )
D. ( ( src.addr in 172.17.1.3 ) and ( dst.port eq 80 ) ) or ( dst. port eq 443 )
3.3 Identify scenarios in which there is a benefit from using custom signatures
137. How would you configure the firewall to control access to a custom DNS application that
operates differently from the standard DNS application?
A. You cannot do it with the next-generation firewall. You need to manually configure a
proxy.
B. Create specific rules for the sources and destinations that run this application.
C. Create a custom DNS application and add it to separate Security policy rules.
D. Create an Application Override policy and specify the sources and destinations that run
this application.
138. What are two results of using Application Override policies? (Choose two.)
A. prevent matching traffic from entering VPN tunnels
B. apply a specified App-ID label to matching traffic
C. prevent matching traffic from being logged
D. cause matching traffic to bypass Content-ID processing
E. route traffic to WildFire for scanning
139. Which two types of entities can have custom signatures? (Choose two.)
A. services
B. URL categories
C. user groups
D. applications
E. vulnerabilities
3.4 Given a scenario, identify the process to update a Palo Alto Networks system to the latest
version of the software
140. Match the upgrade step description with the correct step number.
Upgrade PAN-OS software Step 3
Reboot the firewall Step 4
Update dynamic content Step 2
Activate subscription licenses Step 1
3.5 Identify how configuration management operations are used to ensure desired operational
state of stability and continuity
143. What is the format of the firewall configuration files?
A.
YAML
B.
JSON
C.
XML
D.
CSV
144. Which method can be used to restore the previous configuration when a new
configuration committed on a firewall has undesired consequences?
A. Use the Load configuration version to restore the previous configuration settings, and
follow with commit.
B. Use the Rollback commit link in the commit completion message.
C. Use the Import device state to restore the pre-commit configuration.
D. Use the Load named configuration snapshot to restore the previous configuration, and
follow with a commit.
145. Which CLI command do you use to move a configuration file from an external server to a
firewall’s local storage?
A. rdist
B. ssh
C. scp
D. rcp
3.8 Identify how to configure the firewall to integrate with AutoFocus and verify its functionality
149. Which method is used to connect a firewall to AutoFocus to query data?
A. Click the AutoFocus link in the firewall management user interface under Device >
Licenses > AutoFocus
B. Click the link found in the log events under the firewall’s Monitor > Logs > AutoFocus
C. Configure the connection using the Dashboard’s AutoFocus widget
D. Click the link found in the log event under the firewall’s Monitor > <threat-related log>
> <threat detail>
150. What is a principle benefit of the AutoFocus product?
A. provide additional threat detection data to the firewall
B. manage access to SaaS applications through the firewall
C. provide additional context to previously discovered threats
D. examine Cortex Data Lake log data for undetected threats
3.10 Identify the relationship between Panorama and devices as pertaining to dynamic updates
versions and policy implementation and/or HA peers
154. How are HA firewall pairs kept in sync when Panorama pushes dynamic updates?
A. Panorama delivers the dynamic update to the active firewall(s) of the HA pair and
updates the passive partner when a failover occurs in active/passive pairs.
B. Panorama delivers the update to one firewall, which syncs with its HA partner.
C. Panorama delivers the dynamic update to both firewalls simultaneously.
D. Panorama delivers the dynamic update to the active firewall, which triggers the passive
partner to request the file from Panorama.
155. Which type of device can receive the Antivirus content update?
A. Log Collector
B. firewall
C. AutoFocus
D. MindMeld
156. Which requirement must a Panorama meet to update a managed firewall’s antivirus
signatures?
A. The PAN-OS versions on the firewall and Panorama must be the same.
B. Panorama and the firewall must be able to connect to the Palo Alto Networks update
server.
C. The update must be installed on Panorama before it is installed on any firewalls.
D. Panorama must download an antivirus file version compatible with the target firewall’s
PAN-OS version.
4.2 Given a session output, identify the configuration requirements used to perform a packet
capture
160. Which Security Profile does not have a packet capture option?
A. Antivirus
B. Anti-spyware
C. Vulnerability Protection
D. URL Filtering
161. On a PA-7080, which feature (do you need to disable to use packet capture?
A. NAT
B. hardware offload
C. hardware acceleration
D. decryption
162. When must you use tcpdump to capture traffic on the next-generation firewall?
A. on tunnel interface traffic
B. on data-plane interfaces
C. on the management interface
D. on IPsec negotiation traffic
5.2 Given an attack scenario, identify the appropriate Palo Alto Networks threat prevention
component to prevent or mitigate the attack
181. A URL Filtering Profile is part of which type of identification?
A. App-ID
B. Content-ID
C. User-ID
D. Service
5.4 Identify the fundamental functions residing on the management plane and data plane of a
Palo Alto Networks firewall
187. On a PA-7000 Series firewall, which management function runs on a separate, dedicated
card?
A. configuration management
B. logging
C. reporting
D. management web service
188. Do some next-generation firewall models use FPGA chips?
A. no, never
B. yes, on the data plane, but only on higher-end models
C. yes, on the management plane, but only on higher-end models
D. on both data the data plane and the management plane, but only on higher-end models
©2016-2020, Palo Alto Networks, Inc. 325
189. Which function resides on the management plane?
A. App-ID matching
B. route lookup
C. policy match
D. logging
5.5 Given a scenario, determine how to control bandwidth use on a per-application basis
190. Which parameter is important for QoS policy match decisions?
A. App-ID
B. Content-ID
C. User-ID
D. Ingress interface
191. What is the maximum number of QoS classes supported by the next-generation firewall?
A. 4
B. 8
C. 16
D. 32
5.10 Given a scenario, identify how to configure policies and related objects
204. Which action specifies that Security Profiles are relevant in a policy rule?
A.
deny
B.
drop
C.
reset
D.
allow
205. Are files quarantined while WildFire checks if they are malware or legitimate?
A. always yes
B. always no
C. by default, yes, but you can change the settings
D. by default, no, but you can change the settings
206. Which feature of the next-generation firewall allows you to block websites that are not
business-appropriate?
A. App-ID
B. File Blocking
C. Exploit Protection
D. URL Filtering
Digital Learning
For those of you who want to keep up to date on our technology, a learning library of free digital learning
is available. These on-demand, self-paced digital learning classes are a helpful way to reinforce the key
information for those who have been to the formal hands-on classes. They also serve as a useful overview
and introduction to working with our technology for those unable to travel to a hands-on, instructor-led
class.
Simply register in our Learning Center and you will be given access to our digital learning portfolio. These
online classes cover foundational material and contain narrated slides, knowledge checks, and, where
applicable, demos for you to access.
New courses are being added often, so check back to see new curriculum available.
Instructor-Led Training
Looking for a hands-on, instructor-led course in your area?
Palo Alto Networks Authorized Training Centers (ATCs) are located globally and offer a breadth of
solutions from onsite training to public, open environment classes. There are about 38 authorized
training centers at more than 80 locations worldwide. For class schedule, location, and training offerings
see https://www.paloaltonetworks.com/services/education/atc-locations.