Luna HR Docs

Setting up Fleet

Fleet is the agent behind the Device Security module. Each company gets its own Fleet instance; this guide takes you from a running Fleet to laptops reporting into Luna.

Before you start

  • The Device Security module is on under Admin → Modules.
  • You have the address of your Fleet instance, for example https://fleet.yourcompany.co.uk. Luna provisions one per customer; if you run your own Fleet, that works too.
  • You can sign in to Fleet as an admin.

1. Create an API user for Luna

In Fleet: Settings → Users → Create user. Give it a name like "Luna HR", the Admin role, and tick API-only user. Fleet shows the token once; copy it. API-only tokens do not expire.

2. Connect from Luna

Admin → Integrations → Fleet → Connect. Paste the Fleet address and the token.

Luna checks the token, then adds its checks to your Fleet as policies named Luna: … (disk encryption, firewall, malware protection, screen lock, updates, admin rights, per platform). It also reads the enrol secret and starts the first sync. The card shows the instance it connected to and when it last synced.

3. Enrol laptops

Admin → Device Security → Enrol devices shows a command per platform, for example:

fleetctl package --type msi --fleet-url https://fleet.yourcompany.co.uk --enroll-secret <secret> --fleet-desktop

Run it on any machine with fleetctl installed to build an installer (an .msi for Windows, .pkg for macOS, .deb for Linux), then install that on each laptop. The agent is signed, updates itself, and reports in every few minutes.

Within the hour the device appears under Admin → Device Security → Devices.

Luna links a device to a person through the Assets module: the device's serial number is matched to an asset's serial number, and the device is reported against whoever holds that asset. Two things make this work well:

  • Put serial numbers on your laptop assets. Settings → Assets, or the asset's edit sheet. A match is automatic from the next sync.
  • Fleet Desktop (the --fleet-desktop flag) lets the signed-in person identify themselves on the device; Luna uses that email as a fallback.

Anything still unmatched is listed under Unlinked with a "Link to asset" action. A link you make by hand is never overwritten.

5. Optional: webhook

The hourly sync is all that is needed. If you want failing checks to reach Luna within minutes instead, copy the webhook path from the Fleet card (it looks like /api/fleet/webhook/…) and in Fleet go to Settings → Organization settings → Automations, enabling the failing policies and vulnerabilities automations with that URL on your Luna domain. Luna treats the call purely as a prompt to re-sync; nothing in the body is trusted.

Disconnecting

Admin → Integrations → Fleet → Disconnect. Luna stops reading. Devices stay enrolled in Fleet. The readiness view keeps the devices listed, but two days after the last successful read their agent checks stop counting and show as unknown, so an old snapshot is never mistaken for a current pass. Reconnecting brings them back on the next sync.

What Fleet can see

Fleet reads system state through osquery: operating system and version, whether the disk is encrypted, whether the firewall and malware protection are on, which user accounts are administrators, and the list of installed software with versions. It does not read files, browsing history or messages. Luna stores the check results, the OS version and the vulnerable-software list; it does not store the full software inventory.