Private IP Visibility and Enforcement for Explicit Proxy Traffic Originating from Remote Networks
Focus
Focus
What's New in the NetSec Platform

Private IP Visibility and Enforcement for Explicit Proxy Traffic Originating from Remote Networks

Table of Contents

Private IP Visibility and Enforcement for Explicit Proxy Traffic Originating from Remote Networks

Learn how to preserve the source IP address for Explicit Proxy traffic originating from remote networks.
Some organizations require private IP addresses to skip authentication of headless systems that can't authenticate, set up security policies, and get visibility of the traffic on Prisma® Access Explicit Proxy. You can now accomplish these tasks by leveraging the private IP addresses of the systems in your branch locations that are forwarding traffic to Explicit Proxy using Proxy mode. Proxy mode on remote networks helps to secure outbound internet traffic for users and servers in your branches that need PAC-based connection method due to networking or compliance reasons.
You can enable this functionality when you secure users and devices at a branch with a site-to-site IPSec tunnel using Remote Network and Explicit Proxy Secure Processing Nodes (SPNs).