Design Requirement

R5.1 - Need to know principle

Compliance with the 'need to know' principle: only the customers themselves and entities relevant to the KYC process must have access to customers' personal data.

Overview

Producer metadata and the represented concept document.

Concept identity

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

Open concept record

Producer label: R5.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-r5-1.md

bankingdesign-requirementidentity-ssikyckyc-framework-ssiverifiable-credentials

Design requirement R5.1: Need to know principle

An essential and fairly universal principle in this context is compliance with the "need to know" principle: only the customers themselves and entities relevant to the KYC process must have access to customers' personal data. This is also a general recommendation for information systems from a security perspective.

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 5: Privacy

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

1 Design Objective

design-knowledge/kyc-framework-ssi-do5

Objective 5 - Privacy

Protecting customers' privacy is a key feature of an eKYC process, requiring compliance with the need to know principle and data minimization.

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
R5.1 - Need to know principle
Link label
Design requirement R5.1: Need to know principle
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": "R5.1 - Need to know principle",
  "description": "Compliance with the 'need to know' principle: only the customers themselves and entities relevant to the KYC process must have access to customers' personal data.",
  "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": "R5.1",
  "tags": [
    "kyc-framework-ssi",
    "design-requirement",
    "identity-ssi",
    "kyc",
    "banking",
    "verifiable-credentials"
  ]
}