Skip to content

Audit Trail

Project -> COMPLY -> Audit Trail provides tamper-evident records for compliance evaluations.

What Is Stored

Each audit entry contains:

  • traceId
  • evaluationId
  • resultSummary (verdict + per-rule summary snapshot)
  • sha256Hash
  • createdAt

Entries are append-only from the product workflow.

Hashing Model

XeroML computes SHA-256 over canonical JSON (deterministic key ordering) of resultSummary. This makes the same logical content produce the same hash every time.

Verify Action

The Verify action recomputes the hash from stored resultSummary and compares it to the persisted hash:

  • Match -> Verified
  • Mismatch -> TAMPERED

Working With Audit Data

  • Filter by trace ID, verdict, and date range
  • Open linked traces directly
  • Expand entries to inspect the exact stored resultSummary
  • Copy hashes for external incident records