Audit log and integrity proof
The Audit log stores, per organisation, the actions performed on the platform: who did it, what, on which record and when. Each entry is chained to the previous one by a hash, so altering or deleting an old entry breaks the chain.
Who has access
The page and the integrity proof are available to the ADMIN and AUDITOR roles. Other roles have no access.
Filters and export
- Filters: model (the type of record affected), action, date range (From / To) and free-text search by model, action or user. Clear restores the full list.
- Export: choose the CSV or PDF format and click Export.
Integrity proof
The Integrity proof button generates a ZIP file that an auditor can verify outside EterShield, without depending on the platform. It contains:
| File | Contents |
|---|---|
entries.jsonl |
The log entries, one per line, with the fields that go into the hash |
anchors.json |
The anchors that cover those entries, with the verification path to the root (only your organisation's data) |
anchors/<id>.tsr |
The timestamp (RFC 3161) of each anchor, issued by an external authority |
manifest.json |
Identification of the organisation, the interval covered, the algorithms used and the checksum of each file |
README.txt |
Verification instructions |
What it proves: (1) that no entry was altered or deleted within the interval; (2) that each entry already existed, exactly as it is, at the time of the timestamp.
How far it goes: the proof ends at the last anchored entry. Anchors are created every hour, so the most recent actions only enter the next proof. If the organisation does not yet have any timestamped anchor, the platform shows "Could not generate the proof" with the message "there is no timestamped anchor for this organisation yet"; try again later. There is a limit of 5 proofs per minute per organisation. Each proof generation is itself recorded in the audit log.
How to verify
- Download the verifier at
<platform URL>/trust/verify-audit-proof.mjs(public, no session required). It is a single file, using only native modules from Node.js 18 or later, and can be read before you run it. - Run:
bash
node verify-audit-proof.mjs prova.zip
This confirms the checksums, the hashes and the chaining of all entries, the paths to the root and that each timestamp is over the right anchor.
- To also validate the signatures of the timestamping authority, add
--ca <file with the authority's CA>(requiresopensslto be installed). If the authority's certificate is supplied separately, also use--untrusted <certificate>. The--jsonoption returns the result in a machine-readable format. - Read the last line: "RESULT: VERIFIED" (exit code 0) means everything checks out; "RESULT: FAILED" (exit code 1) indicates problems, listed beforehand as "PROBLEM". Without
--ca, the verifier warns that the timestamp signature was not verified.
The
README.txtinside the ZIP also explains how to verify a timestamp by hand withopenssl ts -verify.