NetSec-Pro Palo Alto Networks Network Security Professional Questions and Answers

When migrating from a perpetual VM-Series firewall license to a flexible VM licensing model , two critical steps are needed:

Allocate same number of vCPUs – This ensures that the VM-Series capacity remains consistent and avoids resource bottlenecks.

“When migrating perpetual VM-Series licenses to flexible VM licensing, allocate the same vCPU and memory resources to ensure equivalent performance.”

(Source: VM-Series Flexible Licensing Migration)

Limit to same security services – Flexible licensing requires maintaining the same security services to preserve licensing compliance.

“Ensure that you allow only the same security services on the flexible VM instance as were licensed on the perpetual VM.”

(Source: Flexible Licensing and Service Subscriptions)

In cloud environments like Azure, the VM-Series NGFW is deployed to create Layer 3 segmentation zones closest to the application workloads.

“In Azure, deploy VM-Series firewalls in Layer 3 mode to enforce security policies closest to private applications, meeting strict compliance and segmentation requirements.”

(Source: VM-Series in Public Clouds)

Layer 3 segmentation ensures security policies are enforced at the right boundary to isolate traffic within Azure’s virtual networks.

To connect a remote network to Prisma Access via Strata Cloud Manager (SCM), the remote network requires an IPSec termination node . This acts as the VPN endpoint, ensuring secure connectivity between branch locations and Prisma Access.

“To onboard a remote network, configure the IPSec termination node on the customer’s premises. This VPN endpoint establishes the secure tunnel to Prisma Access for traffic backhauling.”

(Source: Onboard Remote Networks)

Key takeaway:

The IPSec termination node is fundamental for secure, encrypted connectivity.

Threat logs for Prisma Access mobile users can be reviewed in both Strata Cloud Manager (SCM) and Strata Logging Service . Prisma Cloud and service connection firewalls are not directly tied to mobile user traffic logs.

“Prisma Access logs are available in the Strata Cloud Manager and can also be sent to the Strata Logging Service for detailed analysis and threat visibility.”

(Source: Prisma Access Administration Guide)

WildFire inline ML detection supports PE files , which are Windows Portable Executable files such as .exe and .dll.

For Zero Touch Provisioning, the firewall must be registered and claimed, CSP registration must be valid, and Panorama must have the required device group and template configuration prepared before onboarding.

To inspect SaaS app traffic (often encrypted), you must configure:

SSL Forward Proxy

“The SSL Forward Proxy decryption profile enables the firewall to decrypt outbound SSL traffic, essential for visibility into SaaS app usage.”

(Source: SSL Forward Proxy Overview)

Validate certificates

“Validating and deploying the appropriate root and intermediate CA certificates is critical for establishing trust and preventing SSL errors during decryption.”

(Source: Certificate Deployment and Validation)

Without these steps, SaaS decryption and policy enforcement would be incomplete.

For IoT Security to accurately classify and monitor IoT devices, the following logs must be forwarded to Strata Logging Service:

Enhanced application logs – provide detailed application usage and behaviors, essential for profiling device types and roles.

“Enhanced Application logs provide additional context on IoT device behavior and usage patterns, and must be forwarded to Strata Logging Service for IoT Security to build accurate Device-ID profiles.”

(Source: IoT Security Logging Requirements)

Threat logs – essential for detecting suspicious or malicious activities by IoT devices.

“Threat logs are critical for identifying potential exploits or suspicious activities involving IoT devices and are required for accurate threat visibility within IoT Security.”

(Source: IoT Security Logs)

These logs collectively ensure accurate device classification and real-time threat visibility.

GlobalProtect HIP checks can evaluate host posture information including anti-malware status, disk encryption, patch levels, firewall status, and other endpoint security attributes.

Device grouping rules in SCM allow administrators to organize firewalls into logical groups and collectively manage updates or configuration pushes across those groups.

“SCM allows you to create device group rules, enabling streamlined management and collective updates of multiple NGFW instances.”

(Source: SCM Device Grouping)

This approach ensures consistency in software versions and configuration baselines across large deployments.

In Prisma Access, the interzone security policy rule is available and plays a crucial role in controlling traffic between zones.

“You can configure an interzone rule to control traffic that flows between different zones in Prisma Access, enabling granular security policy enforcement.”

(Source: Prisma Access Security Policies)

This ensures comprehensive control of traffic crossing security boundaries in the cloud-delivered architecture.

GlobalProtect logs

These logs provide detailed insights into the user’s connectivity, tunnel status, and authentication events.

“GlobalProtect logs include detailed information about connection establishment, tunnel negotiation, and any errors that can prevent mobile users from accessing applications.”

(Source: GlobalProtect Troubleshooting)

Autonomous Digital Experience Management (ADEM)

ADEM helps visualize end-to-end performance and identifies network issues affecting SaaS app access for mobile users.

“ADEM provides real-time and historical visibility into user experience, enabling quick identification and resolution of connectivity or performance issues for SaaS applications.”

(Source: ADEM for Prisma Access)

Palo Alto Networks requires upgrading to the next major feature release before moving to newer releases. This ensures stability and compatibility.

“When upgrading across multiple major PAN-OS releases, you must upgrade to each intermediate major feature release. Skipping major releases is not supported.”

(Source: Upgrade Considerations)

For PAN-OS 9.1 → 11.2, the proper path is:

9.1 → 10.0 → 11.2

The firewall must be running a PAN-OS version that is supported by Panorama. This means that Panorama must be running the same or a newer PAN-OS version as the one being installed on the firewalls to maintain compatibility.

“Before you upgrade the firewall, ensure that Panorama is running the same or a later PAN-OS version than the firewall. Panorama must always be at the same or a higher version to maintain compatibility.”

(Source: Panorama Admin Guide – Upgrade Process)

The Anti-spyware profile includes DNS-based protections like sinkholing and detection of DNS queries to malicious domains, offering real-time protection against attacks that exploit DNS misconfigurations.

“The Anti-Spyware profile protects against DNS-based threats by sinkholing DNS queries to malicious domains and detecting suspicious DNS activity, thus blocking data exfiltration and C2 communication.”

(Source: Anti-Spyware Profiles)

A security profile group named “default” is automatically applied to all new security rules unless a specific profile group is explicitly configured.

“If a security profile group named ‘default’ exists, it will be automatically applied to any newly created security policy rules to ensure consistent protection.”

(Source: Security Profile Groups)

This behavior ensures that newly created policies are always protected by default security profiles, minimizing human error.

Cloud NGFW for AWS can be configured using Panorama for centralized management, as well as the AWS management console for native integration and configuration.

“You can configure Cloud NGFW for AWS using Panorama for centralized security management, or directly through the AWS management console to deploy and manage security services for your AWS resources.”

(Source: Cloud NGFW for AWS Guide)

Advanced DNS Security uses a signature policy to sinkhole malicious DNS queries and prevent them from resolving.

“The DNS Security service integrates with Anti-Spyware profiles, and you must configure signature policy settings to sinkhole malicious queries. This proactively stops traffic to known malicious domains.”

(Source: Configure DNS Security)

Sinkholing ensures that DNS queries to malicious FQDNs are redirected to a safe IP, preventing compromise.