Security Policy for Apps Enabled with ZTNA Connector

Table of Contents

Onboard the ZTNA Connector VM in Your Data Center

ZTNA Connector seamlessly extends your existing Prisma Access security policy to the applications it enables for Prisma Access.

Where Can I Use This?	What Do I Need?
Prisma Access (Managed by Strata Cloud Manager) Prisma Access (Managed by Panorama)	Prisma Access 4.0 ZTNA Connector add-on license The Essential license with the add-on license includes 8 ZTNA Connectors, 100 FQDNs, and 4 IP subnet functionality. The Advanced license with the add-on license includes 40 ZTNA Connectors, 300 FQDNs, and 1024 IP subnet functionality. The Premium license with the add-on license includes 200 ZTNA Connectors, 4000 FQDNs, and 1024 IP subnet functionality. If you don't purchase the ZTNA Connector add-on license, Prisma Access licenses include four connectors, 40 FQDNs, and four IP subnets. This functionality is provided for the purpose of trying out ZTNA Connectors in your environment.

ZTNA Connector does not enforce policy; it seamlessly extends your existing Prisma Access security policy to the applications it enables for Prisma Access. This means you can use a common policy across all your applications and data centers, and you don't need to author your security policy separately for apps onboarded to ZTNA Connector.

However, as part of setting up ZTNA Connector, you do need to make sure that your security policy:

Allows traffic between Prisma Access and ZTNA Connector

For this, follow the ZTNA Connector Requirements and Guidelines to make sure that ZTNA Connector can connect to Prisma Access.

Users can access the applications behind the ZTNA Connector

To ensure your users can access ZTNA Connector apps, follow the steps here for the interface you're using to manage Prisma Access.

Strata Cloud Manager
Panorama

Security Policy for Apps Enabled with ZTNA Connector (Strata Cloud Manager)

Set up a Security policy rule that enables users to access apps behind ZTNA Connector for Cloud Managed Prisma Access deployments and Strata Cloud Manager.

After you onboard apps to ZTNA Connector, you should set up policy rules to allow and control access for those apps. The procedure to create and apply policy differs on whether your apps are defined by

wildcards

IP Subnets

, or

FQDNs

Security Policy for Wildcard-Based Apps

Wilcard-based apps ( (SettingsZTNA ConnectorApplication TargetsWildcard Targets) require that you create a custom URL category; however, that type of category only enforces policy for HTTP and HTTPS traffic, and other traffic (such as SSH) isn't allowed. For this reason, you need to temporarily allow access to all apps by allowing traffic to the ZTNA Connector Application IP blocks.

After ZTNA Connector learns the FQDNs that are based on the wildcards, you can disable the policy that allows Application IP Block traffic and apply policy enforcement based on the learned FQDNs.

Create a Custom URL category and add the wildcard URLs to the category.
1. Go toManageConfigurationNGFW and Prisma AccessSecurity ServicesURL Access Management.
2. Under Custom URL categories, Add Category.
3. Give a descriptive Name for the custom URL category and select a Type of URL List.
4. Add the wildcard URLs you created in ZTNA Connector to the Items.
5. Save your changes.
Create a URL access Management Profile and add the custom URL category you created to it.
1. While still in the URL Access Management area, select URL Access Management Profiles.
2. Select an existing profile to modify or Add Profile.
3. Add the Custom URL category you created to the profile.
4. Select the following parameters:
  Site Access: Allow
  User Credential Submission: Allow
5. Save your changes.
Create a profile group and attach the URL Access Management Profile to the group.
1. Go to ConfigurationNGFW and Prisma AccessSecurity ServicesProfile Groups.
2. Add a profile group, specifying the URL Access Management Profile you created.
Create a policy to allow the profile group and the IP addresses for the ZTNA Connector Application IP Blocks.
1. Go to WorkflowsPrisma Access SetupPrisma AccessPrisma Access Setup and make a note of the Application IP Blocks under ZTNA Connector IPs.
2. Go to ManageConfigurationNGFW and Prisma AccessObjectsAddressAddresses and Add address objects based on the IP addresses you retrieved.
  
  If you have IP Subnet-based apps, create address objects for those subnets as well.
3. Go to ManageConfigurationNGFW and Prisma AccessObjectsAddressAddress Groups and Add the address objects you created to an address group.
4. Go to ManageConfigurationNGFW and Prisma AccessSecurity ServicesSecurity PolicyPre Rules and Add a Security policy to allow access to all application IP address blocks, specifying the Address Group and Profile Group you created in an earlier step.
  
  Adding this Security policy allows all traffic from wildcard-based app traffic to be passed while ZTNA Connector discovers the apps based on wildcards. Without the rule to allow the Application IP Blocks, users can't access wildcard-based apps.
  
  You can leave this policy in place until ZTNA Connector discovers the wildcard-based apps. Then, you can choose to disable this policy and add Security policy rules for each of the discovered apps.
After ZTNA Connector has discovered the apps based on wildcards, configure a Security policy for the apps that you added using FQDNs.
1. Go to WorkflowsZTNA ConnectorApplication TargetsFQDN Targets and make a note of the FQDNs used by the apps.
2. Create an Address object for the FQDN (ManageConfigurationNGFW and Prisma AccessObjectsAddressAddresses).
  
  Select the Prisma Access configuration scope.
3. Add an address object with the Type of FQDN: Domain Name and enter the FQDN of the discovered application.
  
  Enter the FQDNs for the FQDN targets.
4. Go to ManageConfigurationNGFW and Prisma AccessSecurity ServicesSecurity PolicyPre Rules and Add a Security policy to allow access to the discovered apps.
Push Config to save and push your configuration changes.
(Optional) After you have created the Security policy based on FQDNs, remove the policy based on the IP application blocks.

Security Policy for IP Subnet-Based Apps

If you created ZTNA Connector application targets based on IP subnets (SettingsZTNA ConnectorConnectorsApplication TargetsIP Subnets), complete the following steps to allow access to the apps.

Go to WorkflowsZTNA ConnectorApplication TargetsIP Subnets and make a note of the IP subnets used by the apps.
Create a policy to allow the IP addresses for the IP subnets used for the apps.
1. Go to ManageConfigurationNGFW and Prisma AccessObjectsAddressAddresses and Add address objects based on the IP addresses you retrieved.
2. Go to ManageConfigurationNGFW and Prisma AccessObjectsAddressAddress Groups and Add the addresses you created to the address groups.
3. Go to ManageConfigurationNGFW and Prisma AccessSecurity ServicesSecurity PolicyPre Rules and Add a Security policy to allow access to the IP subnets for the apps, specifying the Addresses you created in an earlier step.
Push Config to save and push your configuration changes.

Security Policy for FQDN-Based Apps

If you have added targets based on FQDNs (SettingsZTNA ConnectorConnectorsApplication TargetsFQDN Targets), create an address object and a Security policy to allow access to the apps by completing the following steps.

Configure a Security policy for the apps that you added using FQDNs.
1. Go to WorkflowsZTNA ConnectorApplication TargetsFQDN Targets and make a note of the FQDNs used by the apps.
2. Create an Address object for the FQDN (ManageConfigurationNGFW and Prisma AccessObjectsAddressAddresses).
  
  Select the Prisma Access configuration scope.
3. Add an address object with the Type of FQDN: Domain Name and enter the FQDN of the discovered application.
  
  Enter the FQDNs for all discovered apps.
4. Optional Go to ManageConfigurationNGFW and Prisma AccessSecurity ServicesSecurity PolicyPre Rules and Add a Security policy to allow access to the discovered apps.
Push Config to save and push your configuration changes.