Skip to main content
DefensX is a browser security platform for MSPs: its browser extension, mobile browser and agent filter each user’s web and DNS traffic by policy, protect credentials and file transfers, and isolate risky pages. Each of your clients is a DefensX customer. Connect it, and Neo agents can answer a user’s request for a blocked site, keep each client’s allow and block lists, and read why a site was blocked.

​
What Neo can do with DefensX

  • User requests: read the ticket DefensX opens when a user asks to reach a blocked site, find the site and the block in the client’s URL and DNS logs, and check its category and risk rating
  • Allow a site: add an approved site to the client’s allow list, then note what was done on the ticket and close it
  • Allow and block lists: add and remove sites in a client’s custom URL groups, and block a phishing site
  • Policies: read a client’s policy groups, link a list to a policy, and create or change policies
  • Logs and reports: read URL, DNS, credential and file transfer logs, top blocked sites and categories, and the cyber resilience score
  • Users, agents and usage: read users, installed agents, browser extensions and your DefensX usage per client
See DefensX API for the permission groups.

​
User requests arrive as tickets

DefensX opens a ticket for each user request through its PSA integration (ConnectWise PSA, Autotask or HaloPSA), set up in the DefensX Partner Dashboard under Integrations. Turn its Ticket Integration on. A ticket title that names the site and the user, such as {{report_type}}: {{hostname}} for {{user}}, saves the agent a log lookup. When the agent closes the ticket, DefensX marks the request resolved if you set that up: on ConnectWise PSA, the two-way ticket closure on the integration’s Tickets tab; on Autotask, the Extension Callout and workflow rule DefensX’s Autotask guide describes. The ticket’s closing status must be the one you chose in DefensX.

​
Your customers are mapped to companies

Neo matches your DefensX customers to the companies in your PSA and keeps the mapping on the DefensX card’s Organization Mapping tab, refreshed on each PSA metadata sync. Matching uses the customer name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Next comes a domain on the DefensX customer that matches a company’s website. Last comes an AI match for the long tail. A name match, or one you confirm, is handed straight to your agents. A domain match or an AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. On a ticket, an agent works in DefensX only on the customer mapped to the ticket’s company. A company with no mapping that agents can use gets no DefensX calls until you set or confirm one on the tab. Agents with no ticket, such as a chat or a scheduled report, reach every customer.

​
Next steps

Connect DefensX

Create a Partner API key and save it in Neo.