Skip to content

Documentation

Glossary

Every LEA Platform term in plain words, in alphabetical order. Each entry links to the guide that explains it in detail.

Action

A named list of commands stored in a rule (in the rule editor under Remediations). A function can pick one action for a failing host; the host runs it on its next check-in. Functions choose among actions; they never send their own commands. See Functions.

Ad-hoc command

A one-off command an administrator runs on one host from the host page → Terminal tab, without creating a rule. It runs as the agent user at the host's next check-in, the output appears on the tab, and you get a notification when it arrives. The AI assistant can propose one too; it runs only after an administrator approves it. See Run a one-off command on a host.

Agent

The LEA agent is the small program installed on each host. It runs the validation commands of its rules and sends the raw output to the LEA server. It never decides pass or fail itself. See Hosts.

Artifact

The output a function produces when it runs, recorded with the run. When a function is set up to feed a remediation, the artifact is handed to the host together with the remedy. See Functions.

Audit log

The record of every configuration change: who changed what, when, and the values before and after. It also records commands run on hosts and actions taken through the AI assistant or tokens. Administrators see it on the Audit page. See Tour of the console.

Break-glass account

A local user name and password that works even when single sign-on is broken. While single sign-on is on, it can only sign in during a time window an administrator opens on the LEA server. Using it raises a critical notification. See Local accounts.

Check-in

The moment the agent contacts the server to collect work and send results. By default this happens every 30 seconds. Commands run from the Terminal tab and remedies are picked up at the next check-in. See Hosts.

Compliance score

A percentage that says how much of your fleet passes its rules. Failures count more when the rule's severity is higher (critical 16, high 8, medium 4, low 2, informative 1). It is shown on the Dashboard; the Compliance rate on the Compliance page is simpler (compliant hosts out of hosts with results). See Compliance.

Control

One requirement of a framework, for example ISO 27001 A.8.2. A rule covers a control when it carries a std:<FRAMEWORK>:<control> tag; the control ID is that last part. See Map rules to controls with std: tags.

Cycle

How often a rule runs on each host, in seconds. The rule editor calls it Interval (seconds). The default is 3600 (one hour). See Rules.

Deployment token

A secret value used once (or a limited number of times) to enroll new agents. A token can put new hosts in a group and activate them automatically. Administrators create tokens in Settings → Deployment tokens. See Agent enrollment.

Drift

The number of host and control pairs of a framework that passed in the previous evidence snapshot and fail in the latest one. One control failing on five hosts counts five. Shown on Reports. See Reports.

Enrollment

How an agent gets its identity: it sends a certificate request with a deployment token and receives a client certificate signed by the LEA server. The Enrollment column on Compliance shows each host's state (for example mTLS enrolled, Certificate error, Probation). See Agent enrollment.

Evidence snapshot

A sealed record, per framework, of the result of every control on every in-scope host at one moment. Each record carries an HMAC (a keyed checksum): a changed record no longer matches it. Anyone who holds the key could recompute it, so it is not a signature that a third party can verify. Snapshots run on a schedule set in Settings → Compliance frameworks, or on demand with Snapshot on Reports. See Reports.

Expectation

The part of a rule that says what the output must contain (re), must not contain (not_re) or which exit code it must have (returncode). Also called an expect block. The server checks the raw output against it with Python regular expressions. A rule without expectations is an informational rule. See Rules.

Framework

A compliance standard such as CIS, ISO 27001, PCI DSS, NIST 800-53, SOC 2 or HIPAA. Rules are mapped to framework controls with tags such as std:ISO27001:A.8.7. See Compliance.

Function

Code that runs on the LEA server (not on the host) when a rule has a result: for example to open a ticket, enrich a failure or compute a host-specific fix. Administrators upload and manage functions in Settings → Functions. See Functions.

Group

Connects hosts to rules. A host runs every active rule of every active group it belongs to. Members can be a static list, All hosts, or a JSONPath expression on host data (a dynamic group). See Groups.

