Supply-chain signing
8 articles in The Mesh Series by Arshad Badar Khan cover Supply-chain signing.
Filter with other topics-
Turning telemetry into signed evidence
You have the logs. That is not the same as having evidence.
Compliance evidenceSupply-chain signingLGTM stackDrift & postureMulti-cluster & residency
-
Mapping controls to frameworks — PCI-DSS 4.0 on the mesh
"Our service mesh makes us PCI compliant." If a vendor says that, end the meeting.
PCI DSSAuthorizationPolicyCompliance evidenceDrift & posturemTLS
-
NIS2 and the Austrian NISG 2026 — when the platform is the compliance measure and the board is on the hook
Last time you mapped DORA onto the cluster and drew one box with a dashed border: governance, owned by the management body, living in GRC rather than YAML. You treated that box as somebody else's problem.
-
One detection pipeline, four confession clocks — incident reporting across DORA, NIS2, CERT-In and DPDP
In Article 37 a red team walked through an allow rule that was too wide, and the mesh logged every step of it. The debrief is going well. Then someone from legal asks the question that ends the good mood: when did we become aware?
-
Disaster recovery for a regulated mesh — recovering the proof, not just the app
A regional outage takes your primary cluster offline at 03:10. By 03:40 the platform team has a cluster in the paired region, Argo CD has reconciled the application manifests, and the dashboards are green. At 09:00 the ICT risk…
Compliance evidenceIstioDisaster recoveryGitOpsWorkload identity
-
Designing the ComplianceProfile operator — compliance is a reconcile loop with a different noun
You have a PeerAuthentication that says STRICT. You have a Gatekeeper constraint that says every namespace must carry a default‑deny AuthorizationPolicy . You have Envoy access logs with SPIFFE identities, signed evidence packs…
Kubernetes operatorsCompliance evidencePolicy as code.NET & C#Supply-chain signing
-
Building a Kubernetes operator in C# — Kubernetes has no opinion about Go
The platform team reviews the Article 43 design and says, kindly, that operators are written in Go. Kubebuilder, controller‑runtime, the Operator SDK, the language the API server itself is written in. They are not wrong about the…
-
Shipping continuous evidence as a product — a report is something you send; evidence is something an auditor comes and takes
The ComplianceProfile status says Satisfied. It is signed. It is in the cluster. An external auditor from the FMA's appointed firm arrives, and the first thing she does is decline the dashboard, decline the kubectl session, and…
Compliance evidenceSupply-chain signing.NET & C#Kubernetes operatorsMicrosoft Entra ID