Skip to content
Shield

Decision guideDNS filtering alternatives

Cisco Umbrella pricing: how it is structured and what to model

Decide whether per-user licensing or network-scoped protective DNS fits your venues. You can test a Cisco Umbrella quote against your real staff, guest and visitor counts, model every cost line for both options, and know when to pair a roaming agent on managed laptops with Purple Shield on each SSID, VLAN and venue.

12 min read

Cisco Umbrella pricing: how it is structured and what to model

Watch the explainer

Per-user licensing is typically structured for managed laptops where every user can be named in advance. Network-scoped protective DNS protects venue WiFi serving uncounted guests. Cisco Umbrella pricing is typically quoted per user. Purple Shield applies a policy per SSID, VLAN and venue, and Purple runs WiFi at 80,000+ venues in 90 countries.

When does per-user Umbrella pricing fit a venue?

The rule of thumb: license per head where heads are stable, and scope policy to the network where they are not.

Start with placement. DNS filtering acts at the lookup, before a device opens any connection. A firewall inspects traffic once a session exists. A protective resolver refuses the address before that session can start. Cisco Umbrella and Purple Shield both work at this layer, which is defined in RFC 1035.

Malicious or off-policySafeDevice joins SSIDGuest, staff orresident VLANDNS lookupSent before anyconnection opensPurple ShieldresolverPolicy per SSID, VLANand venueBlockedNo connection is everopenedResolvedConnection proceeds;the firewall stillinspects
Malicious or off-policySafeDevice joins SSIDGuest, staff or residentVLANDNS lookupSent before anyconnection opensPurple ShieldresolverPolicy per SSID, VLANand venueBlockedNo connection is everopenedResolvedConnection proceeds; thefirewall still inspects
Where protective DNS sits in a WiFi session

A device joins an SSID and sends a DNS lookup to Purple Shield, which either blocks the domain before any connection opens or resolves it so the connection proceeds.

Connections

  1. Device joins SSID to DNS lookup
  2. DNS lookup to Purple Shield resolver
  3. Purple Shield resolver to Blocked (Malicious or off-policy)
  4. Purple Shield resolver to Resolved (Safe)

The two models differ in what they are built around. Per-user pricing assumes you know how many people you protect. An office knows its number. A hotel, stadium, shopping centre or hospital does not, because its WiFi serves guests, fans, shoppers and patients whose numbers change by the hour.

Ask "how many users?" at a venue and you get three honest answers. You can count peak concurrent devices, unique visitors a month or staff headcount. On one hotel, those figures differ by a factor of 72, as the model below shows. Whichever count you pick sets the Umbrella licence cost, and none of them describes the network you protect.

Three conditions bend the rule:

  • Staff carry managed laptops off-site and need protection at home or on public WiFi.
  • You already hold an enterprise security agreement that covers named staff.
  • You run many small venues and need one dashboard across them.

For the wider category, see our DNS filtering alternatives overview.

Which DNS filtering lane fits your network?

Answer four questions. Each outcome names the condition it depends on.

Which DNS filtering lane fits your network?

See every path as a list
Does the network serve people you cannot count in advance?
  • Yes: Is your WiFi already run on Purple?
    • Yes: Add Purple Shield to Purple Access Policies attach to the SSIDs and VLANs you already manage, in the same dashboard. Shield pricing
    • No: Do you run more than one venue, SSID or VLAN?
  • No: Do staff need protection on managed laptops away from your sites?
    • Yes: Agent on laptops, Purple Shield on the network A per-device agent follows the laptop off-site. Shield covers every device that joins your WiFi, including visitors. DNS filtering for multi-site estates
    • No: Purple Shield on office and staff networks With no off-site requirement, a per-device agent adds admin without adding coverage. DNS filtering alternatives

How do common venue scenarios map to a DNS filtering model?

