Docs / Policies & Filtering / Working with policies
Browse Policies & Filtering
Policies & Filtering

Working with policies

Policies are where you define what gets blocked or allowed in ScoutDNS, threat categories, content categories, applications, and per-network or per-device overrides.

Updated Aug 23, 2025 • 6 min read

A policy is where you configure threat protections and content restrictions. Once created, policies are assigned to control points, WAN/LAN networks, roaming-client device profiles, or Active Directory / Entra ID persona groups, depending on how you want filtering applied.

Policy list view in the Admin Console

How policies relate to other objects

  • Allow/Block lists are attached to a policy and override category decisions for specific domains.
  • Policies carry the actual filter configuration (threats, content categories, applications, Safe Search, ad blocking, etc.).
  • Control points, WANs, LANs, device profiles, personas, are what you assign a policy to. The same policy can apply to multiple control points.

Default policies are read-only

ScoutDNS ships a set of default system policies as examples. They are read-only and can’t be edited, they’re meant to demonstrate sensible starting points. To take full control, create your own policies (you can copy from a default to save typing).

Template and global policies

Any policy can be reused across multiple control points. You can also treat a policy as a template, copy it and tweak the copy for a different control point. MSPs commonly use this pattern to customize per-tenant policies from a shared baseline.

Create a policy

  1. Open the Policy tab and click New Policy in the top right.
  2. (Optional) Use the Copy a Policy dropdown to seed from a default or existing policy.
  3. Fill in the four tabs: Settings, Threats, Content, Applications.

Settings tab

Two groups: Base and Advanced.

Policy Settings tab, Base and Advanced configuration

Base settings

FieldWhat it does
Policy NameDisplay name for the policy
Policy DescriptionFree text, useful for explaining the policy’s intent to other admins
Allow/Block ListAttach a previously created list to override category decisions for specific domains
YouTube Safe ModeApply YouTube restrictions. See the YouTube article for what each mode allows
Safe SearchForce safe results on Google and Bing. See Safe Search explained for the difference between On and Forced
Ad BlockingBlock domains commonly used to serve display ads

Advanced settings

ToggleWhat it does
TLD filterApply a previously created TLD allow/block filter
Whitelist onlyBlock everything except domains on the policy’s allow list
Logging onlyDisable enforcement but still log what would have been blocked, useful for piloting a policy before going live
Block UnclassifiedBlock any domain that doesn’t have a ScoutDNS category. Can block newly registered domains; submit a classification request if a legit domain is being blocked
Max Domain LengthBlock domains over a configurable character length

Threats tab

Toggle protection against malware, phishing, command-and-control, and other security threat categories.

Policy Threats tab

Content tab

Block content categories like Adult, Social Media, Streaming, Gambling, Real Estate, Job Search, and many others. Some domains appear in multiple categories, blocking a category blocks every domain it contains.

Policy Content tab, long list of toggleable categories

Applications tab

Block specific web applications by name. For example, toggling Social Media here blocks Facebook, Instagram, and similar apps without having to know each underlying domain.

Policy Applications tab

Apply a policy to a control point

A single policy can be applied to networks, device profiles, persona groups, or individual devices. The right one depends on your deployment shape.

[!TIP] Best practice: assign policies to device profiles rather than individual clients. Add all roaming clients to a profile and apply the policy to the profile, every device under that profile inherits the policy automatically.

To a WAN or LAN network

  1. Open the Sites tab → select the site.
  2. Open the WAN or LAN subtab → click the network you want to apply the policy to.
  3. Click Edit WAN (or Edit LAN).
  4. Under Policy, select the policy.
  5. Save.

LAN policies require a Relay on the network.

Assigning a policy to a WAN

To a device with the roaming agent

  1. Clients → Manage → select the device.
  2. Edit Client (top right).
  3. Under Info, set the Policy dropdown.
  4. Save.

Assigning a policy directly to a client

To an Active Directory or Entra ID persona group

  1. Open the persona → Active Directory subtab.
  2. Edit Persona (top right).
  3. Move groups from Observed Groups to Configured Groups.
  4. Under each configured group, pick the Policy to apply.
  5. Save.

Assigning policies per persona group

  1. Clients → Configure → select the profile → Edit Profile.
  2. Under Settings → Default Policy, pick the policy.
  3. Save.

Every device assigned to the profile inherits the policy.

Assigning a policy at the profile level

To an individual device

When you need a special-case policy on one device, you can override both the profile and the policy from the device record:

  1. Clients → Manage → select the device → Edit Client.
  2. Set Profile and Policy independently.
  3. Save.

Overriding policy on a single device

Was this article helpful?
Still stuck? Open a ticket and we'll follow up by email.
Open a ticket
Last updated Aug 23, 2025