Network policy
4 articles in The Mesh Series by Arshad Badar Khan cover Network policy.
Filter with other topics-
Default-deny — the AuthorizationPolicy that fails closed
In default-allow, a forgotten rule leaves a workload open — and you find out when infosec does, or an attacker does. In default-deny, a forgotten rule breaks a deployment in testing, in your face, where you fix it.
AuthorizationPolicyNetwork policyIstioMicrosoft Entra IDSPIFFE
-
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
-
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
-
The policy you wrote isn’t the policy you enforce
You wrote a default-deny policy. You reviewed it. You merged it. And nothing in your cluster stops someone from deploying a workload that ignores it.
Policy as codeKubernetesAuthorizationPolicyNetwork policyCompliance evidence