Blockchain Transaction Lifecycle Security Standard Audit Framework

previous: Ensure Delivery Capacity | Contents | next: Implement Protected Delivery Paths

Re-verify Application Transactions

Statement of Requirement

Deployers SHOULD re-verify bytecode correctness and access-control safety for Application Transactions before broadcast.

See it in the specification

Applicability

• Deployers who deploy Application Transactions

Purpose

To ensure that the code being deployed is as expected, and as reviewed for security.

Audit Procedure

Verify that the Deployer

• compiles source code supplied in a signed metadata envelope,
• compares the result to the transaction to ensure it is the same code,
• verifies application access-control safety, and
• does not deploy the transaction if there is a mismatch in code generated or insufficient access control

Success Criteria

Application Transactions are only deployed if the source code compiles to produce the exact bytes in the transaction, and the code provides adequate access control

Failure Criteria

Transactions can be deployed without testing that they use the exact source code supplied in the metadata envelope, or without determining that there is sufficient access control in the code to be deployed

Justifiable Exceptions

This is a very useful feature. However, its absence is justifiable on the grounds of keeping code or interfaces simple. Justification for not meeting this requirement does not need to be explicit.

Key Evidence

• Deployment logs
• Security review of transactions, assessing access control safety
• Block explorers showing Application Transactions
• Source Code in metadata envelopes for deployed transactions

previous: Ensure Delivery Capacity | Contents | next: Implement Protected Delivery Paths