Secure Access - DNS Defense and Internet Security Bypass

Hello, everyone, Welcome to our session today on DNS Defense and internet security bypass. In this quick video, we're gonna walk through how to add internal domains to internet security bypass on Cisco DNS defense.00:04On today's agenda, we will have an overview of the Internet Security Bypass feature in Cisco DNS defense.wheel discuss what this feature does, why it's important, and how it helps ensure reliable access to internal applications. Next, we will move into a demo where we will walk through the step by step process of adding internal domains to DNS defense, and we'll see.00:19How this configuration works in action to prevent disruptions with internal applications.00:39Internet security bypass refers to the configuration on DNS defense admin console that allows certain internet traffic to bypass the secure access DNS inspection. This is typically used for local or internal domains and IPs that should be resolved by your internal DNS server instead of DNS defense public DNS resolvers.00:45This configuration ensures that DNS queries for internal domains are properly resolved by the internal DNS servers, allowing users to access your internal applications and resources seamlessly. Key points for this feature, simplicity. With this feature, you can easily synchronize your bypass list configuration across all DNS forwarders.01:03And roaming devices. This centralizes management and reduces the chance for misconfiguration. Next is visibility. DNS defense still provides complete visibility and security for all external and untrusted destinations ensuring that your organization remains protected where it matters most. Finally, optimization.01:23By bypassing DNS defense for trusted or internal traffic, you avoid unnecessary proxying and improved network performance for your internal applications. Now, let's get started with the demo. 1st, we need to log in into the DNS defense admin console.once logged in.01:40Navigate to connect end user connectivity. Then navigate to internet security and scroll down to traffic steering section. Here, you'll learn how to manage access requests and ensure they bypass secure access when necessary. By default, domains ending in.local and RFC 1000.02:00918 IP addresses are included in the bypass list. Therefore, they are resolved by your internal DNS servers. Click on add destination.02:20This will bring this window where you can add your internal domains. Now, enter the internal domain you want to bypass secure access and be resolved by your internal DNS servers. In this example, we will enter 1st company.com, which is our internal domain. Optionally, we can add a description about the entry and save changes.02:30You can add multiple domains in the list if needed. Once ready, click save. In conclusion of our demonstration, take a look at how the traffic steering table is updated with the new domain. Notice how all devices across all sites are now configured to recognize 1st company.com as an internal domain for direct access.02:49Now, let's go to our testing machine. This testing machine has secure client with the umbrella module to protect the DNS traffic with DNS defense. We try to access a website from the internal domain we added to the bypass list and confirm that is accessible. Also, we can access resources located in external or public domains which will be inspected by DNS.03:10Defense. To corroborate this information, we can check the logs from DNS defense reports. This report is located under monitor reports, activity search. We apply the internal domain as filter and confirm there is not any DNS query received in DNS defense.03:30However, if you use an external domain as a filter, you will see the DNS defense is receiving and inspecting the DNS traffic for that destination. Thank you for watching this video.03:49