-
Network policy and mesh policy — belt and suspenders
Your mesh AuthorizationPolicy has a blind spot: a pod without a sidecar. A DaemonSet, a node agent, a debug pod — it can open a raw socket to your ledger and the mesh never gets a vote, because the request never hit a proxy.
Network policyAuthorizationPolicyPolicy as codeSPIFFECompliance evidence
-
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
-
Regional frameworks — one control surface, four rulebooks
If you run card workloads across Mumbai, Riyadh, and Dubai, you answer to RBI, SAMA, the UAE regulators, and ISO 27001 at once. The instinct is four compliance programs. That's expensive and wrong.
SAMACompliance evidenceCERT-In & DPDPRBIMulti-cluster & residency
-
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