- Home
- Prisma Access
- Prisma Access Advanced Deployments
- Prisma Access Remote Network Advanced Deployments
- Provide Secure Inbound Access to Remote Network Locations
- Configure Secure Inbound Access for Remote Network Sites
- Configure Secure Inbound Access for Remote Networks
- Configure Secure Inbound Access for Remote Networks (Strata Cloud Manager)
Prisma Access
Cloud Management
Table of Contents
Expand All
|
Collapse All
Prisma Access Docs
-
- Prisma Access China
- 4.0 & Later
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
-
-
-
- 5.1 Preferred and Innovation
- 5.0 Preferred and Innovation
- 4.2 Preferred
- 4.1 Preferred
- 4.0 Preferred
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
Configure Secure Inbound Access for Remote Networks (Strata Cloud Manager)
Strata Cloud Manager
)Here’s how to make an application accessible from a remote network site to all
internet-connected users (not just
Prisma Access
users).- If you haven’t already, review the inbound access remote network guidelines.
- Gather the application details you’ll need to get started.Make a list of the applications to which you want to provide access, and assign a private IP, port number, and protocol combination for each application. If you use the same IP address for multiple applications, the port/protocol combination must be unique for each application; if you use the same port/protocol combination for multiple applications, each IP address must be unique.
- In Strata Cloud Manager, go to.WorkflowsPrisma AccessSetupRemote NetworksInbound AccessAdd Inbound Access
- Enter the required details.Choose theNumber of Public IPsyou want to use for the applications, either five or ten.Each public IP allocation takes bandwidth from your Remote Networks license, in addition to the license cost for the remote network. 5 IP addresses take 150 MB from your remote network license allocation, and 10 IP addresses take 300 MB.FromPrisma Accessversion 4.1, if you have a resource that is in a remote network site that has inbound access enabled and you want users at non-inbound access sites to have access to that resource, you canAllow inbound flows to other Remote Networks over the Prisma Access backbonewhen you configure the non-inbound access remote network.FromPrisma Accessversion 5.0, you can allow inbound flows to other remote networks over the Service Provider (SP) backbone when you configure the non-inbound access remote network.SP interconnect supports only the following:
- GCP Regions
- NewPrisma Accessdeployments
- Explicit proxy egress traffic
- Add theInbound Access Applicationsfor which you want to secure access.Add the associated private IP / port number / protocol combination for the application.
- Decide how you want to map applications to the public IP addresses.By default,Prisma Accessassigns the public IP addresses to the applications you specify, and multiple applications can be assigned to a single IP address. If you need to map a single application to a single public IP address, you canAssign Dedicated IPduring system configuration. You can configure up to 100 inbound applications for each group of provisioned public IP addresses (either 5 or 10).
- Finish setting up the inbound access remote network as you would a regular remote network site.