Cloud Management

Configure the IP address blocks that

Prisma Access

will use internally to route traffic to the ZTNA Connector and the private apps you onboard.

You must define separate IP address blocks for your connectors and your applications and the blocks cannot overlap with each other, with the Prisma Access infrastructure subnet, or with you GlobalProtect IP address pool.

Select
Settings
Prisma Access
Setup
Shared
and Edit the
Infrastructure Settings
.
If you're using Strata Cloud Manager, go to
Workflows
Prisma Access
Setup
Prisma Access
Infrastructure Settings
.

Add
ZTNA Connectors Application IP Blocks
.
You can add a single Application IP Block, or multiple blocks depending on your deployment. For example, enter 100.64.10.0/24 and 100.64.11.0/24. You can also
Advertise Application IP blocks to Remote Networks
to provide remote network access.
Use RFC 1918 or RFC 6598 addresses. You can specify an RFC 1918 address pool during ZTNA Connector setup instead of RFC 6598; however, you cannot change the address pool type back to RFC 6598 after you specify RFC 1918.
Add
ZTNA Connectors Connector IP Blocks
that
Prisma Access
will use internally to route traffic between mobile users, remote networks and the connector VMs in your data centers.
You can add a single Connector IP Block, or multiple blocks depending on your deployment. For example, enter 100.65.10.0/24 and 100.65.11.0/24.

Click
Save
to save the IP address block configuration and then
Commit
and push the configuration.

Launch ZTNA Connector from the Prisma SASE Platform.

Log in to

Prisma SASE Platform

.

Select

Settings

ZTNA Connector

.



If you're using Strata Cloud Manager, go to

Workflows

ZTNA Connector

.

If you haven't done so already,

Enable ZTNA Connector

.



Prisma Access

begins setting up the infrastructure for the ZTNA Connector. This may take a few minutes.



When onboarding finishes, the ZTNA Connector Overview displays.