Venue scenarios mapped to a DNS filtering model Data as of 2026-06-10
ScenarioRecommendationWhy
200-room hotel, guest and staff SSIDsPurple Shield, one policy per SSIDStaff headcount is 60; unique guests exceed 4,000 a month
20,000-seat arena, 40 event days a yearPurple Shield on the fan SSID with ad blockingPeak lasts hours; ad blocking cuts data by up to 44%
40-store retail estate with shopper WiFiPurple Shield, a policy per venueShoppers cannot be named; one dashboard covers every store
Hospital trust with patient, visitor and staff WiFiPurple Shield, a policy per VLANSt George's Healthcare NHS Trust runs Shield across its network
Student halls on Multi-Tenant WiFiPurple Shield with Purple AccessResidents change each term; policy follows the network
Airport with passenger WiFiPurple Shield per SSID and terminalPassenger volumes follow the timetable; AGS Airports runs Shield
Head office, 300 hybrid staffAgent on laptops, Purple Shield on office WiFiLaptops leave the building; visitors on site still need a policy
Single café with one SSIDPurple Shield standaloneA managed resolver removes patching and blocklist upkeep
Hotel and arena figures are illustrative models from this guide. Bandwidth figures are Purple's own data.

Worked scenario: a 200-room hotel

Situation. A 200-room hotel has 60 staff, a guest SSID and a staff VLAN. Assume 80% occupancy, 1.8 guests per occupied room and a two-night average stay.

What the count looks like. That gives 288 guests a night and about 4,320 unique guests a month, before anyone connects a second device. A per-user quote could be sized on 60, 288 or 4,320. The largest count is 72 times the smallest.

Outcome. With Shield, the hotel sets two policies: one for the guest SSID, one for the staff VLAN. Nothing is installed on a guest's device.

Worked scenario: a 20,000-seat arena

Situation. An arena hosts 40 events a year and employs 150 permanent staff. Fans connect for a few hours, then leave.

What the count looks like. Peak demand is 20,000 fans, roughly 133 times the permanent headcount. Size a per-user licence to the peak and it sits idle on 325 days. Size it to staff and the fan SSID falls outside the count.

Outcome. Shield applies one policy to the fan SSID and another to staff. Purple's own data shows ad blocking cuts data by up to 44% and DNS queries by up to 62%. That headroom matters when 20,000 devices share one backhaul.

Worked scenario: an NHS hospital trust

Situation. Hospital WiFi serves patients and visitors whose numbers change hourly, alongside clinical staff.

What was done. St George's Healthcare NHS Trust runs Purple Shield across its network.

Outcome. Shield blocks threats across the trust's network, with a policy per VLAN for patient, visitor and staff traffic.

How does Cisco Umbrella per-user pricing behave on guest WiFi?

What Cisco sells

Cisco has sold Umbrella as tiered packages. Its package comparison lists DNS Security Essentials and DNS Security Advantage for DNS-layer protection, with Secure Internet Gateway (SIG) tiers above them. Cisco has announced end of sale for these packages on 31 January 2027, with the last renewal on 31 January 2028 and end of support on 31 January 2029. The named replacements are Cisco Secure Access DNS Essentials and DNS Advantage, so a new quote may arrive under the Secure Access name. Cisco publishes no list price: prices come by quote from Cisco or a Cisco partner, and quotes are typically sized on the people you protect.

Where per-user pricing holds up

Per-user pricing works when the headcount is stable and named. A 300-person head office takes its number from HR. Managed laptops can run the Umbrella module in Cisco Secure Client, which keeps DNS protection on at home and on public WiFi. Here a per-user licence buys cover that leaves the building with the device.

Where it breaks at a venue

At a venue, the licence unit stops matching the risk. Three things go wrong:

  1. Nobody can be named. Guests, shoppers and fans connect once and leave. There is no directory to count from.
  2. The count swings. Occupancy, fixtures and seasons move device numbers by an order of magnitude. A count fixed at renewal is wrong most days.
  3. The agent has nowhere to go. You cannot install software on a guest's phone, so a roaming client adds nothing on the guest SSID.

