One DNS policy per client, on the network and off it.
Shield is the DNS filtering module in The One Stack, the platform MSPs run their whole business on. It checks each domain lookup against the client’s policy and threat intelligence, then answers it or returns a block page. It covers a client’s office networks and the laptops that leave them.
DNS filtering (Shield) is part of Security, one of the six systems of The One Stack.
What it does.
A policy per client
A DNS profile sets which categories are filtered. Assign it to your organization, to a client or to one device, and the most specific assignment applies.
Allow and block lists
Lists work at the platform, MSP and client level. Saving an entry clears the cached verdict for that domain, so the change applies on the next lookup.
Threat filtering
Lookups are checked against threat feeds and against Shield’s own record of which domains are newly seen across the platform. A domain that has not been seen before is analyzed, by its name and then by its content.
Roaming laptops
A roaming token sends a laptop’s lookups to Shield over encrypted DNS, so the client’s policy follows the device off the office network.
A verdict you can read
The verdict browser shows whether a domain was allowed or filtered, which check decided and why. Reports show lookups and filtered domains per client.
Inside dns filtering.
More of the product, screen by screen.
A profile sets the policy
A DNS profile holds the categories to filter, the threat feed setting and its own allow and block lists. Build it once and assign it to your organization or to individual clients.
How it connects.
DNS filtering reads and writes the same record as the rest of the platform.
A detection carries the domain’s reputation
When a detection in Defend involves a domain, Shield’s reputation for it is added to the alert.
Filtering runs inside secure access
Shield DNS filtering runs inline on dedicated concentrators, the secure access gateways that each serve one client. Remote users and connected sites get that client’s policy.
It switches on with the one agent
On managed devices, DNS filtering is a module of the agent already installed. The device list shows which policy is in force on each one.
Policy attaches to the client record
Lists and profiles belong to the client companies you already manage, so there is no second customer list to keep.
Questions
Questions about dns filtering
Do I need to install anything to filter an office?
No. Point the network’s DNS at Shield and every device that uses it is filtered. Laptops that leave the office use the agent or a roaming token.
How quickly does an allow or block entry apply?
On the next lookup of that domain. Saving the entry clears the cached verdict for it.
Can I see why a site was filtered?
Yes. The verdict browser shows the verdict for a domain, the check that decided it and the category, and you can test a domain on demand.
Is DNS filtering a separate charge?
No. DNS filtering is part of the plan, which is priced by people and devices, not by product. The pricing page explains the units.
Related
Keep going
Start
Run on One.
Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.