◇ OpenCyber Academy
Postgraduate · Chapter 7 · English

Chapter 7 — Web3, blockchain and cryptoasset security: organizational integration

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 7 — Web3, blockchain and cryptoasset security: organizational integration

Lesson map

Lesson 07 published. Map, example, EX031.

flowchart TD
  N0["Learning outcomes"]
  N1["7.1 Integrating with existing processes"]
  N2["7.2 Responsibilities across institutions"]
  N3["7.3 Training staff"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX031"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["7.1 Integrating with existing processes"]
  N2["7.2 Responsibilities across institutions"]
  N3["7.3 Training staff"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX031"]
[Learning outcomes]
    |
    v
[7.1 Integrating with existing processes]
    |
    v
[7.2 Responsibilities across institutions]
    |
    v
[7.3 Training staff]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX031]

Learning outcomes

You will (1) integrate ledger controls with existing processes; (2) assign responsibilities across institutions; (3) train staff.

7.1 Integrating with existing processes

The credit union already has payment controls, incident management and change management. Nadia integrates the pilot into them rather than creating parallel processes. Settlement batches enter the existing payment approval workflow, ledger incidents use the existing incident system with a new category, and contract or validator changes go through the change advisory board. Integration avoids a separate, less mature process that staff might not follow. She lists each place where ledger work touches an existing process and agrees the handoff with the process owner, recording the agreement.

7.2 Responsibilities across institutions

Nadia drafts a responsibility matrix with the partners. Each institution operates its validator, monitors its own node and holds one multisig key. The independent operator runs the fourth validator and publishes availability reports. A joint operations group meets weekly during the pilot. For each activity the matrix names who is responsible, who approves, who is consulted and who is informed. Ambiguous responsibility is a common source of failure in shared systems, because everyone assumes someone else is watching. The partners sign the matrix as an annex to the pilot agreement.

7.3 Training staff

Payment operations staff need to understand the new batch summary, reviewers need to know what errors to look for and keyholders need to practise signing with hardware devices. Nadia designs short training sessions with exercises on synthetic batches. She measures training by having each participant review a seeded batch; all twelve participants catch the seeded duplicate after training, compared with five of twelve before. She records attendance and results. Training is a control, and measuring it shows whether it works, just as testing any technical control would.

Worked example

Nadia embeds the pilot in existing workflows, signs a cross-institution responsibility matrix and raises duplicate detection from 5 of 12 to 12 of 12 staff through training.

Synthetic case. The processes, matrix and training results are synthetic.

Errors and limits

Creating parallel processes for new technology produces controls staff do not follow.

Exercises

Synthesis

Integration, clear responsibilities and measured training make ledger controls part of normal work.

Continue studying — chapter 07 of 12

← Chapter 06 (draft) · Course chapter index · Chapter 08 (draft) →