Introduces get started with private access rules. Private access rules control and secure access to internal resources and applications that are private and should not be accessed by the general public.
Private access rules control and secure access to internal resources and applications that are private and should not be accessed by the general public.
Traffic to private destinations is blocked by default. You must create rules to allow traffic to private destinations.
-
Plan your private access rule
Plan your rule so that you get the results you expect. For example, factors such as rule order impact traffic handling.
-
Create rule components.
You will assemble rules largely from components, including but not limited to source, destination, endpoint posture, and security control components. For more information, see Components for Private Access Rules.
-
Specify rule defaults.
New rules will use the default security controls and other settings that you specify on the Rule Defaults page. For more information, see Default Settings for Private Access Rules.
-
Add private access rules
Generally, you will create rules to allow access to private resources. For more information, see Add a Private Access Rule.
-
Configure logging for the default private access rule
Traffic to private destinations that does not match any other private access rule in the policy will be handled by the default private access rule. Traffic that matches this rule is blocked. For more information, see Edit the Default Access Rules.
-
Edit the global settings
For more information, see Global Settings for Private Access Rules.
-
Review the rule order
Make sure the order of the rules on the Policy page will have the results you expect. For more information, see Edit the Order of the Rules on the Policy Page.
-
Distribute dummy access URLs to end users
For rules allowing access to private resources using browser-based connections, distribute the remotely accessible dummy URL to the users who will use it to connect to the resource. You configure a URL for each resource when configuring the resource. For more information, see Add a Private Resource.
Users who are not allowed access may see a Block page
Users that attempt to access a configured private resource will see a Block page if all of the following are true:
The user's access is blocked by a Block rule, including by the default private access rule.
The user's device has the Cisco Secure Client installed.
Decryption is enabled on the private resource configuration page.
VPN connections are not enabled on the private resource configuration page.
Zero Trust connections are enabled for the resource.
You cannot customize this block page, and this block page is NOT the same block page that users see when they attempt to access a blocked internet destination.
Components for Private Access Rules
Describes components for private access rules. You can create access rules by adding rule components that you or others have configured to a rule. Components described in this topic are reusable. You can use the same component (such as a source) in multiple rules, speeding and simplifying rule creation.
Default Settings for Private Access Rules
Describes default settings for private access rules. You can choose default settings that will automatically populate newly created access rules by default.
Add a Private Access Rule
Describes adding a private access rule. Cisco Secure Access connects users, devices, both public and branch networks, and network tunnels to private resources in your enterprise. Private resources are applications and services that you deploy on your enterprise's infrastructure or private cloud.
About Configuring Sources in Private Access Rules
Describes about configuring sources in private access rules. Let the following information guide you when you add sources to a private access rule. Source Components Sources created directly in Private Access Rules If there are multiple sources in a rule (Boolean logic)
About Configuring Destinations in Private Access Rules
Describes about configuring destinations in private access rules. Let the following information guide you when you add destinations to a private access rule. Destination components for private access rules Destinations created directly in a private access rule If there are multiple destinations in a rule (Boolean logic)
About Endpoint Requirements in Access Rules
Describes about endpoint requirements in access rules. If endpoints do not meet the requirements specified in posture profiles, traffic is handled differently for zero trust connections and VPN connections:
Allowing Traffic from Users and Devices on the Network
Describes allowing traffic from users and devices on the network. In addition to creating access rules for remote users accessing private resources, you must create rules to allow traffic from users and devices on the network, including those in branch offices.
Global Settings for Private Access Rules
Describes global settings for private access rules. Global settings generally apply to all rules. However, some settings apply only to internet access rules, not to private access rules.
Troubleshoot Private Access Rules
Describes troubleshooting private access rules. To troubleshoot private access rules: Problems while creating the rule Problems after creating a rule