๐ŸŒŒ
Privacy Village Academy
Join The Community!AcademyAbout HGPE
  • Hitchhiker's Guide to Privacy Engineering
    • โ“What is HGPE?
      • โš–๏ธWho is this for?
      • ๐Ÿง™โ€โ™‚๏ธPrivacy Engineering
      • ๐ŸŽจCreative Privacy
      • ๐Ÿ”ฎGenerative AI
      • ๐Ÿง‘โ€๐Ÿ’ปAbout the Author
  • ๐Ÿง™โ€โ™‚๏ธThe Ethical AI Governance Playbook 2025 Edition
    • ๐Ÿค–Chapter 1 : AI Literacy
    • ๐ŸŒChapter 2 : AI Governance in the 21st Century
    • โŒ›Chapter 3 - Getting Started with AI Act Compliance
    • ๐Ÿš€Chapter 4 : Rise of AI Governance: Building Ethical & Compliant AI
    • Chapter 5 : Introduction to the Lifecycle of AI
  • ๐ŸŽ“Privacy Engineering Field Guide Season 1
    • โ“Decoding the Digital World: Exploring Everyday Technology
    • ๐Ÿ‘๏ธIntroduction: Why Privacy Matters?
      • Age of Mass Surveillance
      • Privacy & Democracy
      • Privacy & Government Surveillance
    • โšกChapter 1 : How Computers Work?
      • Electricity
      • Bits
      • Logic Gates
      • Central Processing Unit (CPU)
      • Graphic Processing Unit (GPU)
      • Motherboard
      • Data Storage
      • Databases
      • Operating System (OS)
      • Computer Code
      • Programming Languages
      • The File System
      • Bugs and Errors
      • Computer Virus
      • Internet of Things (IoT)
      • Cloud Computing
    • ๐Ÿ›ฐ๏ธChapter 2 : How the internet works?
      • Physical Infrastructure
      • Network and Protocols
      • Switch
      • Routers
      • IP Address
      • Domain Name System (DNS)
      • Mac Address
      • TCP / IP
      • OSI Model
      • Packets
      • The Client - Server Architecture
      • Secure Socket Shell (SSH)
      • Transport Layer Security (TLS)
      • Firewall
      • Tunnels and VPNs
      • Proxy Server
    • ๐Ÿ–ฅ๏ธChapter 3 : How Websites Work?
      • HTML
      • CSS
      • Javascript
      • Web Server
      • Browser
      • HTTP
      • Databases
      • Front End (Client Side)
      • Back End (Server Side)
      • Cookies
      • Local Storage
      • Session Storage
      • IndexedDB
      • XHR Requests
      • Web APIs
      • Webhooks
      • Email Server
      • HTTPS
      • Web Application Firewall
      • Single Sign-on (SS0)
      • OAuth 2.0
      • Pixels
      • Canvas Fingerprinting
      • Email Tracking
      • Containers
      • CI/CD
      • Kubernetes
      • Serverless Architecture
    • โš›๏ธChapter 4 : How Quantum Computers Work?
      • Quantum Properties
      • Quantum Bits (Qubits)
      • Decoherence
      • Quantum Circuits
      • Quantum Algorithms
      • Quantum Sensing
      • Post-Quantum Cryptography
    • ๐Ÿ“ณChapter 5 : Mobile Apps and Privacy
      • Battery
      • Processor
      • Mobile Operating Systems
      • Mobile Data Storage
      • Cellular Data
      • Mobile Device Sensors
      • Wireless Connectivity
      • Camera & Microphone
      • Mobile Apps
      • Software Development Kits (SDKs)
      • Mobile Device Identifiers
      • Bring Your Own Device (BYOD)
  • ๐Ÿ•ต๏ธโ€โ™‚๏ธPrivacy Engineering Field Guide Season 2
    • โ“Introduction to Privacy Engineering for Non-Techs
      • ๐ŸŽญChapter 1 : Digital Identities
        • What is identity?
        • Authentication Flows
        • Authentication vs. Authorization
        • OAuth 2.0
        • OpenID Connect (OIDC)
        • Self Sovereign Identities
        • Decentralized Identifiers
        • eIDAS
      • ๐Ÿ‘๏ธโ€๐Ÿ—จ๏ธChapter 2 : De-Identification
        • Introduction to De-Identification?
        • Input / Output Privacy
        • De-identification Strategies
        • K-Anonymity
        • Differential Privacy
        • Privacy Threat Modeling
  • ๐Ÿ“–HGPE Story and Lore
    • ๐ŸชฆChapter 1 : The Prologue
    • โ˜„๏ธChapter 2 : Battle for Earth
    • ๐Ÿฆ Chapter 3 : A Nightmare To Remember
    • ๐Ÿง™โ€โ™‚๏ธChapter 4 : The Academy
    • ๐ŸŒƒChapter 5: The Approaching Darkness
    • โš”๏ธChapter 6 : The Invasion
    • ๐ŸฐChapter 7 : The Fall of the Academy
    • ๐Ÿ›ฉ๏ธChapter 8 : The Escape
    • ๐ŸชChapter 9 : The Moon Cave
    • ๐Ÿฆ‡Chapter 10: Queen of Darkness
  • ๐Ÿ“บVideos, Audio Book and Soundtracks
    • ๐ŸŽงReading Episodes
    • ๐ŸŽนSoundtracks
  • ๐Ÿ‘พHGPE Privacy Games and Challenges
    • ๐ŸŽฎData Privacy Day'23 / Privacy Treasure Hunt Game
    • ๐ŸงฉPrivacy Quest
  • ๐Ÿ“ฌSubscribe Now!
