The audit trail and the verified seal
Each investigation keeps an audit trail where every record carries the hash of the one before it. Changing any record breaks the chain. The console also compares the copy it reads with the one locked in object storage, so a copy rewritten to look consistent is still caught.
AvailabilityAvailable to everyone with early access to Varqeni.
Steps
- Open an investigation and choose Audit trail.
- Hash chain lists each record with its time, kind and hash.
- Verification lists the checks the console ran on the bundle.
- The seal at the top says Verified against the write-once copy, how many records are in the chain, and how long the stored copy is locked.
- If the locked copy cannot be read just then, the seal says Local copy verified, write-once copy not checked. Varqeni does not act on an incident in that state unless your administrator allows it.
What you should see: The seal line reads, for example, 14 records in the hash chain, Object Lock COMPLIANCE until a date. Local copy verified alone means your installation keeps no locked copy.
What it can and cannot do
Can
- Prove a bundle has not been altered since it was sealed, against the copy locked in object storage.
Cannot
- Repair a bundle that fails verification. It stays as evidence of the failure.
If it does not work
- If the seal says Verification failed or Altered: does not match the write-once copy, see Verification failed on a bundle.
Related articles
- How evidence is sealed and keptEach investigation is sealed with a hash chain and stored write-once for one year.
- Read an investigationOpen an investigation to see the cause of record, the model review, what was ruled out and what a person should do next.
Still stuck? Contact support or email info@fortisdatagroup.com.