Skip to content
Shield

ComparisonDNS filtering alternatives

A Cisco Umbrella alternative for guest WiFi

Decide whether Purple Shield or Cisco Umbrella should protect each network you run. You will be able to match guest and public SSIDs to agentless protective DNS, keep identity-led control where staff need it, and compare licensing structure without guessing prices. You can also plan a guest network move as a...

11 min read

A Cisco Umbrella alternative for guest WiFi

Choose Purple Shield if you need protective DNS for anonymous guests on public WiFi. It applies a policy per SSID and VLAN, with no agent and no new hardware. It comes from the platform already running 80,000+ venues in 90 countries. Choose Cisco Umbrella if you are securing named employees and managed devices within a wider SASE programme.

The short answer on Cisco Umbrella alternatives for guest WiFi

Cisco Umbrella is a mature product that solves a different problem. It grew out of OpenDNS, which Cisco acquired in 2015. It now sits within Cisco's secure access service edge (SASE) portfolio, which delivers networking and security together from the cloud. Its home ground is a known workforce: named employees, managed laptops, branch offices and roaming staff, all tied to a directory.

Guest WiFi breaks those assumptions. The people on your network are anonymous and change by the hour. Footfall swings with events and seasons. Visitors install no agent and hold no account in your directory. A licence counted in seats has nothing stable to count.

Purple Shield is protective DNS built for that situation. Protective DNS filters threats and unwanted content when a device looks up a domain name. You set a policy per SSID, per VLAN (virtual LAN, a logically separate network segment) and per venue. Shield runs from the same platform as your captive portal, the sign-in page guests see before they get online.

The answer turns on identity. If the people you protect have accounts you manage, Umbrella's model fits. If they are visitors you cannot name, Shield's model fits. For the full head-to-head, read Shield vs Cisco Umbrella. For the wider market, start with our overview of DNS filtering alternatives.

What we compared Shield and Umbrella on, and why

Why placement comes first

Protective DNS acts when a device asks where a domain lives. That lookup happens before any connection opens. If the domain is malicious or breaks policy, the resolver refuses it and the device never connects. A firewall usually judges traffic after a session starts, and most of that traffic is now encrypted. Filtering at resolution stops phishing, malware and command-and-control domains before they reach the perimeter. The UK National Cyber Security Centre runs its protective DNS service for the public sector on the same principle.

Both Shield and Umbrella filter at the DNS layer. The difference lies in everything wrapped around that layer.

Cisco Umbrella: identity-ledPurple Shield: network-ledManaged deviceCisco Secure Clientlinks traffic to apersonDirectory identityPolicy by person orgroup, synced from yourdirectoryUmbrella cloudDNS layer plus webgateway, firewall andCASB by packagePer-seat policyand reportsLicensed per seatacross the workforceGuest joins venueSSIDAny device, no agent,no accountDNS query reachesShieldChecked at resolution,before any connectionopensPolicy per SSID,VLAN, venueThreat, content and adblocking rulesBlocked orresolvedBad domains neverconnect; results in thePurple dashboard
Umbrella ties policy to a known identity; Shield ties policy to the guest network itself

Two lanes compare Cisco Umbrella's identity-led path through agent, directory and cloud with Shield's path from guest SSID to a DNS policy decision.

Connections

  1. Managed device to Directory identity
  2. Directory identity to Umbrella cloud
  3. Umbrella cloud to Per-seat policy and reports
  4. Guest joins venue SSID to DNS query reaches Shield
  5. DNS query reaches Shield to Policy per SSID, VLAN, venue
  6. Policy per SSID, VLAN, venue to Blocked or resolved

The criteria we scored

We fixed eight criteria before scoring either product. Each option is scored only from its own public material: Cisco Umbrella documentation and Purple's product information.

  1. Where filtering happens in the connection.
  2. Who the product is built to protect.
  3. Whether visitor devices need an agent.
  4. The unit a policy attaches to.
  5. The licence unit.
  6. Whether pricing is published.
  7. Scope beyond DNS.
  8. Fit with the hardware and guest stack you already run.

