Skip to main content
Version: V2-Next

Security Properties

A security property is a guarantee of the platform that can be checked. This page lists the properties that the architecture board has agreed. Together with the Security Architecture Principles they are the reference for design and code reviews and for the threat model.

Each property states:

  • Relies on: the conditions the property depends on, mostly provided by the operator. The property holds only where they hold.
  • TR-03187: the requirements of BSI TR-03187 that the property serves, fully or partially (see the TR 03187 Conformance Statement).
  • Release 2.0.2: whether the latest release meets the property, and the issues that track the gaps.
  • Checked by: how a violation is detected.

Properties that are still under discussion are kept, with their evidence, in the security properties catalogue.

PropertyAreaRelease 2.0.2Agreed
SP-EDGE-1 Single entry pointEdge and gatewayHolds2026-11-18
SP-EDGE-2 Identity headers come only from the gatewayEdge and gatewayHolds2026-11-18
SP-AUTHZ-1 Deny by default, fail closedAuthorizationHolds2026-11-18
SP-AUTHZ-6 Open data is explicit, read-only and payload-onlyAuthorizationHolds2026-11-18
SP-NET-1 Default-deny ingress, peers pinned by namespace and labelTrust zones in the clusterPartially2026-11-18
SP-NET-4 Add-onsAdd-onAn optional component that extends the Platform for specific use cases, for example for visualization or low-code data processing. An Add-on is not part of the platform core: it is maintained in a separate repository, included in the deployment as a Git submodule, and accesses the Platform only via its public interfaces. use only the public interfacesTrust zones in the clusterPartially2026-11-18
SP-WL-3 No shipped credential is a known defaultWorkloads and secretsNot yet2026-11-18
SP-SC-3 No executable code is fetched at runtimeSupply chain and deliveryHolds2026-11-18
SP-SC-5 Rendered manifests pass the hardening policies before mergeSupply chain and deliveryHolds2026-11-18

Edge and gateway​

Boundary: internet → ingress → APISIXApache APISIXAn open-source API gateway for traffic management, security and observability. In CIVITAS/CORE it is used as the centralized entrypoint to route and protect externally exposed APIs. → upstreams

SP-EDGE-1: Single entry point​

All traffic from outside the cluster enters through the APISIXApache APISIXAn open-source API gateway for traffic management, security and observability. In CIVITAS/CORE it is used as the centralized entrypoint to route and protect externally exposed APIs. Ingress. The shipped charts render no other Ingress and no Service of type NodePort or LoadBalancer.

note

NiFiApache NiFiA stream processing and connector framework. In CIVITAS/CORE it is the pipeline engine for data integration and transformation (see ADR 047) and implements dataset-defined data flows.'s pull connectors open outbound connections and bring external data into the platform. That data does not pass APISIXApache APISIXAn open-source API gateway for traffic management, security and observability. In CIVITAS/CORE it is used as the centralized entrypoint to route and protect externally exposed APIs. and is not covered by this property.

  • Relies on:
    • The operator provides and hardens the Kubernetes cluster and its nodes. Cluster administrators, node administrators and whoever holds the instance's kubeconfig are trusted. (ENV-1)
  • TR-03187: AR-16 Abschirmung unterschiedlicher Vertrauenszonen (partially); W-3 Einheitlicher Zugriffskontrollmechanismus (partially)
  • Release 2.0.2: Holds.
  • Checked by: review.
  • Agreed: architecture board, 2026-11-18.

SP-EDGE-2: Identity headers come only from the gateway​

On every APISIXApache APISIXAn open-source API gateway for traffic management, security and observability. In CIVITAS/CORE it is used as the centralized entrypoint to route and protect externally exposed APIs. route — static, add-on and created at runtime by the config-adapter — the headers X-Userinfo, X-Access-Token, X-Id-Token, X-Allowed-Scope-Ids, X-Allowed-Pool-Ids, X-Refresh-Token and X-Raw-ID-Token that a client sends are removed before any plugin or upstream reads them. Only openid-connect and opa set them.

  • Relies on:
    • The operator provides and hardens the Kubernetes cluster and its nodes. Cluster administrators, node administrators and whoever holds the instance's kubeconfig are trusted. (ENV-1)
    • The cluster's CNI enforces NetworkPolicy. (ENV-2)
  • TR-03187: W-3 Einheitlicher Zugriffskontrollmechanismus (partially); AR-8 Replay-Schutz (partially)
  • Release 2.0.2: Holds.
  • Checked by: automated tests in CI; runtime security test suite (run manually); review.
  • Agreed: architecture board, 2026-11-18.

