Configure Secure Inbound Access for Remote Networks (Strata Cloud Manager)
Focus
Focus
Prisma Access

Cloud Management

Table of Contents


Configure Secure Inbound Access for Remote Networks (
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).
  1. If you haven’t already, review the inbound access remote network guidelines.
  2. 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.
  3. In Strata Cloud Manager, go to
    Workflows
    Prisma Access
    Setup
    Remote Networks
    Inbound Access
    Add Inbound Access
    .
  4. Enter the required details.
    Choose the
    Number of Public IPs
    you 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.
    From
    Prisma Access
    version 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 can
    Allow inbound flows to other Remote Networks over the Prisma Access backbone
    when you configure the non-inbound access remote network.
    From
    Prisma Access
    version 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
    • New
      Prisma Access
      deployments
    • Explicit proxy egress traffic
  5. Add the
    Inbound Access Applications
    for which you want to secure access.
    Add the associated private IP / port number / protocol combination for the application.
  6. Decide how you want to map applications to the public IP addresses.
    By default,
    Prisma Access
    assigns 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 can
    Assign Dedicated IP
    during system configuration. You can configure up to 100 inbound applications for each group of provisioned public IP addresses (either 5 or 10).
  7. Finish setting up the inbound access remote network as you would a regular remote network site.


Recommended For You