Blockchain Transaction Lifecycle Security Standard Audit Framework

previous: Retain Logs | Contents | next: Document PII Handling

Minimize Personal Information Exposure

Statement of Requirement

All Roles SHOULD minimize the exposure of Personally Identifying Information (PII)

See it in the specification

Applicability

All roles

Purpose

Protect Personally Identifiable Information from malicious third parties, supporting user expectations and legal requirements about privacy

Audit Procedure

Verify that PII is managed securely, only exposing the information to parties who have an operation need to access it.

Success Criteria

Logs are stored in a tamper-evident or immutable manner

Best Practice

• Store all PII data separated from standard logs, with an additional access control layer.
• Apply the Principle of Least Privilege and Role-based Access Control specifically to PII data.

Failure Criteria

• Logging records Personally Identifiable Data (PII) as a standard entry
• There is no data-labelling or sanitisation to identify PII

Justifiable Exceptions

It is reasonable to expose data when explicit informed consent has been given to expose an individual's data, for example for a marketing campaign, or where there is a specific legal requirement such as a taxation regulation or court order.

The consent or the legal direction, and the purpose, need to be documented, for any such case.

Key Evidence

• Logs
• Operational documentation

previous: Retain Logs | Contents | next: Document PII Handling