We show no competitor prices. Cisco quotes Umbrella through its own team and partners, so any figure would be unverifiable and quickly out of date. If you are weighing other vendors, see DNSFilter alternatives and Cloudflare Gateway vs Purple Shield.

Shield vs Cisco Umbrella: the comparison matrix

The matrix below is the quickest way to see where each product is aimed.

Cisco Umbrella vs Purple Shield for guest WiFi, scored from each vendor's public material Data as of 2026-06-10
CriterionCisco UmbrellaPurple Shield
Where filtering happensDNS layer, plus web gateway and cloud firewall in higher packagesDNS resolution, before any connection opens
Built forNamed employees, managed devices, branches and roaming staffAnonymous, changing visitors on guest and public WiFi
Agent on the deviceOptional for network DNS; Cisco Secure Client for per-person policy and roamingNone; guests install nothing
Policy unitIdentity: person, group, device, network or siteSSID, VLAN and venue, from one dashboard
Licence unitPer seat, typically each named employeeNo per-guest seat; add-on to Purple plans or standalone
Pricing visibilityQuote-based through Cisco and partnersSet out on the Shield pricing page
Scope beyond DNSSecure web gateway, cloud firewall and CASB, by packageThreat blocking, content filtering and ad blocking at DNS
Hardware fitNetwork DNS on any gear; native Cisco and Meraki integrationsCisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, Fortinet

Read it as two products answering two different questions. Umbrella asks who is connecting. Shield asks which network the device is on.

Where Cisco Umbrella wins

If your problem is a workforce, Umbrella covers ground Shield does not attempt to cover.

Identity-led control for your own staff

Umbrella ties policy to people. It integrates with directory services, including Microsoft Entra ID, so you can set rules per person or group. You can report on each employee's activity. Cisco Secure Client carries that protection to laptops off the corporate network, at home or on the road.

Security beyond the DNS layer

DNS is one layer of Umbrella. Depending on package, Cisco adds a secure web gateway (SWG) that inspects encrypted web traffic. It also adds a cloud-delivered firewall and a cloud access security broker (CASB) to govern SaaS use. Those are the building blocks of a SASE programme.

Threat intelligence and the Cisco estate

Umbrella draws on Cisco Talos, Cisco's threat intelligence group. Cisco documents native Umbrella integrations with Cisco Meraki and other Cisco networking. If your security operations team already works in Cisco consoles, standardising on one vendor has real value.

For a managed workforce, Umbrella is a credible choice, and this guide does not argue otherwise.

Where Shield wins on guest WiFi

Built for visitors you cannot name

Shield assumes nothing about the person on the network: no account, no agent, no enrolment. The policy belongs to the network. Each SSID, VLAN and venue gets its own rules from one dashboard. A hotel could run a family-safe policy on its lobby SSID and a lighter one on its conference VLAN.

Agentless protective DNS, no new hardware

You point the network's DNS at Shield, and the policy applies to every device that joins. That covers a guest's phone, a laptop and a smart TV that could never run an agent. Shield works on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet networks. Run it standalone on any WiFi, or add it to Purple Access as a guest WiFi security add-on.

One platform for the whole guest stack

Purple already runs captive portals and Guest WiFi analytics across 80,000+ venues in 90 countries. Shield adds protection inside that same platform. The team that manages guest sign-in also sets security policy, so you replace a separate console with one dashboard.

Earlier threat flags and lighter networks

Shield flags malicious domains at DNS resolution before connections open, stopping threats before traffic reaches the network. With ad blocking enabled, Shield suppresses unwanted advertising requests and tracking queries. On a busy venue network, that capacity goes back to the guests you are serving.

  • 80,000+venues on PurpleIn 90 countries
  • 500M+users and loginsA year globally
  • 99.999%uptime SLAPlatform availability
  • 2012foundedPlatform established

What each costs to run: licensing structure, not price

This section shows no prices. What you can compare is structure: what you count, what grows the bill, and what work sits outside the licence.

Umbrella: seats sized to a workforce

