To successfully implement an IPSec VPN on a Palo Alto Networks NGFW, the security architect must account for two distinct types of traffic:Control Plane(tunnel negotiation) andData Plane(traffic through the tunnel).
First, for the tunnel to establish, the firewall must permit negotiation traffic. While IKE (UDP 500/4500) is the protocol used, Palo Alto Networks uses theIPSec container applicationto represent the underlying encrypted tunnel traffic. This traffic is typically destined for the firewall's own "Local" zone (the management
/loopback or physical interface IP). Therefore, a policy must exist to allow theipsec-esp-udpor the broader IPSecapplication between the external-facing zone and theLocal zone.
Second, once the tunnel is active, the decrypted traffic emerges from theTunnel Interface. This interface must be assigned to a security zone (often a dedicated "VPN" zone or an existing internal zone). Because the NGFW is a stateful, zone-based firewall, theinterzone-defaultpolicy is "Deny" by default. Consequently, a pair of security policies is required to allow data to flow: one for traffic entering the tunnel (e.g., Trust to VPN) and one for traffic exiting the tunnel (e.g., VPN to Trust). Without these specific rules, the tunnel may show as "Up" (Phase 1 and 2 complete), but no production data will pass through it.

To configure the management interface as a DHCP client on a Palo Alto Networks NGFW, the correct CLI command is set deviceconfig management type dhcp-client. This command configures the management interface to obtain an IP address dynamically using DHCP.

To enable both RADIUS and SAML authentication to run in parallel during the transition period, you need to configure an authentication sequence and an authentication profile that includes both authentication methods.
By creating an authentication sequence that includes both RADIUS and SAML server profiles, the firewall will attempt authentication with RADIUS first and, if that fails, will fall back to SAML. This enables both authentication types to function simultaneously during the transition period.
You can also configure an authentication profile that includes both the RADIUS Server Profile and the SAML Identity Provider server profile. This setup allows the firewall to use both RADIUS and SAML for authentication requests, and it will check both authentication methods in parallel.

To implement post-quantum cryptography (PQC) in VPNs between Palo Alto Networks NGFWs, you would enable the PQ KEM (Post-Quantum Key Encapsulation Mechanism) in the IKE gateway configuration. This enables the firewall to use quantum-resistant encryption for key exchange, which is an essential part of securing communications against the potential future threats posed by quantum computing.
By selecting IKE v2 Preferred and enabling the PQ KEM option under Advanced Options, you can add specific Rounds for the post-quantum cryptography process, which will help in implementing quantum-resistant key exchange methods.
This option similarly selects IKE v2 and enables PQ KEM while also creating a dedicated IKE Crypto Profile with the necessary Rounds configured for post-quantum cryptography.

In this scenario, the customer requires that users do not directly access websites and that a security device (the firewall) manages the connection, while also ensuring that there is authentication back to the Active Directory (AD) servers for all sessions. The explicit proxy with Kerberos authentication is the best solution because:
The explicit proxy allows the firewall to intercept user web traffic and manage the connections on behalf of users.
Kerberos authentication ensures that the user's identity is validated against the Active Directory servers before the session is allowed, fulfilling the authentication requirement.