Zorus

Zorus (Zorus CyberSight, now part of DNSFilter) filters the web traffic on your customers’ endpoints. Connect it once with an API token from your Zorus portal, and Neo agents can read and act across your Zorus customers.

​

What Neo can do with Zorus

• Count each customer’s Zorus endpoints: installed, filtering, CyberSight and network seats, for a QBR or a billing check
• List a customer’s endpoints and find the ones in error, offline or not filtering
• Triage an unblock request ticket: find the user’s request, check the site, why Zorus blocked it and its categories, and hand your technician a recommendation with the steps to approve or deny it in the Zorus portal
• Restart the filtering service on a device that stopped filtering, or enable it again
• Isolate a device a security alert says is compromised, and release it
• Create the deployment token that installs Zorus on a new device, for your RMM’s install script
• Read groups and policies, and create customers and groups

​

Each ticket stays with its customer

One Zorus token reaches every customer its user can see. On a ticket that names a company, Neo sends a call only for the Zorus customer the ticket’s company is mapped to. An endpoint action or a deployment token names that customer, and Neo first reads the endpoint or group to confirm it belongs to it. Creating a new customer happens only outside a ticket run, such as from a chat with Neo.

​

Disabling an endpoint always asks first

Disabling an endpoint turns its web filtering off, so it always waits for a technician’s approval, whatever the agent’s settings.

​

Your customers are mapped to companies

Neo matches your Zorus customers to the companies in your PSA and keeps the mapping on the Zorus 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). Last comes an AI match for the long tail. Zorus names the customer in each unblock request email ({Customer Name} Requests to Unblock Domain), so keeping the Zorus and PSA names the same also routes those tickets to the right company. A name that matches exactly one of your PSA companies, as it is or after stripping a legal-form suffix, or a match you confirm, is handed straight to your agents. A name two of your PSA companies share, or two Zorus customers that match one company, is left to the AI match, and an AI match waits for you on the Organization Mapping tab. Confirm or correct each there. 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. See Zorus API for the permission groups.

​

Next steps