topic Re: HIP distribution into Remote Networks in Prisma Access Discussions

HIP distribution into Remote Networks

sk_display — Wed, 17 Jun 2026 21:48:26 GMT

We have:

* Mobile Users

* Remote Networks

* Internal Gateways

We get Mobile Users userid and hip data by redistributing into the on-prem environment from all three Service Connections.

However, we setup distribution into Remote Networks from the Internal Gateway and TAC said it's not a supported configuration to distribute into Remote Networks, since it introduces a loop.

Is that correct?

Is there a way to prevent Remote Networks from redistributing back to the Service Connections?

For others who use Mobile Users, Remote Networks, and Internal Gateways, how do you redistribute userid/hip appropriately?

Re: HIP distribution into Remote Networks

nikoolayy1 — Sun, 21 Jun 2026 05:01:52 GMT

If TAC itself said it is an issue then in the forum you may not get a better answer. Better try something else in that case.

Maybe Prisma Access can feed this to CIA (Cloud Identity Engine ) and then everything else can get the data from there:

Identify Users and Devices with Cloud Identity Engine

Re: HIP distribution into Remote Networks

nikoolayy1 — Mon, 13 Jul 2026 06:07:24 GMT

As have not given enough information to be honest your case sounds as when users connect to a on-prem Gateway FW that and the connection then does not go through Prisma Access but directly to the DC or remote networks and this seems not possible but maybe with CIA as a central point for User Identification as I mentioned this could work.

Identity Redistribution