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

Troubleshooting NAT

NAT is commonly applied when address space is running out or to hide internal address space. There are many ways to apply NAT, but this can bring about some challenges. In this section, we'll cover some useful commands and special use cases.

In my lab, I have set up the following NAT rules:

Figure 7.14 – Lab NAT rules

The following command shows which NAT rules are active on the data plane and in which order they are installed. You will notice inbound 1 is missing. This is because it is disabled, so it is not installed on the data plane:

reaper@LABFW> show running nat-policy
"hide-nat; index: 1" {
        nat-type ipv4;
        from [ trust lab ];
        source any;
        to untrust;
        to-interface ethernet1...