Cisco Umbrella SIG Upgrade Guide to Cisco Secure Access

PDF

Cisco Umbrella SIG Upgrade Guide to Cisco Secure Access

Overview to Start Upgrade

This step creates a new Secure Access organization and transfers over your Umbrella configurations.


In this step, you are creating a Secure Access account, and your existing Umbrella DNS, Web, and Firewall policies are unified into a single set of internet access rules within the Access Policy.

Your Data Loss Prevention (DLP) policy is copied to Secure Access and is not merged into the Access Policy. DLP policy retains its original configuration, and enforcement continues independently from the internet access rules. While your Upgrade Manager is active, your DLP policy is shared between Umbrella and Secure Access. Any changes made in one product will affect the other until you permanently close your Umbrella account.

Internet Access Rules

This integration eliminates the previous distinction between DNS, Web, and Firewall policies, as each new Internet Access Rule can comprehensively manage both DNS-layer, web-layer, and Firewall traffic components.

For example, while traditional Umbrella required creating separate DNS, Web, and Firewall policy rules to block a specific application like social media, Secure Access achieves this with a single, unified internet access rule.

This streamlined "single pane of glass" approach significantly reduces complexity, enhances operational efficiency by eliminating duplicate configurations, and provides a more robust, easier-to-manage security posture.

Umbrella DNS Policies become Secure Access internet access rules.

Umbrella Web Policy becomes Secure Access internet access rules.

Umbrella Firewall Policy becomes Secure Access internet access rules.

Umbrella DNS policies + Web Policy = Secure Access internet access rules.

Umbrella DNS policies + Web Policy + Firewall Policy = Secure Access internet access rule

Start Upgrade: After completing the prerequisites, the next step is to Start Upgrade. This step creates a new Secure Access organization and transforms your existing Umbrella DNS policies, Web policy, Firewall policy, and configurations into the Secure Access dashboard.

Continuous Protection: Umbrella continues to operate and protect your organization during the upgrade.

Simplified Policy Management: The traditional Umbrella DNS policies, Web policy, and Firewall policy are configured separately. Secure Access consolidates all your internet access rules into one Access Policy. There is no distinction between DNS policies, Web policy, and Firewall policy—just one set of internet access rules that combine all policy components.

Review and Reorder Rules: After the upgrade, your Umbrella DNS, Web, and Firewall policies are converted into internet access rules. Depending on the original configuration, a single Umbrella policy or rule might be split into multiple internet access rules.

You must review your rules in Secure Access to confirm they align with your security goals. Secure Access enforces the first matching rule in the policy list-meaning rules at the top take precedence over those below-reordering your rules may be required. Properly order your rules to ensure your intended protections and access controls are maintained.

Note

Minimize changes in Umbrella during the upgrade process. While it is possible to make changes, please be aware that not all changes will reflect in Secure Access post upgrade. To ensure a smooth transition and consistent security enforcement, it’s best to limit changes during this period.

Why Order Matters

  • When network traffic (like your internet request or an attempt to access an internal server) comes into a system with an access policy, the system evaluates the traffic against the rules in the order they are listed, from top to bottom.

  • The first rule that matches the characteristics of the traffic is applied.

  • Once a match is found and an action (allow or deny) is taken, the system stops processing further rules for that specific piece of traffic.

  • This means if you have a very broad "allow" rule at the top of your list, it might accidentally permit traffic that a more specific "deny" rule further down the list was intended to block. Conversely, a broad "deny" rule at the top could block legitimate traffic that a more specific "allow" rule was supposed to permit.