Book Image

Securing Remote Access in Palo Alto Networks

By : Tom Piens aka Piens aka 'reaper'
Book Image

Securing Remote Access in Palo Alto Networks

By: Tom Piens aka Piens aka 'reaper'

Overview of this book

This book builds on the content found in Mastering Palo Alto Networks, focusing on the different methods of establishing remote connectivity, automating log actions, and protecting against phishing attacks through user credential detection. Complete with step-by-step instructions, practical examples, and troubleshooting tips, you will gain a solid understanding of how to configure and deploy Palo Alto Networks remote access products. As you advance, you will learn how to design, deploy, and troubleshoot large-scale end-to-end user VPNs. Later, you will explore new features and discover how to incorporate them into your environment. By the end of this Palo Alto Networks book, you will have mastered the skills needed to design and configure SASE-compliant remote connectivity and prevent credential theft with credential detection.
Table of Contents (11 chapters)
1
Section 1: Leveraging the Cloud and Enabling Remote Access
6
Section 2: Tools, Troubleshooting, and Best Practices

Configuring the service connection

In Templates > Network > Network Profiles > IKE Gateways, first, switch the template to Service_Conn_Template, which will ensure the IPSec tunnel is created in the service connection part of the Prisma infrastructure. As we learned in Chapter 2, Configuring Advanced GlobalProtect Features, the IKE gateway is configured based on local and remote parameters.

Important note

The IPSec tunnel configuration is created as a service on the Prisma Access service infrastructure, so the physical firewall connecting to Prisma Access will need its own configuration.

The Prisma Access side interface will receive a static IP address, while the remote service connection can either be a static or dynamic host. In the following screenshot, my service connection is hosted on a dynamic ISP, so Peer IP Address Type is set to Dynamic and is behind a NAT device, and Local Identification and Remote Identification have been set to accommodate this. Follow...