Blockchain Transaction Lifecycle Security Standard Audit Framework

previous: Present Readability-optimised Information | Contents | next: Communicate Transaction Data Securely

Maintain Transaction Integrity

Statement of Requirement

A transaction's payload and metadata MUST NOT be changed except:

• a Producer MAY create a new transaction by modifying an indexed transaction
• a Signature Manager MAY add signatures and signing metadata
• a Deployer MAY set gas or fee values and add deployment metadata

See it in the specification

Applicability

All Roles

Purpose

Reduce the risk of transactions being altered in ways that could have undesirable consequences

Audit Procedure

Verify that the actor does not change the semantics of transactions

Success Criteria

There are no changes to the semantics of transactions other than those that are allowed by the requirement, and are necessary for correct operation

For example, a Producer creating a new transaction by modifying an indexed transaction is allowed. This is necessary for correct operation, but still needs to pass relevant requirements such as Reject Unauthorized Construction

Failure Criteria

The semantics of transactions are changed unnecessarily, or in a manner other than those allowed by the requirement.

Justifiable Exceptions

• a Producer MAY create a new transaction by modifying an indexed transaction
• a Signature Manager MAY add signatures and signing metadata
• a Deployer MAY set gas or fee values and add deployment metadata

Key Evidence

• Logs
• Transactions processed
• Reperformance

previous: Present Readability-optimised Information | Contents | next: Communicate Transaction Data Securely