I. Overview

%%{init: { 'theme': 'base', 'themeVariables': { 'edgeLabelBackground': '#fff' }}}%%
flowchart LR
    A["Threats in\npublic key distribution"] -- "Built on trust in a Certificate Authority (CA)" --> B["Hierarchical\ntrust structure"]
    style A fill:#f9f9f9,stroke:#333,stroke-width:3px
    style B fill:#e1f5fe,stroke:#01579b,stroke-width:3px

Definition: A hierarchical trust structure that performs user identification, and certificate issuance, storage, distribution, and revocation, so that public-key cryptography can be used safely.

Necessity:
( Establishing a Trust Model ) A framework is needed to guarantee the trustworthiness of a public key within an asymmetric-key cryptographic system
( Preventing MITM Attacks ) Blocks the man-in-the-middle attacks that can occur during public key distribution
( Integrated Management System ) Requires infrastructure to manage the full lifecycle of a certificate — issuance, storage, distribution, and revocation

II. Mechanism & Components

A. Core PKI Entities

graph TD
    CA["Certificate Authority (CA)\nissues/revokes certificates"] --- RA["Registration Authority (RA)\nverifies identity/handles registration"]
    RA --- User["User\napplies and uses"]
    CA --- Repo["Repository\nstores certificates/CRLs"]
  • CA (Certificate Authority): The top-level trusted entity responsible for issuing and revoking certificates and managing the CRL
  • RA (Registration Authority): Verifies user identity and handles registration on behalf of the CA (distributing the CA’s workload)
  • Repository: A directory such as LDAP that stores certificates and the CRL (certificate revocation list)
  • User: The party using the service (sender/recipient)

B. Certificate Issuance and Verification Process

StepKey ActivityDetails
1. RegistrationVerify user identityOffline or online face-to-face verification via the RA
2. IssuanceGenerate certificateThe CA embeds the user’s public key and information, and signs it with the CA’s private key
3. VerificationConfirm trustworthinessThe recipient verifies the signature inside the certificate using the CA’s public key
4. RevocationManage loss of validityIf revoked before expiry, it is registered in the CRL or via OCSP

III. Advanced Topics & Comparison

Comparison ItemHierarchical ModelNetwork (Mesh) Model
StructureTree structure centered on a Root CAMutual authentication between CAs (cross-certification)
Trust PathOne-way, top to bottomBidirectional or a more complex path
AdvantageManagement is centralized and clearHigh integration and scalability across organizations
ExampleNational accredited certification systems, SSL/TLSCross-organizational federated security systems

Last updated 18 Aug 2026, 00:00 UTC. history