A. B. Khan

The Evidence Series

Evidence, not dashboards

A series on what it takes for a Kubernetes platform to prove its controls to an auditor, tied clause by clause to DORA, NIS2 and PCI DSS.

What counts as evidence

A green dashboard shows a state now, to whoever is logged in. An auditor asks for something else: a record that can be checked later, by someone who was not there. Four properties make a record evidence.

Source
Which system produced the record, through which API, under which identity.
Time
When it was true, taken from a clock the platform team does not control.
Integrity
A signature showing the record has not changed since it was taken.
Reproducibility
Someone else can verify the record independently and repeat the collection method to check it.

The series

A series of long-form articles, each written from a milestone in a lab: a private cluster, admission control, a service mesh with workload identity, and a signed evidence pipeline. Every article ties the platform work to a named clause and to the record that proves it. Lab incidents are labelled as lab incidents.

The first article, “The compliance dashboard is not evidence”, is in preparation.

Where the argument starts

The Mesh Series already covers the ground the new series builds on.

The tooling the series builds towards is described on the Probata page.