Probata · in development
Probata
Probata reads the controls running on a Kubernetes platform and turns them into signed evidence that an auditor can verify without relying on the platform team’s word.
Status, November 2026. The design is published in the articles listed below. The specification (evidence-pack schema, catalogue format and the read-only access the collector asks for) is public at github.com/abkhan5/probata. A read-only collector is the first planned component. Nothing here is for sale, and there is no release to download yet.
The evidence plane
A cluster has a control plane that decides and a data plane that carries traffic. The evidence plane is the third part: it records what the other two enforced, and when, in a form that someone who was not there can check later.
What it does
- Reads, never changes
- The first component is a collector that runs with a read-only service account and needs no custom resources or admission hooks. The ComplianceProfile operator in Articles 43–44 is a later, optional layer.
- Maps each observation to a clause
- Mesh policy, admission policy, workload identity and change history are each tied to a row in a control catalogue.
- Signs what it finds
- The output is an evidence pack: canonical JSON in a signed envelope with an RFC 3161 timestamp, verifiable offline with a public key.
- Reports gaps as gaps
- A control that is not enforced is recorded as not enforced.
Designed for
OpenShift with OpenShift Service Mesh 3, and AKS with Istio. On-premises and disconnected clusters are first-class: the signing key and the timestamp authority are the institution’s own, so nothing calls out to a public service.
Regulatory scope
The first control catalogue covers Regulation (EU) 2022/2554 (DORA) and its technical standards, Directive (EU) 2022/2555 (NIS2) and PCI DSS 4.0.1. The catalogue is data, so an institution can put its own control standard underneath and treat each regulation as an overlay.
Read the design
- Turning telemetry into signed evidence Article 27
- Continuous posture and drift — proving the control is still holding Article 28
- Mapping controls to frameworks — PCI-DSS 4.0 on the mesh Article 29
- Designing the ComplianceProfile operator — compliance is a reconcile loop with a different noun Article 43
- Building a Kubernetes operator in C# — Kubernetes has no opinion about Go Article 44
- Shipping continuous evidence as a product — a report is something you send; evidence is something an auditor comes and takes Article 45
Specification and roadmap: github.com/abkhan5/probata.
The reasoning behind it runs through The Evidence Series.
Evidence is something an auditor comes and takes.