edeXa Certify - audit trail infrastructure
An audit trail
nobody can edit.
Immutable audit trail and file integrity monitoring anchored to a Layer 1 blockchain. Tamper-proof timestamps your auditors can verify themselves, while your data never leaves your servers.
The problem
Most audit logs are trusted.
Very few are provable.
Logs guard the system that owns them
If the audit table lives in the same database as the data, anyone with write access can edit both and leave no trace.
Append-only is a setting, not a guarantee
Retention policies and write locks can be reconfigured. What was permanent last quarter can be quietly editable today.
Auditors have to take your word for it
Without an external reference point, an audit trail proves only what the operator of that trail chooses to show.
How it works
Capture, link, anchor, verify.
01
Capture
An event or file version is hashed locally as it happens.
02
Link
The hash is chained to the previous entry, creating an append-only sequence.
03
Anchor
The sequence is committed to the edeXa Layer 1 blockchain with block time.
04
Verify
Anyone can re-hash and compare. Match means intact, mismatch means altered.
Capabilities
Compliance evidence
that verifies itself.
Immutable audit trail
Every event is hashed and linked in sequence, then anchored on chain. Editing history requires rewriting a public ledger.
File integrity monitoring
Scheduled re-hashing detects modification, corruption, and ransomware activity, with the precise moment integrity broke.
Tamper-proof timestamps
Distributed block time replaces server clocks, so the moment a record existed does not depend on your infrastructure.
Independent verification
An auditor or regulator verifies a hash against the public chain without an account, a login, or your cooperation.
Privacy by construction
Only fingerprints leave your environment. Log content, documents, and personal data never move.
Runs alongside what you have
Connect existing storage, SIEM, and document systems. No migration, no retraining, no change to daily workflow.
Where it is used
Wherever "we did not change it" has to hold up.
ISO 27001 and SOC 2 evidence
Logging and integrity controls auditors can test themselves rather than accept on trust.
Financial and regulatory records
Retention with provable non-modification for supervisory and tax review.
Healthcare and research data
Study data, consent records, and clinical files fixed in time without exposing content.
Security and incident response
Forensic timelines that hold up when the attacker had administrator access.
Questions
Straight answers.
What makes an audit trail immutable?
It is immutable when nobody, including a database administrator, can change or remove an entry without detection. edeXa anchors each entry's hash on a Layer 1 blockchain, so any edit breaks the anchored value and becomes provable.
How does blockchain file integrity monitoring work?
Files are hashed inside your environment and the hash is anchored on chain. Scheduled re-hashing compares current state against the anchored value, detecting tampering or corruption and pinpointing when it happened.
Does this help with ISO 27001 or SOC 2?
Yes. Both require reliable logging and evidence that records were not modified. An anchored trail lets auditors verify integrity directly instead of relying on your assurances or a vendor's.
Is our log data stored on the blockchain?
No. Only one-way fingerprints and timestamps are anchored. Log contents and files stay in your systems, which keeps confidentiality and GDPR obligations intact.
What happens if we stop using edeXa?
Existing anchors remain on a public ledger and stay verifiable. Your proof does not expire with a subscription.
Next step
Anchor your first 10 records free.
A 15-minute technical walkthrough covers connectors, hashing intervals, and what independent verification looks like to an auditor.
Engineered by edeXa AG, Vaduz, Liechtenstein.