Blockchain Transaction Lifecycle Security Standard Audit Framework

previous: Require Strong Authentication | Contents | next: Retain Logs

Tamper-Proof Logs

Statement of Requirement

Logs MUST be immutable or tamper-evident (e.g., append-only store, hash-chaining, write-once-read-many (WORM) or immutable object storage, or external log attestation)

See it in the specification

Applicability

All roles

Purpose

Ensure that logs provide reliable information for auditing

Audit Procedure

Verify that logs are stored in a tamper-evident or immutable manner

Success Criteria

• Logs are stored in a tamper-evident or immutable manner

Best Practice

Logs are written to write-once-read-many (WORM) or immutable object storage, with the retention period enforced by the storage rather than by the application that writes to it.

Failure Criteria

• There is a log that can be changed without leaving a record of the change
• Logs needed to audit another requirement are no longer available for the period under audit

Key Evidence

• Logs
• Log retention configuration
• System documentation

previous: Require Strong Authentication | Contents | next: Retain Logs