What's Next
- Test the connection between Secure Access and your private resources. See Test Private Resource Reachability.
- (Optional) If you entered a FQDN of the format *.example.com and you want to exclude subdomains from the ability to connect to this resource, add exceptions to the Traffic Steering page. See Using Wildcards to Configure Traffic Steering for Private Destinations.
- (Optional) You can exclude subdomains from this Private Resource configuration and then add one or more separate Private Resources and access rules to allow different access for those subdomains.
- Configure requirements that you want to apply to this resource, such as endpoint requirements (using posture profiles) and intrusion prevention (IPS profiles). See Components for Private Access Rules.
- After you have configured other requirements, add policy rules to access this resource.
-
Add private access rules to allow users and devices to access this resource. See Get Started With Private Access Rules to add private acess rules.
-
See Add a Real Time Rule to the Data Loss Prevention Policy to allow DLP real-time rules to scan for violations in upload, download, or both upload and download traffic.
An access policy rule targeting “any” for private destination will not pass traffic to Data Loss Prevention rules for evaluation. Secure Access will forward private traffic to the Data Loss Prevention engine only if an access policy rule matching that traffic specifies private resources or private resource groups for the destination. -
- When you are ready for end-users to access the resource, if you have enabled browser-based access, give your users the dummy URL that you configured in this procedure.