Dark Web ID Integration with BMS


This guide is designed for users who want to enable Dark Web ID integration with Business Management Solution (BMS). It walks you through a step-by-step integration process. This integration is highly secured since Dark Web ID and BMS.

Integration Overview

The functionality is a significant Dark Web ID enhancement that leverages integration with BMS.

  • This integration improves customers' ticketing service for compromise.
  • Manage service tickets for all your organizations and customers in one central location.
  • Provide easier workflow for your technicians. When a ticket is created in BMS, a URL in the ticket leads to a dedicated compromise page in Dark Web ID.


  • You must have access to both Dark Web ID and BMS accounts.
  • You must be an admin in both accounts to configure the integration. 

Your Dark Web ID user account must be configured to allow integration access. Please contact support @ darkwebid.com or call 844-ID AGENT, and a customer support representative will help you enable integration access for your user account.

To Get Started

1. Enter your credentials and company name on the BMS page and click LOG IN.


2. You can configure user permission settings by navigating to > Admin > Security > Roles.


3. Once the service ticket is created, you can view it from Service Desk > Tickets. 


Enabling Integration

To enable Dark Web ID integration with BMS, follow these steps:

1. Log in to the Dark Web ID.

2. On the Partner Dashboard page, navigate to the left panel and click Integrations.

3. Click New Integration under the PSA tab to define your ticketing integration.


4. This page shows the available integration services. Select the Kaseya BMS service from the New Integration drop-down menu to start defining your ticketing integration.


5. Select your intended ticketing system. Name your integration on the Create Integration page. It is possible to have multiple integrations of the same type, so we recommend naming them as needed.


6. Enter your Kaseya BMS Information.
Note: If your Organizations are spread out between multiple Kaseya BMS sites, you will need to set up multiple integrations.


7. Once you enter information on the Integration page, click Save. You will see the BMS authentication successful message on the page.


8. Ensure you edit your organization name to match them across both products. The Dark Web ID Organization title should match the BMS company names exactly. Please make sure organization names don't contain leading or trailing spaces.

9. Populate required content as it should map to Kaseya BMS Service Ticket fields. You can use the Dark Web ID Tokens to add context to your service tickets.

Note: One Dark Web ID SMB organization can only be mapped to one BMS service ticket.


Available Dark Web ID Tokens

[uuid] UUID (text) – Dark Web ID’s unique identifier for the Compromise.
[password] Password Hit (text (255)) – The password hit is associated with the Compromise.
[obscured_password] Password Hit (Obscured) (text (255)) – The password hit associated with the Compromise obscured with asterisks after the first four characters.
[record_type] Record Type (text (255)) – The type of record monitored: Email, Domain, or IP.
[source] Source (text (255)) – The record source as reported in Dark Web ID.
[Origin] Origin (text (255)) – The record origin website as reported by Dark Web ID.
[organization_name] Organization Name (text (255)) – The name of the Organization to which the Compromise belongs.
[compromise] Compromise (text (255)) – The record compromise as reported in Dark Web ID.
[password_criteria] Password Criteria (text (255)) – An indication of whether the Compromised Password meets the Organization’s Password Criteria: ‘N/A’ ‘Matches’ ‘Doesn’t Match.'
[search_value] Email Domain / IP Address (text (255)) – The Email or IP Address found by Dark Web ID.
[date_added] Date Added (date) – The date on which the Compromise was added to Dark Web ID.
[date_found] Date Found (date) – The date on which the Compromise was found.

10. Add additional fields as necessary. 

11. Save your Integration: In the lower-right corner of the page, click Save or Save And Submit A Test Compromise for your configuration. This option will populate a service ticket as you've constructed here with test data in your Kaseya BMS platform. If you receive an error upon saving, check your field mapping and try again. Contact support@idagent.com if you experience any unexpected behavior.

Note: You can map a single Dark Web ID SMB organization to BMS per ticket.


Health indicators: There are two Health statuses for Integrations. Healthy, represented by a tick mark, means your most recent integration request was successful! Unhealthy, represented by a cross mark X, means that your most recent integration request was unsuccessful or resulted in an error. This status will persist until a successful integration request is completed.

Note: An integration is marked unhealthy after the fifth unsuccessful consecutive attempt. The error will be shown on the Edit screen.

Status indicators: You can turn your integration on/off using the toggle button. 

You can edit the integration using the edit icon, and the delete icon will completely delete your integration. 


12. Associate Organizations with Integrations: You can edit an existing organization or add a new organization. Organizations can be associated with multiple integrations, and any new SMBs will be dynamically mapped with the company on the BMS side. Still, you must enable integration on the SMB edit page to send compromises for those integrations. A count of associated organizations is displayed in the Integrations table.


13. Enable your Integration: Integrations are turned off by default. You can enable your integration using the toggle button.


After that, all new compromises imported to Dark Web ID will attempt to create a service ticket with the associated platform. Turning off an integration will cease the attempts to generate service tickets with the associated platform.

Note: You can turn your integrations on or off at any time. 

14. Enable Integration on SMB: Once you enable the integration toggle button on the Integrations page, you must enable it on the SMB edit page for compromises to send this SMB organization

  • You can go to the SMB edit page. 
  • You can scroll down to view the Associated Integration section.
  • Select the Kaseya BMS BETA Integration (or given Integration Title) check box and click Save.


You can view the list of active organizations connected to BMS on the Integration page.


Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section