Design Requirement

R3.1 - Avoid central storage of customer data

A viable solution for an improved eKYC process must avoid central storage of customer data, since silos of customer data are an attractive target for attackers.

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/kyc-framework-ssi-r3-1

Open concept record

Producer label: R3.1
Source paper: Designing a Framework for Digital KYC Processes Built on Blockchain-Based Self-Sovereign Identity
Timestamp: 2026-08-05T00:00:00+00:00
Bundle path: design-knowledge/kyc-framework-ssi-r3-1.md

bankingdesign-requirementidentity-ssikyckyc-framework-ssiverifiable-credentials

Design requirement R3.1: Avoid central storage of customer data

Recent data breaches that revealed sensitive customer data stored in central data silos have significantly reduced confidence in their respective architectures. To avoid comparable data breaches, a viable solution for an improved eKYC process must therefore avoid central storage of customer data.

Source paper

This design requirement is proposed by Designing a Framework for Digital KYC Processes Built on Blockchain-Based Self-Sovereign Identity (Vincent Schlatt, Johannes Sedlmeir, Simon Feulner, Nils Urbach, 2022).

Addresses

Design objective Objective 3: Decentralization

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

1 Design Objective

design-knowledge/kyc-framework-ssi-do3

Objective 3 - Decentralization

A viable solution for an improved eKYC process must avoid central storage of customer data and prevent lock-in effects that could result in the aggregation of market power.

bankingdesign-objectiveidentity-ssikyc+2

1 Paper

papers/kyc-framework-ssi

Designing a Framework for Digital KYC Processes Built on Blockchain-Based Self-Sovereign Identity

The paper derives six design objectives (16 sub-requirements) for an SSI-based eKYC framework and demonstrates how blockchain-based self-sovereign identity can solve KYC challenges without violating data-protection regulation, deriving three nascent design principles that theorize blockchain's role for SSI: use blockchain only for public data, anticipate an ecosystem of various ledgers, and enable decentralization at the edge.

bankingblockchaindesign-science-researchidentity-ssi+3

Relationships

Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.

Outgoing links

Incoming backlinks

Designing a Framework for Digital KYC Processes Built on Blockchain-Based Self-Sovereign Identity
Paper
Source
Designing a Framework for Digital KYC Processes Built on Blockchain-Based Self-Sovereign Identity
Target
R3.1 - Avoid central storage of customer data
Link label
Design requirement R3.1: Avoid central storage of customer data
Status
Resolved
Derived heading context: Design knowledge

Local graph

One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.

Knowledge graph

3 of 3 concepts · 5 directed relationships

Concept types

Raw metadata

The complete producer frontmatter, serialized without server paths or runtime data.

Show producer frontmatter

{
  "type": "design-requirement",
  "title": "R3.1 - Avoid central storage of customer data",
  "description": "A viable solution for an improved eKYC process must avoid central storage of customer data, since silos of customer data are an attractive target for attackers.",
  "resource": "https://doi.org/10.1016/j.im.2021.103553",
  "source_paper": "Designing a Framework for Digital KYC Processes Built on Blockchain-Based Self-Sovereign Identity",
  "label": "R3.1",
  "tags": [
    "kyc-framework-ssi",
    "design-requirement",
    "identity-ssi",
    "kyc",
    "banking",
    "verifiable-credentials"
  ]
}