Umbrella packages are licensed per seat, typically sized to your number of named employees. That suits a business with a stable headcount. It sits awkwardly on a stadium concourse or in a shopping centre. There, fan and shopper numbers rise and fall with every fixture and season.

Endpoint work adds cost of its own. Per-person policy and roaming protection depend on rolling out Cisco Secure Client to managed devices. Someone has to maintain that rollout.

Shield: no guest seats to count

Shield has no per-guest seat. You buy it as a security add-on to the Connect, Capture or Engage plans, or standalone on any WiFi. Guests install nothing, so there is no endpoint rollout. The Shield pricing page sets out current terms, so you can budget before a sales call.

How running costs are structured, not what they are Data as of 2026-06-10
Cost driverCisco UmbrellaPurple Shield
How you buyQuote from Cisco or a partnerAdd-on to Connect, Capture or Engage, or standalone on any WiFi
What you countSeats, typically named employeesNo guest seats to count
Seasonal peaksAnonymous visitors do not map to a seatNo seat count to resize for peaks
New hardwareNone for network DNSNone; uses your existing access points
Endpoint workSecure Client rollout for per-person policyNone
Admin consolesSeparate from the guest WiFi stackOne dashboard with captive portal and analytics
Price listNot publishedShield pricing page
Structure only. Confirm current Umbrella licensing terms with Cisco or an authorised partner.

How much effort is a move from Umbrella to Shield?

A move is a configuration change per guest network, not a hardware project. Most estates follow four steps.

Map what Umbrella does today

List every network that resolves through Umbrella and who uses it. Separate staff networks from guest and public SSIDs. Staff networks that rely on the web gateway or CASB usually stay on Umbrella.

Move guest networks first

Create a Shield policy for each guest SSID or VLAN. Agree the content categories with venue operations before you switch. Then change the DNS each guest network hands out, usually through DHCP on your controller or gateway. Your hardware vendor's documentation covers the exact steps for your platform.

Close the bypass routes

Run in parallel, then cut over

Test from a guest device on each SSID and check the blocks appear in the Purple dashboard. Move venues in waves, starting with a single site. Once guest traffic flows through Shield, remove the guest egress networks from your Umbrella configuration.

How to decide between Shield and Umbrella

Use one question as your decision rule: does every person on this network hold an account you manage? If yes, an identity-led product like Umbrella fits. If no, choose Shield.

Shield or Cisco Umbrella: which fits your network?

Purple Shield

Fits when

  • You protect guest, public or visitor WiFi
  • Visitors are anonymous and numbers swing with the season
  • You want a policy per SSID, VLAN and venue with no agent
  • You already run Purple captive portals or analytics

Not when

  • You need encrypted-traffic inspection, CASB or per-person reporting for staff

Cisco Umbrella

Fits when

  • You secure named employees on managed devices
  • Staff need protection off-network through Cisco Secure Client
  • You want DNS, web gateway and cloud firewall under one Cisco contract
  • Your security team already runs the Cisco estate

Not when

  • Most people on the network are anonymous guests

Our recommendation: Run Shield on guest and public SSIDs. Keep Umbrella, or a comparable SASE product, where you need identity-led control of your own workforce.

Many estates run both: Umbrella on staff devices, Shield on guest SSIDs. Your next step is to price your guest networks on the Shield pricing page. Then read our enterprise WiFi security guide for the segmentation that sits beneath it. You can find more on the wider platform at Purple.

Key terms

