Scope and guarantees
Audit & Report~3 min
Where the data of an assessment comes from, what stays outside its view and where Audit & Report keeps its data.
What it observes
- The configuration and state of the local node.
- The declared configuration of the VMs and LXCs.
- The state of the storage as Proxmox VE knows it.
- The available history of backups and verifications.
- SMART data and the events the Monitor has collected.
- The state of services, cluster, HA and local sources.
What is outside its view
- The interior of the guests, beyond what they declare to Proxmox VE.
- Network equipment outside the host.
- Remote dependencies the node cannot observe.
- Physical state the hardware does not expose.
- Manual actions or actions of other software, in the change journal.
Missing evidence is not evidence of absence
A source that cannot be read gives an unverified or incomplete result, never a conformant one. The report lists the sources that were not available.
Guarantees of the design
- Stable identifiers for the checks.
- History of runs and findings.
- A validated policy, saved atomically.
- Accepted risks with a reason, visible.
- Attribution of changes to script and function.
- Capture before and after, where it is available.
- An explicit result when something cannot be measured or captured.
Where the data is stored
| Data | Location |
|---|---|
| Policy | /usr/local/share/proxmenux/audit_policy.json |
| Assessments | The audit database of the Monitor |
| Captured objects | /usr/local/share/proxmenux/changes/objects/ |
| Pending entries | /usr/local/share/proxmenux/changes/spool/ |
| Consolidated journal | /usr/local/share/proxmenux/changes.db |
A tool to review, not a certification
Audit & Report reviews, compares and documents the node. Its results are read together with the purpose of the system, the declared policy and the sources available.