Connecting ScoutDNS to Neo

You connect ScoutDNS once at the MSP level. One API key covers every organization in your ScoutDNS account.

1. Create the API key

Open API Access Management

Create the key

Create an API key for Neo. A read and write key lets Neo change allow and block lists; a read-only key lets Neo research and answer questions, and ScoutDNS refuses every change Neo would make with it.

Copy the key

Copy the key.

Deleting the key in ScoutDNS cuts Neo off at once. Save the new key here when you replace it.

2. Add the key in Neo

Open Integrations

In the Neo Dashboard, open Integrations and find the ScoutDNS card, under DNS & Web Filtering.

Save the key

Paste the API key and click Save settings. Neo checks it against ScoutDNS before saving, so a wrong key is rejected straight away.

Check the mapping

Open the card’s Organization Mapping tab and confirm each ScoutDNS organization is matched to the right PSA company. A ticket run acts only for a mapped organization.

3. Route review requests to tickets

When the block page lets users request a review, ScoutDNS emails each request. To have an agent research them, send those emails to your PSA’s support mailbox, so each one opens a “ScoutDNS Domain Review Request” ticket on the customer’s company.

4. Turn ScoutDNS on per agent

Open the agent, go to its Tools & Settings tab, click DNS & Web Filtering, and expand the ScoutDNS block. Pick one of its Presets, or set each area yourself:

Area	Access levels you can pick	Notes
Reports and Query Logs	Disabled, Read Only	Query logs, threats, top domains and categories, statistics. Turn on for an agent that researches review requests.
Allow and Block Lists	Disabled, Read Only, Read / Write	The lists and the policies that use each; adding a domain to one.
Policies, TLD Filters and Block Pages	Disabled, Read Only, Read / Write	Policy settings, TLD filters and block pages.
Locations, Networks and Relays	Disabled, Read Only, Read / Write	Sites, their WAN addresses and relays.
Roaming Clients and Profiles	Disabled, Read Only, Read / Write	Roaming clients, their status and policy, and client profiles.
Roaming Client Installers	Disabled, Read Only, Read / Write	Installers and install bundles. Neo keeps the install key out of the run log.
Customer Organizations	Disabled, Read Only, Read / Write	Your organizations and the locations and profiles in each.
Console Users	Disabled, Read Only, Read / Write	ScoutDNS console users and their roles.
Log Streams	Disabled, Read Only, Read / Write	Streams that send query logs to a SIEM.
Usage and Billing	Disabled, Read Only	Query and seat usage per organization.

Preset	What runs on its own	What asks a technician
Read Only	Every read except installers	No write is allowed
Helpdesk	Every read except installers, console users and log streams	Every allow and block list change; no other write is allowed
IT Admin	Every read, and location, network, roaming client, installer and organization changes	List, policy, console user and log stream changes, and the changes that always ask
Full Automation	Every read and write	The changes that always ask

See ScoutDNS API for what the agent can read and change.

Getting started

Core

Triggered & Scheduled Agents

Chat Agents

Integrations

Product

Workflows

Customizing Neo

Connecting ScoutDNS to Neo

1. Create the API key

2. Add the key in Neo

3. Route review requests to tickets

4. Turn ScoutDNS on per agent

​1. Create the API key

​2. Add the key in Neo

​3. Route review requests to tickets

​4. Turn ScoutDNS on per agent

1. Create the API key

2. Add the key in Neo

3. Route review requests to tickets

4. Turn ScoutDNS on per agent