Skip to content

Documentation

Start here

This guide explains what LEA Platform does, the words it uses, and what to look at in your first hour in the console.

What LEA Platform does

LEA Platform checks that your servers and workstations are configured the way your security policy says they should be. A small program on each machine, the LEA agent, regularly runs read-only commands (for example, it reads a configuration file) and sends the raw output to the LEA server. The server compares that output with what the policy expects and decides whether the check passed or failed. The console shows you the results for every machine, lets you drill into any failure, maps checks to compliance frameworks (such as CIS or ISO 27001) and produces reports for auditors. Optionally, LEA can also fix a failing machine automatically.

The words you need

WordWhat it means
HostA machine (Linux, macOS or Windows) that runs the LEA agent.
LEA agentThe program on each host. It runs the checks and sends the raw output to the server. It does not decide pass or fail.
RuleOne check, for example "SSH root login is disabled". A rule has commands, expectations, a severity and an interval.
ValidationThe read-only commands of a rule that the agent runs on the host.
ExpectationWhat the output must (or must not) contain for the rule to pass. The server evaluates it. Also called an expect block.
VerdictThe outcome of one check: PASS, FAIL or INFO (no PASS/FAIL verdict: a rule that only collects information, or no usable result yet).
ResultOne rule on one host: the latest verdict, the raw output and the run history.
GroupConnects hosts to rules. A host runs every active rule of every active group it belongs to.
RemediationCommands a rule can send to a failing host to fix it. Off unless someone turns it on.
FunctionCode that runs on the LEA server when a rule has a result, for example to open a ticket.
FrameworkA compliance standard (CIS, ISO 27001, PCI DSS, NIST, ...). Rules are mapped to its controls.

All other terms are in the glossary.

How the pieces fit

  Host                          LEA server                         Console (your browser)
  ----                          ----------                         ----------------------
  LEA agent runs the rule's     compares the output with the       shows PASS / FAIL per host,
  read-only commands     --->   rule's expectations          --->  rule and framework; reports,
  (e.g. cat a config file)      and stores the verdict             notifications, history
        ^                              |
        |                              |  only if remediation is turned on for that rule
        +------------------------------+  (fix commands sent back to the failing host)
  • Which rules a host runs is decided by its groups.
  • How often a rule runs is set per rule (its interval, one hour by default).
  • The agent never sends anything except raw command output and its own logs. The decision always happens on the server, so a rule can be changed centrally without touching any host.

Your first hour

Follow these steps in order. Each step names exactly where to click.

  1. Sign in. Open the LEA Platform address your administrator gave you. Click Sign in with your company's identity provider, or Sign in with a local account if you were given a local user name and password. You should see: the Dashboard.
  2. Look at the Dashboard. It shows the overall compliance score, the trend, the failing rules and the health of your hosts. Click any number or bar to see the hosts or rules behind it.
  3. Open Compliance. Click Compliance in the left sidebar. You see every host with its status: COMPLIANT, NON-COMPLIANT or NO RESULTS. Click the Non-compliant number in the summary row to show only hosts with failures.
  4. Open a failing host. Click a host name. A preview panel opens on the right. Click Open page (or Ctrl/⌘-click the name) to open the full host page. You should see: tabs Overview, Rule results, Run history, Agent logs, Terminal, Groups and Held rules.
  5. Read a result. On the Rule results tab, click a rule that shows FAIL. The result page shows the Last check: the raw output (stdout and stderr), and which expectation failed. Compare the output with the expectation to understand why it failed. See How to read a result.
  6. Find the rule. On the result page, click the rule name (or Full definition under What is checked). The rule page shows what the rule checks, on which hosts it passes and fails, and its definition.
  7. See which group assigns it. On the result page, look at Assigned via under Track record: it lists the groups that put this rule on this host. On the rule page, the Groups tab lists every group that uses the rule.

Tip: Press Ctrl K (Windows/Linux) or ⌘ K (Mac) at any time to search for a host, rule, group or page by name.

Common tasks

TaskStepsGuide
Add hostsCreate a deployment token in Settings → Deployment tokens, install the agent with it, activate the host if the token does not do it automatically, and put the host in groups (or let an All hosts or JSONPath group pick it up).Add and manage hosts
Roll out a new checkCreate the rule or add it from the library, assign it to a small test group, check its results on Execution, then add it to your production groups.Write and edit rules, Groups
Investigate a failureOpen the result of the rule on the host, read the output and the failed expectation, look at the run history, then fix the host (or the rule, if the rule is wrong) and wait for the next run.Read results and fix failures
Prove complianceTurn on the framework in Settings → Compliance frameworks, let snapshots run (or take one), and download the report from Reports.Reports and evidence

Where to get help in the console

WhereWhat it does
Help button in the top barOpens help for the page you are on.
Documentation in the left sidebarOpens all guides, including this one.
Search in the top bar, or Ctrl/⌘ KFinds hosts, rules, groups, frameworks, pages and guides.
AI Assistant (sidebar, and a floating button on every page)Answers questions about your own data, for example "why is this host failing?". Only shown when an administrator has turned it on in Settings → AI Assistant.

When something is broken, start with Troubleshooting. Quick answers are in the FAQ.

Roles: what administrators can do

Every person has one or more of six built-in roles. The role comes from your identity provider (single sign-on), from a grant an administrator gave you, or from your local account. A role can be limited to some host groups; you then only see and work on the hosts in those groups.

You can...ViewerAuditorOperatorEngineerAdministratorIntegration
See the Dashboard, Compliance, Execution, Rules, Groups and ReportsYesYesYesYesYesYes
Open host, rule, result and group pages, preview panels and searchYesYesYesYesYesYes
Change your own notifications, theme and preferences (account menu → Account settings)YesYesYesYesYesNo
Read agent logs and use the AI assistantYesYesYesYesYesNo
Generate compliance reports with evidenceNoYesYesYesYesYes
See the Audit pageNoYesNoNoYesNo
Handle notifications, run remedies, manage hosts, run commands (Terminal tab)NoNoYesYesYesNo
Create, edit or delete groups, assign rules to groups, remove resultsNoNoYesYesYesNo
Create, edit or delete rules, see secret rule parameter valuesNoNoNoYesYesNo
Settings: sign-in, access, tokens, license, backups, integrations and the clusterNoNoNoNoYesNo
Can be limited to some host groupsYesNoYesNoNoYes

Viewer (read), the older name of Viewer, gives the same access as Viewer. Integration is meant for programs such as a SIEM or CMDB. The full list is in Access: roles and scopes.

If a button described in a guide is missing for you, your role does not include it, or the item is outside your host groups. Ask an administrator.