Reports and comparisons

Audit & Report~6 min

Six documents, each composed for a different question, and the comparison of every run with a reference run.

Six documents, not six styles

The engine selects checks and sections before composing the document. A quick diagnosis is not a full audit with fewer pages, and an inventory presents no assessment results. The sample documents below use fictitious data.

The six documents

Full audit

Documents the node end to end as a technical record.

Checks
Every available check.
Contents
Executive summary; identity and cluster; hardware; network and latency; storage; guests; passthrough; applications; findings with evidence; sources and scope.

Quick diagnosis

Shows what needs attention without the complete inventory.

Checks
The same checks as the full audit.
Contents
Minimal identity; critical findings; warnings; relevant observations; unverified readings and priority actions. Diagrams, inventory and long annexes are left out.

Inventory

Describes what exists on the node without assessing it.

Checks
None; no finding is classified.
Contents
Identity; cluster; CPU and memory; board, BIOS and controllers; network; storage; VMs and LXCs; passthrough; applications and elements managed by ProxMenux.

Security review

Covers exposure and the controls over access to the node.

Checks
The security area, plus container privileges, updates, repositories and the APT chain.
Contents
Identity and cluster; network and latency; access; firewall; 2FA; certificates; privileges; updates; repositories; state and age of Lynis.

Backup assurance

Checks that the declared protection exists and that its backups are usable.

Checks
The backup area, plus storage connectivity and notification delivery.
Contents
Coverage per guest; declared recovery objective; age and result; destination; retention; verification; failed jobs; recovery and incomplete sources.

Capacity and wear

Measures growth margin and signs of exhaustion or ageing.

Checks
The storage and hardware areas, plus memory, swap, journal and the host filesystem.
Contents
Usage and thresholds; thin pools; overprovisioning; memory; inodes; ZFS; temperatures; power-on hours; SMART errors and NVMe/SSD service life.

A document contains the identity of the node and the date of the assessment, the executive result, a summary by area, the structure of hardware, network and storage, the protection of the guests, the findings with their evidence, the sources that could not be read, and the scope and policy applied, in the measure each profile includes them.

Printing or saving as PDF

  1. 1

    Run

    An assessment runs with the profile selected in Report.

  2. 2

    Review

    The finished run shows its findings, the sources it could not read and the policy it applied.

  3. 3

    Generate report

    Generate report opens the view prepared as a document.

  4. 4

    Print

    Print or save as PDF opens the print dialog of the browser, where a printer or Save as PDF is selected.

The printout is a document, not a screenshot

The action bar is hidden, a table that continues on the next page repeats its header, blocks avoid unnecessary breaks and every page keeps the identification and numbering.

Comparing with a reference run

Use as reference marks a finished run as the reference. Later runs are compared with it and their findings are separated into:

GroupMeaning
NewReported now and not before.
WorseStill reported, and graver or reaching further than before.
BetterStill reported, but less grave or reaching less far than before.
ResolvedNo longer reported, and nobody accepted them.
AcceptedNo longer counted because a risk was accepted, not because the host changed.
No longer assessedPresent before and absent from this run; nothing verified that they stopped.
Reference runBehaviour
Setting itAny finished run can be marked; none is marked automatically.
Changing itMarking another run moves the reference without deleting the history.
ComparingWhen no two runs are selected, the comparison uses the reference and the selected or most recent run.
Keeping runsThe 30 most recent runs are kept, and the reference run is never removed.
Without a referenceThe view states that no reference run has been chosen yet, so there is nothing to compare against.

A report describes one moment

An assessment does not certify a whole period. Older results stop describing the current state; the view shows the age of the last run and each source keeps the time it was collected.