Protective DNS
A recursive DNS resolver that checks each lookup against threat intelligence and policy, and refuses to resolve malicious or disallowed domains. It builds on the Domain Name System defined in RFC 1034 and RFC 1035. The UK NCSC runs a protective DNS (PDNS) service for the public sector on this principle. This is the layer both Shield and Umbrella filter at. Because it acts before any connection opens, it stops phishing, malware and command-and-control domains without inspecting encrypted traffic, which is why it suits guest WiFi.
SSID
Service Set Identifier, the network name an access point advertises, defined in IEEE 802.11. One physical access point can broadcast several SSIDs, each mapped to its own network segment and policy. Shield attaches policy to the SSID rather than to a person. A venue can run a family-safe policy on one SSID and a lighter policy on another, from one dashboard.
VLAN
Virtual LAN, a logically separate network segment on shared switching infrastructure, specified by IEEE 802.1Q, which adds a tag to Ethernet frames to identify segment membership. Shield applies a policy per VLAN as well as per SSID. Segmenting guest VLANs from staff VLANs also stops guest traffic reaching staff systems when you run Umbrella and Shield side by side.
Captive portal
The sign-in page a network presents to a device before granting internet access. The IETF describes the architecture in RFC 8952, and RFC 8910 defines how DHCP and IPv6 router advertisements can announce a captive portal to devices. Shield runs from the same Purple platform as your captive portal, so the team that manages guest sign-in also sets security policy and you drop a separate console.
DHCP
Dynamic Host Configuration Protocol, defined in RFC 2131, which assigns addresses and network settings to devices. The DNS server option defined in RFC 2132 tells each device which resolver to use. Moving a guest network to Shield usually means changing the DNS servers that DHCP hands out on your controller or gateway. That is a configuration change, not a hardware project.
DNS over HTTPS (DoH)
A protocol defined in RFC 8484 that carries DNS queries inside encrypted HTTPS sessions, so a device can reach a resolver of its choice without using the network's assigned DNS server. DoH is a bypass route for any network DNS filter, Shield or Umbrella. Block outbound DNS to other resolvers at the gateway and restrict known DoH endpoints where your firewall supports it.
SASE
Secure access service edge, an architecture that delivers networking and security functions together from the cloud. It typically combines DNS-layer security, secure web gateway, cloud firewall and CASB, with policy tied to user identity. Umbrella sits within Cisco's SASE portfolio. If you only need DNS filtering for anonymous guests, you would pay for an identity-led SASE product while using one layer of it.
Secure web gateway (SWG)
A cloud or on-premises proxy that inspects web traffic, including TLS-encrypted sessions, and enforces acceptable use and malware policy beyond the DNS lookup. Umbrella adds an SWG in higher packages. Staff networks that rely on it usually stay on Umbrella during a move, while guest networks go to Shield.
CASB
Cloud access security broker, a control point between people and cloud services that discovers, monitors and governs SaaS use, often applying data protection policy tied to a named identity. Umbrella offers CASB by package for managed workforces. It has no role on an anonymous guest network, which is one reason Shield's DNS-only scope fits guest WiFi.
PCI DSS
The Payment Card Industry Data Security Standard published by the PCI Security Standards Council. It requires network security controls that isolate the cardholder data environment, and segmentation reduces which systems fall in scope. Protective DNS supports PCI DSS but does not deliver it alone. You still segment payment systems from guest networks, and DNS filtering adds a control on top.
GDPR
The EU General Data Protection Regulation (Regulation (EU) 2016/679). Article 28 sets the obligations on processors that handle personal data on a controller's behalf, including contract terms and security measures. The DNS layer sees which domains a device requests, so choose a processor with clear data handling. Purple is ISO 27001, GDPR, CCPA and Cyber Essentials certified.

Worked examples

A hotel wants a family-safe filter in its lobby but a lighter policy for business delegates on its conference network. Guests are anonymous, install no agent and hold no account in the hotel's directory. How should the hotel apply protective DNS?

The hotel attaches policy to the network, not the person, using Shield. It runs a family-safe policy on the lobby SSID and a lighter policy on the conference VLAN, both managed from one Purple dashboard. Every device that joins inherits the rules for that network, including phones, laptops and smart TVs that could never run an agent. An identity-led product would need a directory account or Cisco Secure Client for per-person policy, and guests have neither. Because Shield sits in the same platform as the captive portal, the team that runs guest sign-in also sets these policies.

An estate resolves both staff and guest networks through Cisco Umbrella. Staff rely on the web gateway and CASB, but guest SSIDs only use the DNS layer under a seat-based licence. How should the IT team move guest traffic to Shield?