Authorization​

Boundary: APISIXApache APISIXAn open-source API gateway for traffic management, security and observability. In CIVITAS/CORE it is used as the centralized entrypoint to route and protect externally exposed APIs. (PEPPolicy Enforcement PointThe component that enforces the authorization decision made by the Policy Decision Point. CIVITAS/CORE uses Apache APISIX as its PEP, adopting a centralized, gateway-enforced authorization architecture.) → OPAOpen Policy AgentThe platform's authorization service: it evaluates 'who may do what' against the CIVITAS/CORE authorization model. OPA is the platform's central Policy Decision Point (PDP) for API authorization. (PDPPolicy Decision PointThe component that decides whether a request is authorized. CIVITAS/CORE uses Open Policy Agent (OPA) as its PDP.) → AuthZ repository (PIP) → portal-backend

SP-AUTHZ-1: Deny by default, fail closed​

A request through the gateway is denied unless an explicit rule grants it — unknown backend, endpoint or method, missing or undecodable X-Userinfo and users unknown to the portal database included — and an outage of OPAOpen Policy AgentThe platform's authorization service: it evaluates 'who may do what' against the CIVITAS/CORE authorization model. OPA is the platform's central Policy Decision Point (PDP) for API authorization. or of the AuthZ repository never grants access. Anonymous callers get 401, authenticated ones 403.

  • Relies on:
    • The cluster's CNI enforces NetworkPolicy. (ENV-2)
  • TR-03187: W-1 Deny All als Default (partially); W-20 Nicht benötigte HTTP-Verben deaktivieren (partially); AR-14 Sicherheitsmechanismen defaultmäßig anschalten (partially)
  • Release 2.0.2: Holds.
  • Checked by: automated tests in CI; runtime security test suite (run manually).
  • Agreed: architecture board, 2026-11-18.

SP-AUTHZ-6: Open data is explicit, read-only and payload-only​

Anonymous access is limited to GET reads of the payload of datasets flagged openDataAccess, on the instance's API host; making a released dataset open needs the RELEASE permission.

  • Relies on:
    • SP-EDGE-2 Identity headers come only from the gateway
  • TR-03187: W-1 Deny All als Default (partially); DH-4 Data Governance-Vorgaben etablieren (partially)
  • Release 2.0.2: Holds.
  • Checked by: automated tests in CI.
  • Agreed: architecture board, 2026-11-18.

Trust zones in the cluster​

Boundary: namespace ↔ namespace, pod ↔ pod, instance ↔ instance

SP-NET-1: Default-deny ingress, peers pinned by namespace and label​

Every namespace that holds a component or add-on has an ingress default-deny NetworkPolicy, and every allow rule that names a component pins it by namespace name AND pod labels, so copying labels into another namespace, instance or add-on gains nothing.

  • Relies on:
    • The cluster's CNI enforces NetworkPolicy. (ENV-2)
  • TR-03187: AR-16 Abschirmung unterschiedlicher Vertrauenszonen (partially); DH-3 IPC-Schnittstellen müssen geschützt sein (partially); W-1 Deny All als Default (partially)
  • Release 2.0.2: Partially. Every rendered namespace has an ingress default-deny and every cross-namespace peer is pinned by namespace name. Gaps: the deployment silently drops a policy whose target namespace does not resolve instead of failing, and the mcp-server add-on is installed without a policy. Tracked in deployment#255.
  • Checked by: runtime security test suite (run manually); review.
  • Agreed: architecture board, 2026-11-18.

SP-NET-4: Add-ons use only the public interfaces​

