Device Security
Device Security tells you whether the laptops your people work on are patched, encrypted, firewalled, protected against malware and free of known-vulnerable software — the five controls Cyber Essentials asks about — and ties every device to the person and the asset it belongs to.
It is a separate module from Security Awareness, billed at the usual per-user module price.
What it measures
Every device is scored on nine checks, grouped under the Cyber Essentials controls:
| Check | Control | |-------|---------| | Operating system still supported | Patch management | | Operating system updates installed | Patch management | | Browser up to date | Patch management | | No known-vulnerable software | Patch management | | Firewall switched on | Firewalls | | Disk encrypted | Secure configuration | | Screen locks when idle | Secure configuration | | Malware protection active | Malware protection | | Day-to-day account is not an administrator | Access control |
A check is pass, fail or unknown. Unknown means nothing could see that check on that device; it is shown as a gap in coverage, never counted as a pass.
Known-vulnerable software follows the Cyber Essentials patching rule: a device fails only when installed software has a vulnerability rated high or critical (CVSS 7 or above). Fleet's free edition reports which CVEs affect a device but not how severe they are, so on it a device with CVEs shows as unknown, with the count, rather than as failing.
Where the evidence comes from
The Luna agent (Fleet). The full picture. Luna uses Fleet, an open-source device management tool built on osquery, as the agent. Your company gets its own Fleet instance; Luna connects to it, adds its checks as Fleet policies, and reads every enrolled device once an hour. Fleet also reports installed software and matches it against known vulnerabilities (CVEs).
Microsoft Intune. If you already manage devices in Intune, connect it under Admin → Integrations and Luna reads every managed device hourly: its operating system version and whether its disk is encrypted. See Connecting Microsoft Intune. Fleet and Intune can both report on the same laptop; it is still one device.
Sign-ins. Whenever someone opens Luna, the browser reports which operating system and browser it is. That gives two checks with nothing to install, labelled as coming from the sign-in because the browser is reporting on itself.
Self-confirmation. Every 90 days each employee answers six yes / no questions about the machine they work on, from their Security page. This covers the checks a browser cannot see, and personal devices the agent is not on.
Where more than one source reports on the same device, Luna combines them check by check: each check takes its answer from Fleet if Fleet could see it, then Intune, then the holder's confirmation, then the sign-in. So the agent's firewall result stands even if the confirmation says otherwise, but a screen-lock answer the agent cannot check on Windows comes from the confirmation. Each check on the Device Security page says which source it came from.
Evidence also has to be current to count. A device that has not checked in to the agent, or signed in, for 30 days, a confirmation older than 90 days, or agent data Luna has not been able to re-read for two days (for example after disconnecting Fleet) all count as unknown, and the device is marked Nothing current.
Setting it up
- Turn on the module under Admin → Modules.
- Stand up Fleet. Luna provisions one Fleet instance per company; if you run your own, that works too. Your Luna contact will give you the address.
- Connect it. Admin → Integrations → Fleet. In Fleet, create an API-only user with the Admin role and paste its token. Luna checks the token, creates its policies (all named
Luna: …) and reads the enrol secret. - Enrol laptops. Admin → Device Security → Enrol devices gives you a
fleetctl packagecommand per platform. It builds an installer; run that installer on each laptop. The device appears within the hour.
How devices get linked to people
Fleet reports each device's serial number. If an asset in the Assets module has that serial number, the device is linked to the asset and so to whoever holds it. That is the whole mechanism, and it is why serial numbers on assets matter.
Where there is no serial match, Luna tries the email address Fleet Desktop reports for the signed-in user. Anything still unmatched appears under Unlinked on the Device Security page, with a "Link to asset" action. A link made by hand is never overwritten by a later sync.
If a retired or disposed asset shares its serial number with one still in service, the device is matched to the one in service. If two in-service assets share a serial number, Luna matches the device to neither and lists the serial under Asset register until one is corrected.
When an asset changes hands (assigned, checked out, checked in, returned during offboarding), its devices follow the new holder straight away. The previous holder's confirmation for that laptop is removed, and the new holder is asked to confirm it themselves. Deleting an asset removes its confirmations and unlinks the agent's record of it, which the next sync matches again by email if it can.
The readiness view
Admin → Device Security shows:
- The five controls — pass, fail and unknown counts per check across every device.
- Devices — every device, worst first, with the checks that fail and the vulnerable software Fleet found.
- Unlinked — enrolled devices nobody is linked to.
- Not covered — people with nothing current on record from any source.
- Asset register — where the agent and the register disagree: retired or disposed laptops still checking in, laptops used by someone other than their holder, and serial numbers carried by more than one asset. Retired and disposed laptops are left out of the score.
- Enrol devices — the installer commands.
On an asset's detail sheet, a Device posture section shows the same checks for that asset.
Notifications
When a check newly fails on a device linked to someone, they get a notification with what to fix and a link to their device page, and so does their line manager. A line manager who is not an admin gets the notification without the link, since the readiness view is admin-only. A check that stays failing does not nag again. The category is Device security on the Notifications page.
If the company stops paying for Device Security, the Fleet connection stays but the sync pauses: nothing is read from Fleet and nobody is notified until the module is back.
Employees reach their devices from a card on the Security Awareness page. A company with Device Security but without Security Awareness gets a My Devices item in the sidebar instead.
What it does not do
Luna reports and chases; it does not change devices. There is no remote wipe, no forced update and no script execution. Fleet itself can do some of that, from its own console, if you choose to.