Execution

The Compliance page shows one row per host. The Execution page in LEA Platform shows one row per host and rule: the latest result of each rule on each host. Use it to see exactly why a check failed and when it was fixed.

Summary cards

• Total Executions: host/rule result records.
• Verified: results that passed.
• Active: active result records.
• Verification Rate: share that passed.
• Critical Failing: failing results on critical-severity rules.

Filters

Host name search, rule name search, status (All, Verified, Unverified), group, and the same metadata filters as the Compliance page (see Search & filters).

Columns

Click output cells to see the full text. Export results as CSV or JSON.

Verification details

For a failed result, open the details to see:

• return code, status and timestamp;
• each failed expect step: type (for example re for a regex match, not_re, return code), stream (stdout or stderr) and the pattern expected;
• the stdout with a search box that highlights matches.

Example: searching stdout for PASS_MIN_DAYS shows the value is 0, while the rule expects a value from 1 to 365.

Result history

Open the history of any host/rule pair to see how it changed over time. Each entry has a type:

Columns: time, type, status, return code, stdout/stderr. The history shows how long a host stayed non-compliant, when a remedy or manual fix happened, and that it stayed fixed. Results are kept as an append-only history.

Common tasks

Troubleshoot a failed check

1. Filter Status = Unverified.
2. Open the verification details.
3. Compare the expected pattern with the actual output.
4. Decide on the fix: manual, or an opt-in remedy on the rule.

Confirm a fix

1. Find the host/rule pair.
2. Open the history.
3. Check that the latest validation is Verified and note when it changed from Unverified.