Cisco Umbrella SIG Upgrade Guide to Cisco Secure Access

PDF

Cisco Umbrella SIG Upgrade Guide to Cisco Secure Access

Getting Started with Internet Access Rules

Want to summarize with AI?

Log in

Umbrella DNS policies, Web policy, and Firewall policy are now Secure Access internet access rules. An internet access rule can now be enforced at the DNS layer, web proxy layer, and firewall layer.


The conversion to Secure Access internet access rules unifies policies from Umbrella DNS, Web, and firewall-significantly expanding their enforcement. Now, these consolidated rules can be applied across the DNS, web proxy, and firewall layers, offering more comprehensive control.

This upgrade introduces a fundamental change in policy structure, unlike Umbrella where a single policy or rule could contain multiple block and allow components, Secure Access employs a single Access policy model where each individual rule is configured exclusively to either block or allow traffic.

Note
Secure Access uses a unified policy model where rule order determines traffic precedence. Review and test your rules thoroughly before manually reordering them, as moving a rule can change how traffic is handled and may inadvertently allow traffic that was previously blocked.

The order of rules on the Policy page is crucial for how traffic is managed. Traffic is processed by the first rule in the list that matches, and any rules below that matched rule have no effect on that traffic. It is important to arrange your rules so that more specific rules are placed above more general rules. Essential rules, such as those blocking access to sites you want to restrict for all users, should be positioned at the top. If no rule matches the traffic, Secure Access applies the default access rule for the traffic type (internet or private access), located at the bottom of the Access policy page.

Misconfigurations can lead to unintended events, such as unprotected resources or users accessing blocked destinations, so careful planning and design of your rules before implementation is essential. Test your rules by creating a new identity in Umbrella and redirecting the traffic to Secure Access. Follow these steps to Redirect Umbrella Traffic to Secure Access Sources.

Migration order

During the transition, Umbrella DNS, Web, and Firewall policies are transformed into multiple rules in Secure Access, similar to this order depending on how you selected your policies to copy into Secure Access:

  1. Umbrella Web Policy sourced rules.

  2. Umbrella Web Default Policy sourced rule.

  3. Umbrella DNS Policy sourced rules.

  4. Umbrella DNS Default Policy sourced rule.

  5. Umbrella Firewall Policy sourced rules.

  6. Umbrella Firewall Default Policy sourced rule.

For more information, see our Cisco Secure Access guidebook on Get Started With Internet Access Rules and Manage the Access Policy.

Table 1. Policy Components Mapping
Umbrella Policy Components Secure Access Internet Access Rules
Policies Access Policy
DNS policies Internet Access Rules
Web policy Internet Access Rules
Firewall policy Internet Access Rules
Application Settings Application List
Block Page Appearance Notification Page
Content Categories Content Categories
Destination Lists Destination Lists
Identities Sources
Mobile Device and Roaming Computer Roaming Device
Security Settings Threat Categories
Selective Decryption Do Not Decrypt List

Umbrella DNS Policies to Internet Access Rules: What You Need to Know

After the upgrade, an Umbrella DNS policy can be split into multiple internet access rules in Secure Access. The policy is split in this specific order:

  1. Allow Rule (Primary): The first rule is an allow rule that permits traffic as specified in the original Umbrella policy.

  2. Block Rule (Secondary): The second rule is a block rule that enforces restrictions on traffic as defined in the original Umbrella policy.

  3. Allow Rule (Default): A third rule may be introduced as an implicit allow rule to ensure policy evaluation is consistent with Umbrella's policy model. This rule accounts for scenarios where no explicit match is found for a destination and prevents unintended traffic disruptions.

    • Does not terminate rule evaluation on the enforcement side, enabling further analysis of traffic.

    • Allows general access to safe and non-malicious websites by default. Websites are permitted unless explicitly flagged as malicious by Cisco's threat intelligence.

    • The default rule applies to all sources from the original Umbrella policy until custom rules are configured.

    • Destinations are set to Any.

    How the Default Rule Operates:

    • If the Allow rule (Default) is matched, no rules beyond it will be evaluated during the same query cycle.

    • However, the rule allows subsequent evaluations for the same query under specific circumstances, such as: When analyzing CNAME records and after retrieving resolved IP addresses from DNS resolution.

    Note

    The sources remain the same in these newly separated rules.

