Q-Cyber Magazine

Fintech · 22 April 2026 · 3 min read

Permissioned ledgers: Start from a reference architecture, not a slogan

ISO 23257:2022 provides a published reference architecture for distributed ledger and blockchain systems; permissioned deployments should be designed against that architecture, with identity, key custody and legal duty made explicit.

Abstract graphic of stacked isometric blocks in Knowlcom blue

"Enterprise blockchain" is not a standard. A distributed ledger is a design choice, and it should be described in a language that engineers, auditors and regulators can share. ISO 23257:2022 is that language.

Why a reference architecture helps

Permissioned systems differ from public, open-participation networks in a basic governance fact: who may operate a node, who may submit a transaction, and who may read the record are decided by an authority or a consortium. That fact does not, by itself, make the system sound. Identity, key custody, change control, and the legal status of the recorded data still have to be designed. ISO 23257 exists to name the components and roles involved in that design, rather than leaving each project to invent its own vocabulary.

This article will not reproduce the standard's internal diagrams, which ISO publishes as a copyrighted document. The official abstract is sufficient for a planning point: projects should be able to point to the functional components, roles and relationships they have chosen, and to the cross-cutting concerns they have accepted, in terms an independent reviewer can recognise.

Exhibit 1

ISO 23257 publication and review status

  1. 30 January 2018

    New project approved in ISO/TC 307

  2. 8 February 2022

    ISO 23257:2022 published (Edition 1, 52 pages)

  3. 28 October 2025

    Stage 90.92: international standard to be revised; a successor project, ISO/AWI 23257, is under development

Source: ISO, ISO 23257:2022 catalogue entry, https://www.iso.org/standard/75093.html, including the official life-cycle dates.

Ledgers do not cancel other duties

A permissioned ledger that records personal data is still processing personal data. A ledger used to move or hold virtual digital assets may bring the operator into FIU-IND's 10 March 2023 guidelines, including travel-rule and suspicious-transaction duties. A ledger that merely shares financial information among institutions will be compared, in spirit, with designs such as the Account Aggregator framework, which refuses to let the conduit become the owner of the customer's information. Cryptographic keys that authorise a write to the ledger are production secrets, and should be custodied with the same seriousness as any other payment or signing key.

In other words, the ledger is an architecture. It is not a waiver.

Implications

  1. Describe the system in ISO 23257 terms: components, roles, activities and relationships.
  2. Make permissioning explicit: who runs nodes, who may write, who may read, and how that set changes.
  3. Design key custody and identity first, not after the first network is live.
  4. Map legal duties (data protection, sector cyber rules, and, where applicable, FIU-IND) onto those roles.

What this means for fintech

Firms that want a shared, tamper-evident record among known parties have a published reference architecture to start from. The work that remains is governance and custody, not a new metaphor. A permissioned ledger that cannot name its roles, or its keys, is not yet ready for a regulated environment.

Sources

  1. ISO 23257:2022, Blockchain and distributed ledger technologies — Reference architecture
  2. RBI Account Aggregator Directions (consent and non-ownership of data)
  3. FIU-IND VDA guidelines, 10 March 2023