Skip to content
English
  • There are no suggestions because the search field is empty.

Add your first device


Summary

CyberHQ.ai reports AI activity through two channels: the endpoint sensor, installed on a device, and the browser extension, installed in the browser. This step completes as soon as either one is reporting from a real device. Install both for full coverage: each sees activity the other can't.

Before you start

  • Both are included on every plan. Blocking on devices and hard blocking in the browser are part of the Professional and Ultimate plans; on Starter, devices report activity but nothing is blocked. Hard blocking in the browser also needs the extension deployed through your browser management.
  • What each one sees. The browser extension sees AI activity in Chrome and Microsoft Edge. The endpoint sensor sees desktop AI apps, command-line tools, other browsers and locally running models, plus clipboard activity, running processes, installed software and privilege events.
  • Permissions. You need the Manage Users or Manage Tenant permission to create enrollment tokens and download the installers.
  • Devices per person are set by your organization's license.
  • Supported systems are listed in Minimum system requirements.

1. Install the endpoint sensor

Go to Capture & devices → Install on devices, and under Install an endpoint sensor choose macOS, Windows or Linux.

Get an enrollment token

Under Generate an enrollment token, set TTL (days) (1 to 90), then either pick the person under Bind to user, or tick Fleet token (no user binding) to use one token across many devices with an MDM. Select Generate enrollment token. You can copy the token at any time from Active enrollment tokens.

  • Generating a new token cancels the previous one for the same person, or the previous fleet token.
  • A fleet token needs each install to supply the person's email.
  • Canceling a token doesn't disconnect devices it already enrolled.

Install on one device

macOS (administrator rights needed): under Manual install (.tar.gz), download the installer for that Mac's chip, then run the command shown under 3. Run this command in Terminal:

tar xzf cyberhq-sensor-<version>-<arch>.tar.gz
cd cyberhq-sensor-<version>-<arch>
printf '%s' '<token>' | sudo ./install.sh --email '<user-email>'

Use --email only with a fleet token. Then select Watch for first heartbeat; the page shows Enrolled: [device name] when the Mac reports.

Windows (administrator approval needed): download Setup.exe (employee) or MSI (IT / MDM).

  • Setup.exe: download the token file from the person's token row, put it in the Downloads folder of the person who will run Setup.exe, then run Setup.exe. A fleet token can't be used with Setup.exe.
  • MSI: msiexec /i cyberhq-sensor-<version>-x86_64.msi SENSOR_TOKEN=<token> /qn, adding TENANT_USER_EMAIL=<email> for a fleet token.

Linux (root needed, x86_64 with systemd): download the tarball, then run:

tar xzf cyberhq-sensor-linux-*-x86_64.tar.gz
cd cyberhq-sensor-linux-*-x86_64/
sudo ./linux-install.sh

Paste the token at the prompt. For a fleet token, add --email <user-email> to the last command.

The person at the device may be asked to approve permissions for the sensor. Approve them so the device can report. Which ones appear depends on what your organization has switched on:

  • macOS: System Extension, Network Extension, network filter configuration, Full Disk Access, CA trust, Accessibility and Notifications.
  • Windows: one administrator prompt when the installer starts.

Install with an MDM

Use a fleet token, and renew it in your MDM before it expires or reaches its Uses limit.

  • macOS (Jamf Pro, Kandji, Microsoft Intune and others): deploy the package from MDM install (.pkg), plus the token and email, using the configuration profile or script from the Install & uninstall guide on the macOS tab. The guide also has a profile that pre-approves some of the sensor's permissions.
  • Windows (Microsoft Intune, Configuration Manager and others): deploy the MSI with msiexec /i cyberhq-sensor-<version>-x86_64.msi SENSOR_TOKEN=<token> TENANT_USER_EMAIL=<email> /qn.
  • Linux: run the installer with your existing automation: sudo ./linux-install.sh --token-file <path> --email <user-email>.

Enrollment is limited to 10 devices every 15 minutes from one network address; the rest retry on their own. See Run a pilot rollout.

Let employees enroll their own device

Turn on Allow self-service enrollment on the same page (this needs the Manage Tenant permission). Employees then enroll by signing in, with no token. Their email domain must be listed under People & access → Sign-in & domains. Choosing Keep self-service enrollment off also completes the Decide on employee self-enrollment checklist step.

2. Deploy the browser extension

  1. Go to Capture & devices → Browser extension, generate the enrollment secret, and copy the compound code. Distribute the compound code, not the secret.
  2. Install the extension: select Add to Chrome for one device, or force-install it across your fleet with the policy files and guides on the page (Google Admin Console, Microsoft Edge management, Windows Group Policy, macOS MDM and Microsoft Intune).
  3. Paste the compound code into the extension.

Confirm it worked

Go to Coverage → Fleet and search for the device. It shows a health status other than Never connected and a recent last seen time.

If it didn't work

  • Token problem: check Active enrollment tokens for an expired or canceled token.
  • A self-enrolled device doesn't appear: check that self-service enrollment is on and the person's email domain is listed under People & access → Sign-in & domains.
  • The extension's settings are grayed out: they need the Manage Tenant permission.
  • A device stops reporting later: see An endpoint sensor isn't reporting.

Related