Questions to put to your Cisco partner

  • How does this quote define a "user"?
  • Are devices on a guest SSID counted, licensed separately or excluded?
  • What happens when visitor numbers exceed the licensed count?
  • Can policy differ by SSID and VLAN at each venue?

How does Purple Shield scope protective DNS by network?

Placement and policy

Shield resolves DNS for every device on the networks you assign to it. It refuses lookups for malicious or off-policy domains before any connection opens. You set a policy per SSID, VLAN and venue from one dashboard. A hotel can filter adult content on the guest SSID and apply stricter rules to the staff VLAN.

Hardware you already own

Shield runs standalone on any WiFi, with no new hardware. That includes Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. If your WiFi runs on Purple Access, Shield attaches to the same networks and dashboard. Nothing is installed on a guest device.

Bandwidth and proof

Shield can block ads at the DNS layer. Purple's own data shows up to 44% less data and up to 62% fewer DNS queries with it on. Whitbread, AGS Airports and St George's Healthcare NHS Trust run Shield.

Where it stops

Network DNS protects devices on your network. It does not follow a laptop home. Where that is a hard requirement, pair Shield with an agent on those laptops. Do not license every visitor to get it.

What does each option cost to run?

The licence line is only part of the Cisco Umbrella cost. Model every line below for both options.

Cost line Per-user licence Purple Shield
What you scope People, named or estimated Policy per SSID, VLAN and venue
Counting effort Re-estimate visitors at each renewal Ask how guest devices count in the quote; 30-day free trial to measure first
Guest devices Licence terms set what you must count Covered by network policy
Agent deployment Roaming client on each managed laptop No agent on guest devices
Off-site protection Yes, through the roaming client No; covers on-network devices
Bandwidth effect Not a licence factor Up to 44% less data with ad blocking
Where the price comes from Cisco or a Cisco partner, by quote Purple, by tailored quote (Shield pricing)

The counting cost

Per-user pricing adds a recurring task: estimating visitors before every renewal. Someone pulls controller reports, debates the peak and signs off a number. Shield's quote is built on your sites, networks, users and plan, so ask how unmanaged guest devices are counted, as you would with any vendor. A 30-day free trial lets you measure real guest numbers before you buy.

The running cost

Both are cloud services, so neither adds hardware on site. The per-user lane adds client rollout and updates on managed laptops. The network lane adds policy changes per SSID, made in one dashboard. Self-hosting removes the licence but adds patching, blocklists and uptime to your team's workload.

What changes the answer?

Staff laptops must be protected off-site

If staff work from home on managed laptops, they need an agent. Keep per-user licensing to those named staff. Put Shield on every network visitors join.

You already pay for an enterprise agreement

An existing agreement may cover named staff for its remaining term. Leave it in place for laptops. Move guest SSIDs to Shield now, so visitors stay out of the Umbrella count at renewal.

You run many small venues

Across 50 cafés or 40 stores, per-head reconciliation multiplies with every site. A policy per venue from one dashboard keeps the work flat. See DNS filtering for MSPs and multi-site estates.

Devices use encrypted DNS

Browsers using DNS over HTTPS (RFC 8484) can bypass any network resolver. Firefox respects a canary domain that signals network filtering is in place. Ask every provider how they handle encrypted DNS before you commit.

Compliance sets the network design

PCI DSS expects guest WiFi to be segmented from the cardholder data environment. A policy per VLAN follows that segmentation directly. For the wider security picture, read our enterprise WiFi security guide.

Which option fits your estate?

Per-user licence model

Fits when

  • Fixed headcount of named staff needing off-site protection on managed laptops

Not when

  • Guests, fans or shoppers join your WiFi
  • Attendance swings by day or season

Purple Shield standalone

Fits when

  • Your WiFi runs on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme or Fortinet
  • You need a policy per SSID, VLAN and venue
  • Visitor numbers cannot be counted

Not when

  • Your only requirement is laptops off-site

Purple Shield with Purple Access

Fits when

  • You run Guest, Staff or Multi-Tenant WiFi on Purple
  • You want access and filtering in one dashboard

