Secrets & certificates
4 articles in The Mesh Series by Arshad Badar Khan cover Secrets & certificates.
Filter with other topics-
mTLS and SPIFFE — identity on the wire
Everyone claims they have mTLS. Almost nobody can prove it to an auditor. Those are two different jobs.
-
Entra Workload ID Federation on AKS
A workload can present a SPIFFE cert to its neighbours. It can't present one to Key Vault. So how does it prove itself to Azure — still with no secret in config?
Microsoft Entra IDWorkload identityAzureSPIFFESecrets & certificates
-
Secrets and certificates — for the ones you couldn't eliminate
Eighteen articles deleting secrets. But "fewer" isn't "none." Some secrets must exist — a third-party API key, a legacy DB password, a signing key you own. For those, and for certificates, there's an order of preference most teams…
Secrets & certificatesKubernetesWorkload identityGitOpsNetwork policy
-
GitOps for the mesh — when the pull request becomes the change record
In a regulated shop, a merged pull request IS the change-management record. Author, reviewer, diff, timestamp — maker-checker, enforced by branch protection, mapped straight onto PCI 6.5 and ISO A.8.32.
GitOpsMicrosoft Entra IDCompliance evidenceAuthorizationPolicyDrift & posture