Blockchain Transaction Lifecycle Security Standard Audit Framework

previous: Hash Transactions | Contents | next: Validate Inputs

Use Hardened Environments

Statement of Requirement

Producers MUST generate transactions involving sensitive data or key-derived parameters in a hardened environment with memory isolation and process sandboxing.

See it in the specification

Applicability

• Producers

Purpose

Protect sensitive information in transactions from malicious third parties and from accidental exposure

Audit Procedure

• Verify that the Producer allows Users to designate information as sensitive, or a transaction as containing sensitive information, per Enable Transaction Policies for Generation
• Verify that the operating environment that produces those transactions is hardened with memory isolation and process sandboxing

See also Enable Transaction Policies for Generation

Success Criteria

The Producer enables the User to designate a transaction or specific information as sensitive, and restricts processing to a hardened environment

Best Practice

• All operations are carried out in hardened environments
• User-oriented documentation and User Interfaces guide the users to keep sensitive information out of transactions for production, instead using methods such as hashing the information and keeping it offline

Failure Criteria

• There is no mechanism to generate transactions in a hardened sandboxed environment
• Transactions designated as sensitive are not generated in a hardened sandboxed environment

Key Evidence

• User documentation for designating information or transactions as sensitive
• Evidence assessed for Enable Transaction Policies for Generation
• Operational documentation
• Inspection of operational setup

previous: Hash Transactions | Contents | next: Validate Inputs