Secure Access - Private Resources

Welcome to today's session on Cisco Secure Access, where we are focusing on private resources. In this session, we'll break down the definition of a private resource and demonstrate how they are integrated into access policy rules to allow your users secure connectivity to those internal assets.00:04In today's agenda, we are providing an overview of private resources, discussing what they entail and their significance for your organization. Second, we will conduct a demonstration to illustrate the practical application of these concepts. Private resources refer to internal assets such as applications, servers, networks or sub.00:22Internets managed by your organization. These resources are not publicly accessible over the internet. By designating them as private resources in Cisco Secure Access, you integrate them into a unified cloud based security framework that allows them to be accessed via various secure private access solutions, including client based ZTA, clientless ZTA.00:42Branch to branch connectivity or VPN as a service.01:02The key aspects include. Simplicity. Administrators can define resources once and reuse them across multiple access policies, minimizing the need for redundant configurations. Efficiency. This system streamlines deployment by simplifying complex network setups, allowing IT to rapidly scale access to new applications without reconfiguration.01:05We're now going to delve into a demonstration of how these concepts are applied in practice. This demo will showcase the integration of private resources within Cisco Secure Access. To begin setting up private resources, in the portal, navigate to resources and click on private resources.01:27Here we click on add a private resource. In this step, we configure the essential details for your private resource. Start by entering a descriptive name and an optional description. Next, define the application's FQDN or IP address along with a specific protocol and port. If you use an FQDN.01:47Ensure you select the appropriate DNS server capable of resolving that address.02:07You can manage your DNS server configurations at any time under resources DNS servers. Select the appropriate connectivity method to determine how users reach this resource. Configuration options include branch to branch, client based zero trust, browser based zero trust, and VPN connections. For this demonstration.02:12We will focus on enabling access via client based zero trust. Finally, click save to complete the configuration.02:32Once you have added your private resource, the next step is to configure access policy rules. These rules determine whether selected users are granted or denied access to your private resources. Navigate to secure access policy. Here, you will add rules to the access policy. Defining access control rules ensures that only.02:40Authorized users can connect to the organization's private resources enhancing overall security.03:00This rule illustrates the process of granting access to a specific AD group for our IT web server. We begin by specifying the rules name, allow access to IT web server, which helps us identify it easily within the portal. Next, we set the action to allow, meaning traffic is permitted only when specific security requirements are met. We then link the rules.03:07To a specific AD group ensuring access is restricted to authorized users.03:27Finally, we set the destination to our private resource, web server, ensuring only the designated server is reachable. These configurations provide a secure, granular method to control access to vital network assets. Remember, precise rule configuration is fundamental to maintaining a strong security posture while enabling seamless access to essential resource.03:32Sources.03:52Here we can see the access policy rule we just created. The rule specifies an AD group as the source and allows traffic toward our private resource, web server. Additionally, you can observe the default rules below. These define our baseline security posture, blocking access to all private destinations by default while allowing standard internet access. This structure.03:55For ensures that your private resources remain shielded and access is only granted through a specific authorized rules like the one we just created.04:15This configuration is essential for enforcing a strong security policy. It provides precise control over who can reach which internal assets effectively balancing granular security with operational efficiency. Thank you for watching.04:22