Skip to main content
Primo deploys the ThreatDown agent to targeted devices through an MDM control.

​
Platform compatibility

​
Which setup applies to you

Primo deploys ThreatDown in one of two ways:
  • Licence through Primo: Primo sets up and manages ThreatDown on its own tenant. Click Talk to Sales on the ThreatDown card to get started.
  • Your own Nebula tenant: you connect the ThreatDown tenant your company already owns, then Primo deploys the agent through it.

​
Connect your ThreatDown tenant

Skip this section if Primo manages ThreatDown for you.
1

Collect your ThreatDown credentials

In the ThreatDown console, collect three values:
  • Account ID: under Settings > Account information.
  • Client ID and Client secret: create an API client under Settings > Application registration.
ThreatDown shows the client secret only once, when you create the API client. Copy it before you close the dialog.
2

Open the integration

Go to MDM > Settings. In the Integrations section, click Add integration, then click Connect on the Threatdown card.
3

Fill out the form

In Connect your ThreatDown tenant, enter the Account ID, Client ID, and Client secret, then click Connect.Primo checks the credentials and the account before it saves anything. If a check fails, the cockpit shows the reason:
Once connected, Threatdown appears in the Integrations section of MDM settings.

​
Set up the control

1

Go to MDM > Controls > Add new control

Select the EDR - ThreatDown control.
2

Select targeting

Choose which devices to apply the control to: all devices, specific device groups, or a custom target.

​
How it works

Once the control is deployed, Primo automatically installs the ThreatDown agent on targeted devices via MDM. No employee interaction or manual installation is required.

​
Modify or remove the control

Open the control from MDM > Controls to edit or disable it. Disabling stops enforcement but does not remove existing configurations from devices.

​
Disable the integration

Go to MDM > Settings, click the Threatdown row in the Integrations section, then click Disable.
  • If a ThreatDown control is still enabled, Primo refuses. Click See MDM controls and disable the ThreatDown deployment first.
  • If ThreatDown runs on your own tenant, confirm with Disable. Automatic deployment is no longer available in your MDM controls, and devices no longer show the installation status.
  • If Primo manages ThreatDown for you, click Contact us to ask the team to disable it.