Skip to content

Documentation

Compliance (hosts)

The Compliance page lists every host the LEA Platform server knows about, with its current pass/fail status. (The console calls hosts "clients".) For signed audit evidence, see Compliance evidence & reports.

Summary cards

  • Total Clients: all registered hosts.
  • Verified: hosts passing all their rules.
  • Active: hosts that are currently checking in.
  • Compliance Rate: verified hosts as a share of all hosts.

Hosts table

ColumnDescription
Client nameThe host's name
StatusVerified, Unverified or N/A
SeverityWorst severity among the host's failing rules
EnrollmentEnrollment state (see Agent enrollment)
DistributionOS / distribution (Ubuntu, Rocky, Alpine, Oracle Linux, macOS, Windows, ...)
VersionDistribution version
IP addressPrimary IP
Last seenLast agent check-in

Columns can be shown, hidden and resized. Expand a row for quick details: system type, kernel, architecture, internal and public IP, registration time, last seen, agent version.

Filters: text search, status (All, Verified, Unverified, N/A, Active, Inactive), severity, enrollment state, group, and metadata filters (see Search & filters). Bulk actions work on selected hosts or on all hosts matching the filters. Export the list as CSV or JSON.

Client overview

Click a host to open its overview. Tabs:

TabWhat it shows
DetailsName, status, registration and last-seen times, OS, kernel, architecture, IPs, agent version, enrollment and certificate state, and the rules applied with their latest results
ExecutionsEvery rule result for this host: rule, time, return code, pass/fail
Execution LogChronological log of all commands run on the host
Agent LogsLogs sent by the agent, for diagnosing connectivity or permission problems
Live DebugVerbose debug output from the agent while enabled
Live ExecutionRun an ad-hoc command on the host
GroupsEvery group the host belongs to, including through nesting

Live Execution (ad-hoc commands)

  • Admins can send a one-off command to a host without creating a rule.
  • The command runs on the agent's next check-in; the console polls for the result every 5 seconds.
  • You get stdout, stderr and exit code, with search and copy.
  • The server checks each command against a blocklist and an interactive-command policy before sending it. Every request, including blocked and rejected ones, is written to the audit log with the user's name.

Use it to verify a setting or test a command before turning it into a rule.

Common tasks

  • Find out why a host fails: filter Status = Unverified, open the host, check Executions for the failing rules.
  • Troubleshoot an agent: check Agent Logs and Live Debug; check the Enrollment column for certificate problems.
  • Fleet view: filter by distribution, version or architecture to plan upgrades.

Try LEA Platform on your own servers:

Start a free POC

Try it on your own servers.

30 days, up to 25 endpoints, every feature. We help you install it and agree on success criteria first.