Skip to main content

Audit chain

Ciyora keeps a tamper-evident audit log for each tenant.

How it works​

  • Each entry records the event type, the actor, the time and canonical details of what happened.
  • Each entry includes a SHA-256 hash computed over its canonical form and the hash of the entry before it, with a sequence number. Changing or deleting any entry breaks every link after it.
  • Appends are serialised so the chain has one order, and the database refuses updates and deletes of audit entries.
  • Older entries written before the current hash format are anchored by a checkpoint.

Verifying it​

Open Governance > Audit log. The console recomputes the hashes of the entries on screen in your browser and compares them with the server. Verify on server walks the chain from the first entry and shows the full result.

What is recorded​

Approvals and denials with their reasons, access review decisions, break-glass approvals and activations, vault check-outs, identity status changes, JIT revocations and other administrative actions.