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 infrastructure

The first thing that needs to be configured is the service infrastructure, as illustrated in the following screenshot. This is essentially the virtual network "inside" Prisma Access that serves as the backbone between remote networks, service connections, GlobalProtect users, and the internet. This needs to exist before any other component can be configured and needs a subnet that does not overlap anywhere else in the company.

On the Service Setup menu item, click the cog wheel to configure the service infrastructure.

In the General tab, do the following:

  • Provide an infrastructure subnet that does not overlap with any internal networks. Choose wisely because once this network has been configured, it can't be changed.
  • A Border Gateway Protocol Autonomous System (BGP AS) is present and can be changed if an internal BGP is used for enterprise-wide routing. If no dynamic routing is used, the BGP AS can remain unchanged...