Umbrella DNS Policy upgraded to Secure Access Rules

Example: An Umbrella policy named, New Policy has AD Groups, AD Users, AD Computers as identities, Content Category blocks all adult related websites and illegal activity, and Application Settings allows Box Cloud Storage.

Umbrella policy appears in Secure Access' Access Policy:

  1. 1st rule's name, 3/3 (DNS) New Policy. Sources: AD Groups, AD Users, AD Computers. Allow Application List: Box Cloud Storage.

  2. 2nd rule's name is 2/3 (DNS) New Policy. Sources: AD Groups, AD Users, AD Computers. Block Content Category List: all adult related websites and illegal activity.

  3. 3rd rule's name is 1/3 (DNS) New Policy Default. Sources: AD Groups, AD Users, AD Computers. Allow destinations: Any.


    This screenshot shows an Umbrella DNS policy splitting into three internet access rules in Secure Access.

For more information on creating new internet access rules, see our Cisco Secure Access Help guidebook on Get Started With Internet Access Rules and Manage the Access Policy.


Umbrella Firewall Policy to Internet Access Rules: What You Need to Know

When you upgrade from Umbrella to Secure Access, your existing firewall rules become internet access rules. Internet access rules can be enforced by DNS, Web, and firewall layers. This change brings several important differences you need to know to ensure your rules continue to protect your network effectively.

What’s changing:

  1. Firewall rule name change: We add a prefix, (Firewall) to your rule name to help you easily identify it among the other rules in Secure Access. You can edit or remove the name once you close your Umbrella account.

  2. Bulk Firewall Rule Actions: Umbrella supports bulk actions for firewall rules, but this capability is not available in Secure Access. You must manage internet access rules individually after migration.

  3. Firewall Rule Schedule Translation: When migrating firewall rules, Secure Access translates the schedule to apply the start and end times to every day within the specified period. This differs from Umbrella, where start and end times apply only to the first and last days of the period. As a result, the migrated rule may be active for a broader duration than originally intended.

  4. Firewall Rules May Be Split into Multiple Internet Access Rules: Firewall rules containing applications may be divided into separate internet access rules based on two distinct destinations:

    • Application Protocols refers to the specific communication rules and standards used by software to exchange data over a network, such as HTTP or FTP.

    • Internet Applications are the actual software programs or services (YouTube or Facebook) that use these protocols to provide functionality to users.

  5. Internal Networks and Tunnel Identity Differences:

    • In Umbrella, Firewall rules support internal networks by allowing the selection of All Tunnels as a source. Policies can apply broadly to all network tunnels without specifying each tunnel individually.

    • In Secure Access, the All Tunnels identity is not supported as a single entity. Instead, the equivalent rule criteria is expressed as a logical AND operator by combining:

      • Network Objects or inline source IP (such as CIDR IP addresses representing internal networks) AND

      • Network Tunnel Groups (select Any Network Tunnel Groups).

      Example: The source criteria in Secure Access would be represented as CIDR IP addresses AND Any Network Tunnel Groups.

  6. Changes to Destinations in Internet Access Rules: In Umbrella, the destinations field can include IP addresses, ports, Application Protocols, and Internet Applications.

    In Secure Access, the use of logical AND for destinations is only supported for certain destination types.

    • Logical AND for destinations allows these combinations: Application Protocol, Network Object, and Service Object.

    • Logical AND is not supported for Internet Applications. When configuring internet access rules, you can combine Network Objects AND Service Objects, but you cannot AND Internet Applications.

  7. Umbrella Network Tunnels Become Network Tunnel Groups:

    • Tunnel ID and passphrases change.

    • You must configure and manage network tunnel groups by setting up primary and secondary hubs, and authentication.

    • For detailed steps and guidance, refer to the Cisco Umbrella SIG Upgrade Guide to Cisco Secure Access on, Upgrade to Network Tunnel Groups.

    • In the Secure Access Help guidebook learn more on how to Manage Network Tunnel Groups.

  8. IPS Signature List Renamed to IPS Profile: IPS Signature List is now called IPS Profile. Find and manage these profiles under Secure > Profiles > IPS Profiles.

Umbrella Firewall Policy as Internet Access Rules in Secure Access

Example: An Umbrella firewall rule named, Company Block App Rule, is configured to block Application Protocol for DNS and block Internet Application for all E-Commerce. The identities are Network Tunnel New York and IP address: 209.165.201.1.

