Using Access Policies - Configuring-NetCloud-Exchange-Secure-Connect/Using-Access-Policies

Secure Connect Configuration Guide

ft:locale
en-US
ft:sourceName
Paligo_Prod
Document Type
Configuration Guide

By default, Secure Connect allows outbound internet traffic from a site but does not allow site-to-site traffic. A network administrator must create access policies to allow site-to-site traffic and access between sites and resources (for example, site to Internal Resources).

With NetCloud OS 7.26.20, access policies may be created using any combination of certain AND criteria in the source and destination. Certain OR criteria may also be used in the destination. If no source or destination criteria is selected, it is treated as ANY in the resulting access policy.

Note

If downgrading to a previous version of NetCloud OS after upgrading to 7.26.20, access policies revert to the set of policies saved prior to the upgrade and any access policies created after upgrading to version 7.26.20 are deleted.

Access policies may be created using any combination of the following for the source of a policy:

  • Site names

  • Tags that were assigned to network sites, site groups, or resources

  • IP subnet addresses

  • SAML attributes, if Zero Trust Network Access is licensed

  • Local area networks (LANs) located behind a Secure Connect site router, as defined in the router or group configuration (Networking > Local Networks > Local IP Networks).

Access policies may be created using any combination of the following for the destination of policy:

  • Site names

  • Tags that were assigned to network sites, site groups, or resources

  • Site subnet IP addresses, fully qualified domain name (FQDN), and wildcard FQDN

  • Resource names

  • Web categories, web groups, and web reputation, if Hybrid Mesh Firewall is licensed

  • An application and application categories, if Hybrid Mesh Firewall is licensed

  • Geolocations, if Hybrid Mesh Firewall is licensed

Policies are evaluated in a top-down order. The first policy that matches is applied to the traffic and no further policies are evaluated.

Note

There is a limit of 20 each for sources and destinations per access policy.