Not when

  • Your WiFi is not yet managed through Purple

Our recommendation: For any venue network that visitors join, deploy Purple Shield and scope policy per SSID, VLAN and venue.

Your first action: export 30 days of unique devices per SSID from your controller. Then list every venue, SSID and VLAN you run. That list shows how far a per-user count drifts from your real estate. It is also the brief for a Shield quote.

Key terms

Protective DNS
A resolver that refuses lookups for malicious or off-policy domains. It works at the Domain Name System layer specified in RFC 1035, so a blocked device never receives an address and never opens a connection. Both Cisco Umbrella and Purple Shield sit at this layer, so the pricing decision turns on the licence unit, not on where filtering happens.
DNS over HTTPS (DoH)
RFC 8484 specifies sending DNS queries and responses inside HTTPS, which encrypts lookups and lets a browser use a resolver other than the one the network assigns. DoH can bypass any network resolver, so ask each provider how it handles encrypted DNS before you sign.
Canary domain
Mozilla's use-application-dns.net check: if the network resolver returns a negative answer for this domain, Firefox treats it as a signal that network filtering is in place and does not enable DoH by default. Relevant when you rely on network-scoped filtering for guest devices running Firefox.
SSID
The Service Set Identifier defined in IEEE 802.11, the network name an access point broadcasts and a device joins. Purple Shield attaches a policy to each SSID, so a guest network and a staff network can carry different filtering rules.
VLAN
A virtual LAN defined by IEEE 802.1Q, which tags Ethernet frames to separate traffic into logical networks over shared infrastructure. A policy per VLAN lets a hospital or hotel filter patient, visitor and staff traffic differently and follow existing segmentation.
Per-user licensing
A commercial model in which the licence quantity is a count of people protected, named or estimated, set at purchase and revisited at each renewal. It fits an office with a stable HR headcount but breaks at venues where guest numbers swing by the hour or season.
Roaming client
Cisco's endpoint agent on a managed device, now delivered as the Umbrella module in Cisco Secure Client after the standalone Umbrella Roaming Client reached end of support on 2 April 2025. It keeps DNS-layer protection active when the device leaves the corporate network for home or public WiFi. It is the main reason to keep per-user licensing for staff laptops; it adds nothing on a guest SSID because you cannot install it on a guest's phone.
Secure Internet Gateway (SIG)
Cisco Umbrella package tiers (SIG Essentials and SIG Advantage) that sit above DNS Security Essentials and DNS Security Advantage and extend beyond DNS-layer protection. Cisco names Secure Internet Access Essentials and Advantage as their replacements. When reviewing a quote, confirm which tier you are being sized for and whether you need anything beyond DNS-layer filtering.
Cardholder data environment (CDE)
The PCI DSS term, defined by the PCI Security Standards Council, for the people, processes and systems that store, process or transmit cardholder data; segmentation isolates it from other networks. PCI DSS expects guest WiFi to be segmented from the CDE, and a DNS policy per VLAN follows that segmentation directly.
Personal data under GDPR
GDPR Article 4(1) defines personal data as any information relating to an identified or identifiable natural person, including online identifiers. DNS logs can identify a person, so check where your provider stores them and for how long.

Worked examples

A 200-room hotel with 60 staff, a guest SSID and a staff VLAN needs DNS filtering. A per-user quote asks how many users to license.

At 80% occupancy, 1.8 guests per occupied room and a two-night average stay, the hotel hosts 288 guests a night and about 4,320 unique guests a month. A per-user quote could be sized on 60, 288 or 4,320, and the largest count is 72 times the smallest. None of them describes the network being protected. The hotel deployed Purple Shield with two policies: one for the guest SSID and one for the staff VLAN. Nothing is installed on a guest's device.

A 20,000-seat arena hosts 40 events a year, employs 150 permanent staff and runs a fan SSID that fills for a few hours per event.