Add-onAdd-onAn optional component that extends the Platform for specific use cases, for example for visualization or low-code data processing. An Add-on is not part of the platform core: it is maintained in a separate repository, included in the deployment as a Git submodule, and accesses the Platform only via its public interfaces. pods reach platform components only through the APISIXApache APISIXAn open-source API gateway for traffic management, security and observability. In CIVITAS/CORE it is used as the centralized entrypoint to route and protect externally exposed APIs. data plane, like an external client, and add-on deployment files cannot open platform namespaces.

  • Relies on:
    • The cluster's CNI enforces NetworkPolicy. (ENV-2)
    • Add-onsAdd-onAn optional component that extends the Platform for specific use cases, for example for visualization or low-code data processing. An Add-on is not part of the platform core: it is maintained in a separate repository, included in the deployment as a Git submodule, and accesses the Platform only via its public interfaces. are trusted co-tenantsTenantAn isolated organizational partition that owns Data pools, Datasets, Users, Groups, and Roles. All access rules exist within their Tenant, and the Tenant is the widest Scope of a Role. Currently, one Tenant corresponds to the Platform. of the instance: they share the KeycloakKeycloakAn open-source Identity and Access Management (IAM) solution providing SSO and OAuth2/OpenID Connect flows. In CIVITAS/CORE it is used to authenticate users and issue JWTs. realm and APISIXApache APISIXAn open-source API gateway for traffic management, security and observability. In CIVITAS/CORE it is used as the centralized entrypoint to route and protect externally exposed APIs., and their admins are platform admins. (USE-2)
  • TR-03187: AR-16 Abschirmung unterschiedlicher Vertrauenszonen (partially)
  • Release 2.0.2: Partially. No platform policy admits an add-on namespace today, but nothing prevents an add-on's own policy files from opening a platform namespace.
  • Checked by: no check yet.
  • Agreed: architecture board, 2026-11-18.

Workloads and secrets​

Boundary: container ↔ node ↔ Kubernetes API

SP-WL-3: No shipped credential is a known default​

Every credential between components is generated per install by a CSPRNG, kept across upgrades, and injected by secretKeyRef or file — never a literal in values, a command line, SQL text, a ConfigMap or an image.

  • Relies on:
    • Production installs run profile: production with the shipped security defaults unchanged, and the operator's deployment/ directory (values, environment overrides) is in a private repository. (ENV-6)
  • TR-03187: W-14 Standardzugangsdaten ändern (fully); CT-5 Geheimnisse zur Laufzeit dynamisch bereitstellen (fully); AR-9 Geheimnisse müssen änderbar sein (partially); DH-2 Schutz geheimer Schlüssel (partially)
  • Release 2.0.2: Not yet. Credentials are generated securely per install, but known defaults still ship (FROST admin:admin and write:write, the GeoServer factory admin password, the KeycloakKeycloakAn open-source Identity and Access Management (IAM) solution providing SSO and OAuth2/OpenID Connect flows. In CIVITAS/CORE it is used to authenticate users and issue JWTs. master admin user name 'admin', a 'changeit' truststore password), and some secrets appear on command lines. Tracked in deployment#246, deployment#362, deployment#381, deployment#382.
  • Checked by: runtime security test suite (run manually).
  • Agreed: architecture board, 2026-11-18.

Supply chain and delivery​

Boundary: source → CI → registry → operator's cluster

SP-SC-3: No executable code is fetched at runtime​

No default workload downloads executable code (jars, plugins, packages, scripts) at start; every component runs only what its image contains.

  • Relies on: nothing beyond the platform itself.
  • TR-03187: AR-17 Integritätsgeschützter Kanal für Deployment (partially); AR-4 Version Pinning (partially)
  • Release 2.0.2: Holds.
  • Checked by: review.
  • Agreed: architecture board, 2026-11-18.

SP-SC-5: Rendered manifests pass the hardening policies before merge​

A deployment change fails CI when its rendered manifests violate Pod Security Standards baseline/restricted or the CIVITAS hygiene policies, minus documented PolicyExceptions.

  • Relies on: nothing beyond the platform itself.
  • TR-03187: CT-8 Geringstmögliche Privilegien für Container-Images (partially); AR-14 Sicherheitsmechanismen defaultmäßig anschalten (partially)
  • Release 2.0.2: Holds.
  • Checked by: CI policy on the rendered manifests.
  • Agreed: architecture board, 2026-11-18.