Skip to content
Getting started guide

From sign-up to your first AI event

Six steps, the same ones the setup screen walks you through.

You need a Windows endpoint where you can install software as administrator. Chrome or Edge adds content checks on supported AI sites, and a Wazuh manager is optional.

Last updated: September 2026

Take the product tour

What you need before you start

  • Required

    A Windows endpoint and administrator rights on it

  • Recommended

    Chrome or Edge, for paste, send and upload checks on supported AI sites

  • Optional

    A Wazuh manager, to see AI decisions as Wazuh alerts

Setup steps

  1. 1Step 1 of 6

    Create your account

    Join the waitlist with your work email. When your early access opens, your workspace is created with every module switched on.

    • Use a work email your team can reach you on
    • Invite your team later, each with the role they need
    • Two-factor authentication is available for every account
    Illustrative sample data

  2. 2Step 2 of 6

    Name your organisation, and connect Wazuh if you use it

    Setup opens on your organisation: its name, industry, size and timezone, used to label your workspace and reports. The next screen offers to connect a Wazuh manager. It is optional, and you can skip it and add it later.

    • Organisation name, industry, company size and timezone
    • Wazuh: the manager API address (usually port 55000), an API user and TLS verification
    • Everything here can be changed later in Settings
    Illustrative sample data

  3. 3Step 3 of 6

    Install the EndSecure AI Sensor on a Windows endpoint

    Name the endpoint, then download the installer and run it as administrator. The console gives you a single-use enrollment token, shown only once, and a silent install command for administrator PowerShell if you prefer. The sensor runs as a Windows service next to the Wazuh agent, and the two are independent.

    • Download EndSecure-AI-Sensor.msi from the setup screen
    • Enter the server address, the endpoint name and the enrollment token when asked
    • For content checks in the browser, add the EndSecure extension to Chrome or Edge and enrol it from its options page with a one-time token
    Illustrative sample data

  4. 4Step 4 of 6

    Choose how AI data is governed

    Pick a template to start from. Every rule can be changed later in Policies, and every change is recorded in the audit log. If you are not ready to block anything, start with Monitor only: policies are evaluated but not enforced, and each event shows what it would have done.

    • Balanced (recommended): discover AI use, warn on sensitive data, block critical exposure such as secrets and credentials
    • Strict: block personal, customer, financial, credential, secret and source-code data sent to AI tools that are not sanctioned
    • Monitor only: discover and report, nothing is blocked or redacted
    • Custom: keep your current policies and build your own rules
    Illustrative sample data

  5. 5Step 5 of 6

    Verify the endpoint reports

    The verify screen checks each part of the chain and updates as the sensor checks in. When the endpoint and sensor are connected, AI discovery is ready on that device. If something is missing, the check tells you which part.

    • Endpoint connected
    • Sensor connected, with its heartbeat
    • Wazuh connected (only if you set it up)
    • AI discovery ready
    Illustrative sample data

  6. 6Step 6 of 6

    Open the Security Console and watch

    Setup ends in the Security Console. From here, add more endpoints the same way, review the AI inventory as tools appear, and invite your team with the role each person needs.

    • Endpoints, AI applications, cloud AI services, local LLMs, active policies and sensor health at a glance
    • Invite teammates as Admin, Security Analyst or Viewer
    • Mark each AI tool as approved, unreviewed or blocked as it appears
    Illustrative sample data

After setup

Roll out gradually

Install on a few endpoints first, keep Monitor only on while you learn what people use, then move to Balanced or Strict.

Day 30

The console becomes read-only and your data is kept. Activate a licence to continue exactly where you left off.

Removing the sensor

Uninstall "EndSecure AI Sensor" from Windows Settings, or run msiexec /x with the MSI. The Wazuh agent is not affected.

Setup questions

What EndSecure does, what it doesn’t, and how it fits with your tools.

See all questions
How do I install the sensor?
Download EndSecure-AI-Sensor.msi from the console and run it as administrator on the Windows endpoint, or use the silent install command the console shows you. Each install uses a single-use enrollment token, which the setup screen shows only once.
How long does setup take?
Setup is six short steps: name your workspace, optionally connect Wazuh, install the sensor, choose a policy template, verify the endpoint and open the console. Once a sensor reports, AI discovery starts on that endpoint.
Which operating systems and browsers are supported?
The EndSecure AI Sensor is a Windows service. The browser extension works in Chrome and Edge on supported AI sites. Other platforms are not supported today.
Do I have to write policies from scratch?
No. Setup offers three templates. Balanced discovers AI use, warns on sensitive data and blocks critical exposure such as secrets. Strict blocks sensitive data sent to AI tools that are not approved. Monitor only discovers and reports without blocking anything. Every rule can be changed later, and changes are recorded in the audit log.
How do I remove the sensor?
Uninstall “EndSecure AI Sensor” from Windows Settings, or run msiexec /x with the EndSecure-AI-Sensor.msi package. The Wazuh agent is not affected.

Ready when you are

Create a workspace and install the sensor on one endpoint. If you would rather do it together, we can walk through setup with you.

Join the waitlist

We are onboarding early customers. Join the waitlist to get early access.