The Umbrella firewall rule is copied to Secure Access and becomes two internet access rules:

  1. First rule’s name is: 1/2 (Firewall) Company Block App Rule – Application Protocols.

    • This rule is configured to block Application Protocol for DNS.

    • The sources are Network Tunnel New York and IP address: 209.165.201.1.

  2. Second rule’s name is: 2/2 (Firewall) Company Block App Rule – Internet Applications.

    • This rule is configured to block Internet Application for all E-Commerce.

    • The sources are Network Tunnel New York and IP address: 209.165.201.1.


Umbrella Web Policy to Internet Access Rules: What You Need to Know

In Umbrella, the Web Policy, is made up of rulesets and rules that set various security, permission, and access controls for your identities. A ruleset may contain a rule with a block action and a second rule with a warn action. In Secure Access, this ruleset is separated into multiple rules depending on the type of rule actions and the valid compatibility of sources.

Umbrella Web Policy as Internet Access Rules in Secure Access

Example: An Umbrella Web ruleset named, Company Ruleset has two rules. Each rule has the same identities: G Suite Users, G Suite OUs, and Chromebooks. Rule 1: blocks all adult related websites and illegal activity listed in Content Category. Rule 2: warns users when accessing any Social Networking websites listed in Application Settings.

Umbrella's Web rule in Secure Access' Access Policy:

  1. 1st rule's name, 1/3 (Web) Rule 2 - Company Ruleset. Sources: G Suite Users, G Suite OUs, and Chromebooks. Block all adult related websites and illegal activity listed in Content Category.

  2. 2nd rule's name, 2/3 (Web) Rule 1 - Company Ruleset. Sources: G Suite Users, G Suite OUs, and Chromebooks. Warns users when accessing Social Networking websites listed in Application Settings.

  3. 3rd rule's name, 3/3 (Web) Default allow - Company Ruleset. Sources: G Suite Users, G Suite OUs, and Chromebooks. Destinations set to Allow Any. The default rule allows general access to non-malicious and safe websites. By default, most websites are allowed unless they are explicitly flagged as malicious by Cisco's threat intelligence. This new rule applies to the sources from the separated ruleset and destination is set to Any. This default rule is added to ensure your policy continues to work like it did in Umbrella. It covers situations where none of your specific rules, within the ruleset, match a destination. Without this rule, some user traffic might be blocked unexpectedly. Instead, when no explicit rule applies, traffic from matching sources will still be allowed—just like in your previous Umbrella Web policy.


Umbrella Web Policy as Internet Access Rules in Secure Access.

Data Loss Prevention Policy: What You Need to Know

When you upgrade to Secure Access, it is important to understand how your Data Loss Prevention (DLP) policy is handled while the Upgrade Manager is active.

Shared DLP Policy: Unlike DNS, Web, and Firewall policies where Umbrella and Secure Access each keep their own separate copies, your DLP policy is shared between both products. This means there is a single DLP policy that applies to both Umbrella and Secure Access.

Impact of Changes: Since the DLP policy is shared, any changes you make to the DLP policy on either Umbrella or Secure Access will immediately affect enforcement on both products. All DLP rule updates are synchronized and will impact both products.

Policy Translation and Network Tunnel Groups: During the upgrade, the translation process attaches Network Tunnel Groups only to Umbrella DLP rules that had network tunnels configured. This ensures that your network tunnels continue to be managed properly within the DLP rules.

In summary, when you upgrade, remember that while DNS, Web, and Firewall policies operate independently on Umbrella and Secure Access, your DLP policy is unified and shared. Therefore, any updates you make to DLP rules on one product will be reflected on the other, and network tunnel groups are linked only to those Umbrella DLP rules with existing network tunnels.

See our Secure Access Help guidebook for more information on how to Manage the Data Loss Prevention Policy.


Converting Ruleset and Rule Identities to Secure Access Sources

In Umbrella’s Web policy, ruleset identities are configured followed by rule identities. The Umbrella rules match only when the ruleset identity and the rule identity match for a transaction.

Secure Access does not have rulesets. To achieve the same behavior in Secure Access, Umbrella’s rulesets and rules are converted into internet access rules, and the two identities are combined with the logical AND operator.

Navigate to our Cisco Secure Access Help guidebook for more information on, Using Network Objects for Sources in Access Rules.