Held rule

A rule that a host still runs in an older version, because a change was rolled out to new hosts only. Held rules are listed on the host, rule and group pages. See Rule updates.

Hook

The link between a rule and a function: when the function runs (on fail, on pass, always), on which output, with which arguments, and whether it may send a remedy or an action back to the host. Set in the rule editor under Functions. See Functions.

Host

A machine (Linux, macOS or Windows) with the LEA agent. A host must be active to be evaluated. See Hosts.

Informational rule

A rule without expectations. It collects data (for example the host name or installed packages) but has no verdict and never affects compliance. Its results show INFO. See Rules.

mTLS

Mutual TLS: both the server and the agent prove who they are with certificates. By default the server only accepts agents that present a valid client certificate issued at enrollment. Certificates renew automatically. See Agent enrollment.

Nested group

A group included in another group, either for its hosts or for its rules. Only one level is allowed: a group that nests others cannot itself be nested. See Groups.

Parameter

A named value substituted into a rule's commands where %name% appears, so the same rule can be tuned per site. Parameters can be fixed values, per-host values, or secrets. See Rules.

Personal access token

A token that lets a script, the LEA CLI or an AI tool act as you, starting with lea_pat_. It has an expiry date and can be revoked at any time. Created in Settings → AI Assistant; tokens for the CLI are listed under account menu → Account settings → Command line. See CLI.

Pin

Two meanings. (1) Pin for quick access (right-click menu) keeps a host, rule or group at the top of the search box. (2) Pinning a rule version holds hosts or a group on a specific version of a rule, for a rollback or a test; see Rule updates.

Probation

The state of a host that re-enrolled through a re-enrollment window. It works normally, but rules with secret parameters are withheld until an administrator checks the host and confirms it. See Agent enrollment.

Remediation

Commands a rule sends to a failing host to fix it (the remedy). After the remedy runs, its output is checked again and the next run re-validates the host. Rules from the library ship with remediation documented but switched off. See Remediation.

Result

One rule on one host: the latest verdict, the raw output (stdout, stderr, exit code), which expectation failed, and the run history. Every result has its own page. See How to read a result.

Return code

The exit code of a rule's command on the host, shown as RC: 0 normally means the command succeeded, any other number means it reported an error. Expectations can check it. See Read results and fix failures.

Rollout

How a change to a rule reaches hosts. All hosts now moves every host to the new version. New hosts only keeps hosts that already run the rule on their current version (held) and gives the new version to hosts that get the rule later. See Rule updates.

Rule

One check, for example "SSH root login is disabled". It has validation commands, expectations, a severity, a cycle, tags and optional remediation. See Rules.

Rule pack

A signed file (lea-rules-<version>.tgz) that delivers new and updated rules, also to sites without internet. Importing a pack never changes running rules: you review and apply changes in Rules → Updates. See Rule updates.

Secret

A sensitive value, stored encrypted. Rules can have secret parameters, which are never sent to hosts in probation. Functions have their own secrets, set in Settings → Functions. See Functions.

Severity

How serious a failing rule is: CRITICAL, HIGH, MEDIUM, LOW or INFORMATIVE. It weights the compliance score. Rules without a severity use the default in Settings → Severity. See Tour of the console.

SSO

Single sign-on: you sign in with your company's identity provider (for example Microsoft Entra ID or Keycloak) instead of a LEA password. Your LEA role comes from the provider. Administrators set it up in Settings → Single sign-on. See Signing in.

Step-up

A request to confirm it is you again before a sensitive change, such as uploading a function or changing a secret. You enter your password or sign in at your identity provider again. See Step-up.

Validation

The commands of a rule that the agent runs on the host. They only read the current state, for example cat /etc/ssh/sshd_config, and send the raw output to the server. See Rules.

Verdict

The outcome of one check: PASS (all expectations met), FAIL (at least one not met), or INFO (no PASS/FAIL verdict: an informational rule, or no usable result yet). See Tour of the console.