Skip to content

Security and integration ​

This page shows how the architecture protects the keys and the tenants, how the components connect, what the provider's own services and tools integrate with, and the technology an OpenKCM deployment is built on.

Security principles ​

PrincipleHow the architecture implements it
No key material in the governance planeCMK, the Registry and the CMK-2-Krypton Bridge hold references, metadata and policy. Key material stays in keystores, and in Krypton only sealed
Every request checked twiceExtAuthZ authenticates the caller at the gateway and signs the result; CMK verifies the signature and the caller's role
Tenant isolationOwn identity provider, roles and database schema per tenant; keys in Krypton separated per tenant; a workload gets only the keys of the tenant in its client certificate
Separation of dutiesTenant administrators, key administrators and auditors are separate roles, and sensitive changes can require approval by other users
Encrypted, authenticated service trafficMutual TLS between services through a service mesh; client certificates on the AMQP broker, on Krypton's gRPC APIs and on KMIP
Protected key materialKrypton seals every key with its parent key before it stores it, and keeps unsealed keys only in locked memory
TraceabilityKey, system, login and access events as audit events

See the Trust model, the CMK security architecture and Krypton security.

Connections ​

Authenticate and encrypt every connection between the components. The table lists each connection and how to protect it.

FromToProtocolProtect with
Customer's browser or automationEnvoy Gateway of the CMK regionHTTPSTLS; ExtAuthZ checks a session cookie, a bearer token or a client certificate on every request
Session ManagerCustomer's identity providerOpenID ConnectTLS; one identity provider per tenant
RegistryCMK of each regionAMQP 1.0, through OrbitalClient certificates on the broker (SASL EXTERNAL)
CMK, the Bridge, provider services and onboardingRegistrygRPCMutual TLS through a service mesh; allow only these callers
CMKSystems of each system region, and the BridgeAMQP 1.0, through OrbitalClient certificates on the broker
Provider's onboarding and servicesCMK-2-Krypton BridgegRPCMutual TLS through a service mesh; allow only these callers
CMK-2-Krypton BridgeKrypton root nodegRPCMutual TLS, with the Bridge's own Krypton identity
Krypton root nodeAgentsgRPCMutual TLS, with an identity per agent
WorkloadsKryptonKMIPMutual TLS, with a client certificate whose common name is the tenant ID
CMKKeystoresThe keystore's API, through a keystore pluginThe keystore's own authentication; AWS KMS today
All servicesAudit collectorOTLPTLS to the provider's collector

What the provider integrates ​

Integration pointWho implements itInterface
Tenant onboardingThe provider's onboardingCMK-2-Krypton Bridge gRPC API, which registers the tenant in the Registry; the identity provider through the Registry gRPC API
System registrationEach provider service, or the Bridge for the systems it creates keys forRegistry gRPC API
Key and system tasksEach provider service, per system regionAMQP 1.0 queues, through Orbital
Key deliveryWorkloadsKMIP over mutual TLS (Krypton, Sandbox)
Customer sign-inThe customerOpenID Connect identity provider, per tenant
KeystoresThe provider, as pluginsKeystore plugins; AWS KMS today
User directoriesThe provider, as pluginsSCIM directory plugins
AuditThe provider's security operationsOTLP log records to the provider's audit collector
Automation by customersThe customerCMK REST API

Technology stack ​

NeedTechnology
RuntimeKubernetes 1.23 or later; every service as a container image with a Helm chart
DatabasesPostgreSQL, one database per service and region
Task queue and sessionsValkey or Redis
Messaging between regions and servicesAMQP 1.0, for example RabbitMQ 4, with client certificates
GatewayEnvoy Gateway with external authorization
Service trafficA service mesh with mutual TLS, for example Linkerd or Istio
Sign-inOpenID Connect, per tenant
Key storageAWS KMS (customer keys); OpenBao (Krypton)
Workload key accessKMIP
Observability and auditOpenTelemetry (OTLP)

See also ​

EU and German government funding logos

Funded by the European Union – NextGenerationEU.

The views and opinions expressed are solely those of the author(s) and do not necessarily reflect the views of the European Union or the European Commission. Neither the European Union nor the European Commission can be held responsible for them.