Parent folderOpen Confluence

RWS Architecture article

Public Key Infrastructure

Public Key Infrastructure is the product-neutral architecture building block for certificate issuance, trust anchors, and key lifecycle management. It states what DC 3.0 needs from

  1. Typeabb
  2. Statuscandidate
  3. Domainsecurity
On this page
  1. ABB Public Key Infrastructure
  2. Summary
  3. Capabilities
  4. Constraints
  5. Service Description
  6. Roadmaps
  7. Landing Zones
  8. Interfaces
  9. Dependencies
  10. EIRA Alignment
  11. Available SBB's

ABB Public Key Infrastructure

Summary

Public Key Infrastructure is the product-neutral architecture building block for certificate issuance, trust anchors, and key lifecycle management. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides certificate issuance, trust anchors, and key lifecycle management.
  • Defines the functional, technical, security, and quality expectations that SBBs must satisfy.
  • Keeps service ownership, interfaces, and consumption boundaries visible before product selection.
  • Enables traceability from architecture intent to implementation, operational evidence, and consuming services.

Constraints

  • The resulting SBB must fit the identity and access management ownership model and document the support, lifecycle, and service-management boundary.
  • Security, privacy, logging, evidence, and compliance controls must be explicit enough to assess BIO2-aligned implementation where applicable.
  • Certificate profiles, issuing authorities, renewal policy, and private-key handling must be explicit.
  • SBBs must support automated renewal where feasible and auditable exception handling where not.

Service Description

This ABB offers a PKI service that issues, rotates, validates, and governs certificates and trust chains for DC 3.0 services. It is consumed by solution architects, platform teams, and service owners as the capability contract for selecting and shaping SBBs.

The service description remains implementation-neutral: product selection, hosting pattern, detailed runbooks, and service levels belong in the mapped SBB and related ADRs.

Roadmaps

  • Baseline: confirm scope, service ownership, constraints, and acceptance criteria for Public Key Infrastructure.
  • MVP: validate the mapped SBB implementation and record the selected support and lifecycle model.
  • Next: add measurable service levels, evidence requirements, and roadmap dependencies once the SBB is selected.

Landing Zones

  • Private cloud and central DC 3.0 landing zone for core infrastructure and platform services.
  • Government cloud or external cloud landing zones only when the SBB documents the required control set, connectivity model, and data classification fit.

Interfaces

  • ACME, issuer, certificate, and trust-store interfaces as applicable.
  • Identity, ingress, service mesh, and workload certificate integrations.
  • Audit and lifecycle reporting interfaces.

Dependencies

  • Depends on secrets-management for a supporting capability or integration boundary.
  • Depends on federated-authentication for a supporting capability or integration boundary.
  • Implemented by cert-manager as currently mapped SBB traceability.
  • Consuming ABB and SBB dependencies must be recorded as links when solution design identifies concrete upstream or downstream use.

EIRA Alignment

Available SBB's

  • cert-manager - cert-manager is a candidate solution building block for the translated DC 3.0 ABB model. It remains candidate until the responsible architects confirm service ownership, support model, and acceptance criteria.