Zorus Portal Setup
      Back to home
      1. Help Center
      2. Setup Guides
      3. Zorus Portal Setup

      ThreatLocker Configuration

      When installing the Zorus Agent with ThreatLocker already installed, there's a possibility it may try to block the application from running or from creating a connection to our policy servers. We've worked directly with ThreatLocker to address this and as a result, they have added us to their Built-In list of supported applications.

      To ensure that ThreatLocker doesn't deny the Zorus Filtering software, please apply the Built-In Application policy at the "Entire Organization" level if used on all machines within a tenant, or the "Global" level for multi-tenant.

      ThreatLocker Policy Hierarchy

      See screenshot below.

      1-1

      2-1

      Zorus MSP CyberSight Browser Extension:

      In order for our CyberSight Browser extension to install and function properly, you will need to add a few Application policies to your Organization (or group) policy.

      You will need to add the following:

      • Zorus (Built-in)
        • This allows our Agent to be installed.
      • Browser Extension MSP CyberSight: Chromium Ext MSP CyberSight(Built-in) [This handles Chrome, Edge, and Brave], Firefox Extension MSP CyberSight (Built-in).
        • This allows our extension to be installed in the browser.
      • Browsers: Google Chrome (Built-in), Microsoft Edge Chromium (Built-in), Mozilla Firefox (Built-in), Brave Browser (Built-in).
        • This allows the browser extension to communicate with our servers and report back to the portal.

      4

      The red box indicates all the applicable browser policies, as they're listed in "Suggested Policies" for ThreatLocker. The Yellow box indicates the added software policies for the most optimal compatibility between ThreatLocker and Zorus.

      Troubleshooting Network Ringfencing (Recommended by Threatlocker):

      You will want to enable the 'EnableDriverDomainNameParsing' option within the organization settings.
      Once this has been enabled, please restart the ThreatLocker agent on the affected device(s) from the Computers page. When this is completed, next time this denies you should see a FQDN in the audit next to the denied IP addresses.
      Once we are the domain logged in the audit, you will want to exclude that domain on the Internet Ringfencing portion of your PowerShell policy. Please let me know if you have any further questions regarding this process.