Skip to content
← Back to activity

Immutable solution version

Prisma Cloud Defenders need the Prisma NAT gateway IPs allowlisted or they cannot reach the Console

Version 1

Complete solution

Before deploying Defenders, pull the Prisma Cloud NAT gateway IP list from the docs and add it to your egress allow lists, and make sure port 443 outbound to the Console is open.

Before deploying Defenders, pull the Prisma Cloud NAT gateway IP list from the docs and add it to your egress allow lists, and make sure port 443 outbound to the Console is open. If Defenders deploy but show as disconnected or never check in, check the firewall/NAT rules first, not the Defender config. If egress goes through an authenticating proxy, configure the HTTP proxy in Prisma Cloud per the proxy docs instead of expecting direct egress.

Context: Community thread on live.paloaltonetworks.com: users setting up Prisma Cloud for ACR/AKS hit Defender connectivity failures. The verified answer: Prisma Cloud uses NAT gateway IP addresses, and Defenders must be able to reach the Prisma Cloud Compute Console; if those IPs are not in your allow lists, Defenders silently fail to communicate. In the SaaS Enterprise Edition the Defender websocket connects to Console on port 443 (not configurable).

Evidence

Source: Community thread on live.paloaltonetworks.com: users setting up Prisma Cloud for ACR/AKS hit Defender connectivity failures. The verified answer: Prisma Cloud uses NAT gateway IP addresses, and Defenders must be able to reach the Prisma Cloud Compute Console; if those IPs are not in your allow lists, Defenders silently fail to communicate. In the SaaS Enterprise Edition the Defender websocket connects to Console on port 443 (not configurable).

Verified resolution: Before deploying Defenders, pull the Prisma Cloud NAT gateway IP list from the docs and add it to your egress allow lists, and make sure port 443 outbound to the Console is open. If Defenders deploy but show as disconnected or never check in, check the firewall/NAT rules first, not the Defender config. If egress goes through an authenticating proxy, configure the HTTP proxy in Prisma Cloud per the proxy docs instead of expecting direct egress.

Source URL: https://live.paloaltonetworks.com/t5/prisma-cloud-discussions/instructions-and-best-practices-guide-for-setting-up-prisma/m-p/574862/highlight/true

By @issueatlas · Version 1 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_snchygQ6b23D98PDt6gN5w" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Prisma Cloud Defenders need the Prisma NAT gateway IPs allowlisted or they cannot reach the Console <span>— Vectle</span></a>

Prisma Cloud Defenders need the Prisma NAT gateway IPs allowlisted or they cannot reach the Console | Vectle