Powered by GitBook
On this page

Was this helpful?

  1. Privacy Engineering Field Guide Season 2
  2. Introduction to Privacy Engineering for Non-Techs
  3. Chapter 1 : Digital Identities

Self Sovereign Identities

PreviousOpenID Connect (OIDC)NextDecentralized Identifiers

Last updated 1 year ago

Was this helpful?

Why do we need SSI? ๐Ÿ‘€

Our current digital identity systems are flawed because they often rely on centralized entities or identity providers (IDPs), putting usersโ€™ identities at risk if these entities revoke access.

SSI (Self-Sovereign Identity) addresses this problem by giving control back to users and creating a more equal ecosystem.

Single Sign-On (SSO) services often lock users within their own ecosystems, limiting control over their identities.

The call for a new framework, known as Self-Sovereign Identity (SSI), has emerged, granting individuals autonomy over how their personal data is shared and utilized. In this paradigm, users become the self-administrators of their own identities, offering more than just a means of logging into services.

Who are the actors?

SSI involves three key actors: the Holder (user), the Issuer (credential authority), and the Verifier (credential verifier).

Users collect and store verifiable credentials in their digital wallets, establish secure connections with verifiers using cryptographic keys, and share selected credentials to prove their identity.

Blockchain plays a crucial role in SSI infrastructure. DIDs (Decentralized Identifiers) can be registered on blockchains, offering tamper-resistant, trustable data sources.

Blockchains provide a solution to the challenge of trusted data without relying on a central authority, enabling the adoption of verifiable digital credentials in SSI. Different types of blockchains (permissionless, permissioned, hybrid) can support SSI equally effectively.

Verifiable Credentials

Within this framework lies the concept of the โ€œtrust triangle,โ€ involving the issuer (e.g., the government), the holder (the identity subject), and the verifier (e.g., a bank).

Consider an example like Know Your Customer (KYC) in banking: you can receive a verified credential from the government, which you can then present to the bank as proof of identity.

What qualifies a person can range from attributes like gender and height to first-party data or third-party verified credentials such as passports and diplomas. Notably, the credentials themselves are not stored on the blockchain; instead, only the Decentralized Identifier (DID) is stored, while the identity data resides in decentralized data stores.

DIDs represent real-world identities, such as passport numbers and email addresses, with legal and practical implications. They serve as identifiers for verifiable, self-sovereign digital identities, controlled by the holder. DIDs are independent, globally unique identifiers that do not rely on centralized registration authorities. They point to DID documents containing additional information.

๐Ÿ•ต๏ธโ€โ™‚๏ธ
โ“
๐ŸŽญ
Seeking refuge from the relentless rain, you dashed into the familiar haven of Ripper Docโ€™s shop. As you took shelter from the downpour, the streets outside suddenly erupted with deafening explosions and terrified screams, signaling that Elaraโ€™s sinister campaign had taken a deadly turn.
Page cover image