AuthorizationPolicy
17 articles in The Mesh Series by Arshad Badar Khan cover AuthorizationPolicy.
Filter with other topics-
Istio Without the Overwhelm
Istio has a reputation problem. You open the docs and drown: control planes, sidecars, gateways, virtual services, destination rules, telemetry pipelines, a CRD zoo that reads like someone was paid per resource kind. Most…
-
Terminating user identity at the mesh edge
A bug that ships to production quietly, in regulated shops, all the time:
Microsoft Entra IDJWT validationOAuth 2.0 & OIDCAuthorizationPolicy.NET & C#
-
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
-
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
-
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
-
Egress control and the locked-down cluster
You locked the front door of your Kubernetes cluster. Ingress gateway, token validation, default-deny — the works.
-
Threat-modelling a meshed .NET API
You've spent a dozen articles building controls. Now ask the question nobody budgets for: what does each one do when it BREAKS?
Threat modellingAuthorizationPolicyCompliance evidenceJWT validationCERT-In & DPDP
-
Continuous posture and drift — proving the control is still holding
Your admission controller said yes to the policy six months ago. Is the policy still there?
Drift & posturePolicy as codeCompliance evidenceGitOpsLGTM stack
-
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
-
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
-
Sidecar to ambient — what gets cheaper, what just moves house
"Sidecarless mesh, zero downtime" is a half-truth — and the missing half is exactly the one a regulated cluster cares about.
Ambient meshService meshMicrosoft Entra IDmTLSAuthorizationPolicy
-
The reference architecture — thirty-two pieces, one system
33 articles ago this series opened on a distributed monolith held together with auth tokens and prayer. This is where the pieces become one picture.
Ambient meshCompliance evidenceMicrosoft Entra IDAuthorizationPolicyPasswordless
-
Threat-led penetration testing under DORA — what the red team does once the mesh says yes
The letter from the supervisor is two paragraphs long. Your institution has been identified for threat-led penetration testing. A white team is to be formed. Scope will cover critical or important functions. Testing will run…
-
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