Blockchain Transaction Lifecycle Security Standard Audit Framework

previous: Monitor Delivery Latency | Contents | next: Apply Configured Policies for Deployment

Log Deployment

Statement of Requirement

Deployers MUST log the transaction hash, block number, and confirmation count for all deployed transactions.

See it in the specification

Applicability

• Deployers

Purpose

Ensure records are sufficient for forensic analysis

Audit Procedure

Verify that logs of transactions included in a block include all of

• Transaction Hash
• The number of the block where the transaction is included
• Confirmation count

Success Criteria

When a Deployer has deployed a transaction and reports that it is successfully included in a block, that report includes

• Transaction Hash
• The number of the block where the transaction is included
• Confirmation count

Failure Criteria

Failure to log all transactions deployed successfully automatically fails this requirement.

Logging successfully deployed transactions wittout all the required information of

• Transaction Hash,
• The number of the block where the transaction is included, and
• Confirmation count

fails this requirement.

Key Evidence

• Indexers and blockchain explorers
• Logs provided for Log All Delivery Attempts

previous: Monitor Delivery Latency | Contents | next: Apply Configured Policies for Deployment