Connecting Dark Web ID to Neo

You connect Dark Web ID once at the MSP level. One partner user covers every client organization it can see.

1. Prepare the API user

Dark Web ID lets only a partner user call its API, and only from the addresses on that user’s IP allowlist.

Pick or create the user

In Dark Web ID, use a user in your partner organization with the Partner Administrator or Partner Agent role. A dedicated user for Neo is easiest to manage.

Turn on web services

On that user (My Account > My Settings, or Edit User), turn on Permit access to web services.

Allow Neo's addresses

In the user’s IP Address whitelist field, add all three of Neo’s addresses:

235.25.90
5.41.248
196.4.206

Different Neo services make different calls, so add all of them (IP Whitelisting).

Set a Dark Web ID password

The API needs the user’s own Dark Web ID password. A KaseyaOne sign-in does not replace it. If Require Log In with KaseyaOne is on, add the user to User Overrides on the KaseyaOne tab of Dark Web ID’s settings, set the password with Forgot Password on the Dark Web ID sign-in page, and then remove the override if you like. Kaseya’s article Enabling API access for Dark Web ID has the details.

2. Add the user in Neo

Open Integrations

In the Neo Dashboard, open Integrations and find the Dark Web ID card, under Security.

Save the user

Enter the user’s email and Dark Web ID password and click Save settings. Neo checks them against Dark Web ID before saving. A refusal names the cause: a wrong password, web services turned off, or an address missing from the allowlist.

Removing one of Neo’s addresses from the allowlist, or turning web services off, stops Neo’s calls until you restore them in Dark Web ID. If you change the user’s password, save the new one here too.

3. Turn Dark Web ID on per agent

Open the agent, go to the Integrations section, and pick an access profile for the Dark Web ID block, or set each area yourself:

Area	Access levels you can pick	Notes
Organizations	Disabled, Read Only, Read / Write	Client organizations, your reseller accounts and supply-chain companies; creating, changing, deactivating and deleting an organization. Deleting one always asks a technician.
Monitored Domains	Disabled, Read / Write	Adding an email domain to an organization’s monitoring.
Compromises	Disabled, Read Only, Read / Write	Each organization’s compromises; setting a status, and creating or deleting a compromise record.
Live Search	Disabled, Read Only	A live search for one email address or domain. Kaseya limits live searches per partner.
Users	Disabled, Read Only, Read / Write	Dark Web ID users and their notification preferences.
User Roles	Disabled, Read / Write	Any user write that sets a role, other than the Standard role on a new user. Users must allow it too.
Alerts and Reports	Disabled, Read / Write	An organization’s alert emails, its report sections and its automated monthly and quarterly reports.

Profile	What runs on its own	What asks a technician
Read Only	Every read and live search	No write is allowed
Helpdesk	Every read and live search	Compromise status changes and user changes. Onboarding, roles, alerts and reports are off
IT Admin	Every read, compromises, users, organizations and monitored domains	Role changes, alert and report settings, and deleting an organization
Full Automation	Every read and write	Deleting an organization

See Dark Web ID API for what the agent can read and change.

Getting started

Core

Triggered & Scheduled Agents

Chat Agents

Integrations

Product

Workflows

Customizing Neo

Connecting Dark Web ID to Neo

1. Prepare the API user

2. Add the user in Neo

3. Turn Dark Web ID on per agent

​1. Prepare the API user

​2. Add the user in Neo

​3. Turn Dark Web ID on per agent

1. Prepare the API user

2. Add the user in Neo

3. Turn Dark Web ID on per agent