The team first maps every network resolving through Umbrella and separates staff networks from guest and public SSIDs. Staff networks using the web gateway or CASB stay on Umbrella. For each guest SSID or VLAN, they create a Shield policy, agreeing content categories with venue operations beforehand. They then change the DNS each guest network hands out through DHCP on the controller or gateway. They block outbound DNS to other resolvers and restrict known DNS over HTTPS endpoints to close bypass routes. After testing from a guest device and confirming blocks in the Purple dashboard, they move venues in waves and remove guest egress networks from Umbrella.

Frequently asked questions

What is a good Cisco Umbrella alternative for guest WiFi?

Purple Shield is a protective DNS service built for guest and public WiFi rather than a managed workforce. It filters threats and content at DNS resolution, with a policy per SSID, VLAN and venue. Visitor devices need no agent. Whitbread, AGS Airports and St George's Healthcare NHS Trust run it. DNSFilter and Cloudflare Gateway are also worth shortlisting for specific estates.

Why is Cisco Umbrella a poor fit for anonymous guest WiFi?

Umbrella's deepest features assume you know who is on the network. Per-person policy, roaming protection and identity reporting rely on a directory and Cisco Secure Client on managed devices. Guests have neither. You can point a guest network's DNS at Umbrella. You then pay for an identity-led SASE product while using only its DNS layer, under a seat-based licence.

How does Umbrella's per-seat licensing work for public WiFi?

It works awkwardly, because the licence counts seats and public WiFi has no fixed seats. Cisco sells Umbrella packages through its own team and partners on a quote basis, typically sized to named employees. Anonymous visitors who change hourly and swing with the season do not map cleanly to that unit. Ask Cisco or your partner how they would license a guest network.

Is there a no-hardware alternative to Umbrella for venues?

Yes. Shield runs in the cloud, so you add no appliance and replace no access points. You point the guest SSID or VLAN at Shield for DNS, usually through DHCP on your controller or gateway. It works on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet networks, standalone or alongside Purple Access.

How does Shield compare with Umbrella on pricing transparency?

Shield is easier to price up front. Its terms are set out on the Shield pricing page, and you buy it as an add-on to Connect, Capture or Engage or standalone on any WiFi. Umbrella pricing is quote-based through Cisco and its partners, with no public price list. Only one model lets you budget a guest network before a sales call.

Can we run Cisco Umbrella for staff and Shield for guests?

Yes, and for many estates it is the right split. Keep Umbrella on managed staff devices, where its web gateway, CASB and directory integration earn their place. Put Shield on guest and public SSIDs, where visitors are anonymous. Each network resolves through its own filter, so the two never overlap. Segment the VLANs so guest traffic cannot reach staff systems.

Does protective DNS help with GDPR or PCI DSS compliance?

It supports compliance but does not deliver it alone. PCI DSS expects you to segment payment systems from guest networks, and DNS filtering adds a control on top of that segmentation. Under GDPR, the DNS layer sees which domains a device requests, so choose a processor with clear data handling. Purple is ISO 27001, GDPR, CCPA and Cyber Essentials certified.

How much effort is a move from Umbrella to Shield?

It is a configuration change per guest network, not a hardware project. You create a Shield policy for each SSID or VLAN, switch the DNS those networks hand out, and block bypass routes. Then you test from a guest device. Staff networks on Umbrella stay untouched. Most of the effort goes into auditing which networks use Umbrella today and agreeing each venue's content policy.

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. Running change control? We plan a pilot on one site with your team.

  1. We map your networksA Purple expert maps your networks, your venues and the people on each, and answers your questions on bypass, outages, data handling and integrations.
  2. You get a policy for each oneStaff, guests, students, residents, IoT and paid tiers, each with the policy it needs.
  3. You prove it, then get your tailored quote30 days free on one network, or a pilot on one site planned with your team, then Shield priced standalone or as an add-on to your Access plan.

Your policy map

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

A Purple expert comes back with a policy for every network and group you run, from the team that has run content filtering since 2012 and runs WiFi for 80,000+ venues in 90 countries.