Peak demand is 20,000 fans, roughly 133 times the permanent headcount. A per-user licence sized to the peak sits idle on 325 days; sized to staff, it leaves the fan SSID outside the count. The arena applies one Purple Shield policy to the fan SSID and another to staff, with ad blocking on for fans. Purple's own data shows ad blocking cuts data by up to 44% and DNS queries by up to 62%. That headroom matters when 20,000 devices share one backhaul.

An NHS hospital trust runs WiFi for patients and visitors whose numbers change hourly, alongside clinical staff, and needs DNS protection across the network.

St George's Healthcare NHS Trust runs Purple Shield across its network, with a policy per VLAN for patient, visitor and staff traffic. By Purple's own data, Shield blocks about 241,000 threats a week at the trust. The per-VLAN policy also follows the segmentation the trust already uses, so filtering rules map to the way its networks are built rather than to a head count that changes every hour.

Frequently asked questions

How much does Cisco Umbrella cost for a venue?

Your Cisco Umbrella cost comes from a partner quote, not a public list price. That quote is sized on a count of people, and at a venue the count is the decision. Staff headcount, peak devices and unique monthly visitors can differ by a factor of 72 on one hotel. Get the counting rule in writing before you compare any figure with a network-scoped option such as Purple Shield.

Is Umbrella per-user pricing based on staff or on WiFi devices?

Per-user pricing counts people, which on most estates means your staff. Guest devices on a public SSID are the grey area. Ask your partner three things in writing: how a user is defined, how guest WiFi is treated and what happens when visitors exceed the licensed count. If the answers shift at each renewal, your Umbrella per-user pricing is a forecast rather than a fixed figure.

Does Purple Shield work with the WiFi hardware I already own?

Yes. Shield runs standalone on your existing network, including Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. It needs no new hardware and no agent on guest devices. You assign a policy to each SSID or VLAN. If you already run Purple Access, Shield attaches to the networks you manage there, in the same dashboard.

How do I move from Umbrella to Shield without a gap in protection?

Move one network at a time and run both services in parallel. Start with the guest SSID, where per-user licensing fits worst, while staff networks stay put. Compare blocked categories and query volumes for two weeks, then move the next VLAN. Keep any roaming agent on managed laptops until its term ends. Our [multi-site guide](guide:dns-filtering-for-msps-and-multi-site) covers sequencing across many venues.

Does DNS filtering make guest WiFi compliant with PCI DSS or GDPR?

No, not on its own, but it supports both. PCI DSS expects guest WiFi to be segmented from the cardholder data environment, and a policy per VLAN follows that segmentation. Under GDPR, DNS logs can identify a person, so check where they are stored and for how long. Purple is ISO 27001 and Cyber Essentials certified and GDPR compliant, which shortens your supplier review.

Can I keep Umbrella for staff laptops and use Shield for guest WiFi?

Yes. That split keeps each tool on the job its model was built for. A roaming agent protects managed laptops away from your sites. Shield protects every device that joins your WiFi, including visitors nobody counted. You stop estimating visitor numbers for a per-user quote, and the staff licence shrinks back to the named people it was designed around.

How is Purple Shield priced?

Shield is quoted on your sites, networks, users and plan, with a 30-day free trial and no hardware costs. It runs standalone on any network or adds onto Purple Access. There are no published prices; the [Shield pricing](product:shield/pricing) page sets out the trial and the two ways to buy. Bring your list of venues, SSIDs and VLANs to the conversation with Purple.

Is a free resolver or Pi-hole good enough for guest WiFi?

For one small site with an in-house engineer, a self-hosted resolver can work. It costs nothing to license, but updates, blocklists, uptime and logs all fall to you. Across several venues, a managed service removes that upkeep. See [Pi-hole vs managed DNS filtering](guide:pi-hole-vs-managed-dns-filtering) and [Control D alternatives](guide:control-d-alternatives) for the detailed comparison.

Sources

Decide what your network reaches, free for 30 days

Tell us your networks and who uses them, and we map a policy to each. Point one at Shield and see what it stops for 30 days.

Tell us your networks. We map a policy to each one.