<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>The Mesh Series — Arshad Badar Khan</title>
    <link>https://www.abkhan.in/software/</link>
    <atom:link href="https://www.abkhan.in/software/feed.xml" rel="self" type="application/rss+xml"/>
    <description>45 articles on Kubernetes, Istio, .NET and Entra ID for regulated platforms.</description>
    <language>en</language>
    <item>
      <title>Shipping continuous evidence as a product — a report is something you send; evidence is something an auditor comes and takes</title>
      <link>https://www.abkhan.in/software/blog/45-shipping-continuous-evidence-as-a-product/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/45-shipping-continuous-evidence-as-a-product/</guid>
      <pubDate>Sat, 14 Nov 2026 09:00:00 GMT</pubDate>
      <description>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…</description>
      <category>Compliance evidence</category>
      <category>Supply-chain signing</category>
      <category>.NET &amp; C#</category>
      <category>Kubernetes operators</category>
      <category>Microsoft Entra ID</category>
    </item>
    <item>
      <title>Building a Kubernetes operator in C# — Kubernetes has no opinion about Go</title>
      <link>https://www.abkhan.in/software/blog/44-building-a-kubernetes-operator-in-csharp/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/44-building-a-kubernetes-operator-in-csharp/</guid>
      <pubDate>Fri, 13 Nov 2026 09:00:00 GMT</pubDate>
      <description>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…</description>
      <category>Kubernetes operators</category>
      <category>.NET &amp; C#</category>
      <category>Kubernetes</category>
      <category>Policy as code</category>
      <category>GitOps</category>
      <category>Supply-chain signing</category>
      <category>LGTM stack</category>
    </item>
    <item>
      <title>Designing the ComplianceProfile operator — compliance is a reconcile loop with a different noun</title>
      <link>https://www.abkhan.in/software/blog/43-designing-the-complianceprofile-operator/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/43-designing-the-complianceprofile-operator/</guid>
      <pubDate>Tue, 10 Nov 2026 09:00:00 GMT</pubDate>
      <description>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…</description>
      <category>Kubernetes operators</category>
      <category>Compliance evidence</category>
      <category>Policy as code</category>
      <category>.NET &amp; C#</category>
      <category>Supply-chain signing</category>
      <category>DORA</category>
      <category>Kubernetes</category>
      <category>PCI DSS</category>
    </item>
    <item>
      <title>What the mesh actually costs — two curves on two axes, and the one the CFO sees</title>
      <link>https://www.abkhan.in/software/blog/42-what-the-mesh-actually-costs/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/42-what-the-mesh-actually-costs/</guid>
      <pubDate>Sat, 14 Nov 2026 09:00:00 GMT</pubDate>
      <description>The platform lead has one slide. It says the sidecar costs about 100 millicores and 128 mebibytes per pod, multiply by your pod count, and ambient makes most of that go away. Finance nods. The slide is correct. It is also the…</description>
      <category>Ambient mesh</category>
      <category>Service mesh</category>
      <category>FinOps &amp; cost</category>
      <category>Compliance evidence</category>
      <category>Multi-cluster &amp; residency</category>
      <category>LGTM stack</category>
      <category>Distributed tracing</category>
      <category>Kubernetes operators</category>
    </item>
    <item>
      <title>Upgrading Istio without a control‑failure event — the traffic shift that is not a mutation</title>
      <link>https://www.abkhan.in/software/blog/41-upgrading-istio-without-a-control-failure-event/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/41-upgrading-istio-without-a-control-failure-event/</guid>
      <pubDate>Fri, 06 Nov 2026 09:00:00 GMT</pubDate>
      <description>Istio 1.31.1 fixes GHSA‑qm8v‑g4f9‑qhjx: a BackendTLSPolicy that quietly reverts to plaintext when its CA reference fails to resolve. The control that encrypts was, under one specific failure, not encrypting. You read the advisory…</description>
      <category>Upgrades &amp; patching</category>
      <category>Istio</category>
      <category>Ambient mesh</category>
      <category>Compliance evidence</category>
      <category>DORA</category>
      <category>Kubernetes operators</category>
      <category>Microsoft Entra ID</category>
    </item>
    <item>
      <title>Disaster recovery for a regulated mesh — recovering the proof, not just the app</title>
      <link>https://www.abkhan.in/software/blog/40-disaster-recovery-for-a-regulated-mesh/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/40-disaster-recovery-for-a-regulated-mesh/</guid>
      <pubDate>Tue, 03 Nov 2026 09:00:00 GMT</pubDate>
      <description>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…</description>
      <category>Compliance evidence</category>
      <category>Istio</category>
      <category>Disaster recovery</category>
      <category>GitOps</category>
      <category>Workload identity</category>
      <category>mTLS</category>
      <category>Supply-chain signing</category>
      <category>AuthorizationPolicy</category>
    </item>
    <item>
      <title>Multi-cluster mesh for data residency — residency is a topology decision, not a config flag</title>
      <link>https://www.abkhan.in/software/blog/39-multi-cluster-mesh-for-data-residency/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/39-multi-cluster-mesh-for-data-residency/</guid>
      <pubDate>Sat, 31 Oct 2026 09:00:00 GMT</pubDate>
      <description>Article 38 ended on a problem that sounds administrative and is not. Your Indian arm's CERT‑In report is due in six hours. The evidence that proves it — the access‑log lines, the signed aware‑at record, the Loki result set — must…</description>
      <category>Multi-cluster &amp; residency</category>
      <category>Compliance evidence</category>
      <category>SPIFFE</category>
      <category>Ambient mesh</category>
      <category>Istio</category>
      <category>LGTM stack</category>
      <category>mTLS</category>
      <category>DORA</category>
    </item>
    <item>
      <title>One detection pipeline, four confession clocks — incident reporting across DORA, NIS2, CERT-In and DPDP</title>
      <link>https://www.abkhan.in/software/blog/38-one-detection-pipeline-four-confession-clocks/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/38-one-detection-pipeline-four-confession-clocks/</guid>
      <pubDate>Tue, 27 Oct 2026 09:00:00 GMT</pubDate>
      <description>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?</description>
      <category>DORA</category>
      <category>NIS2</category>
      <category>CERT-In &amp; DPDP</category>
      <category>LGTM stack</category>
      <category>Compliance evidence</category>
      <category>Incident reporting</category>
      <category>SPIFFE</category>
      <category>Supply-chain signing</category>
    </item>
    <item>
      <title>Threat-led penetration testing under DORA — what the red team does once the mesh says yes</title>
      <link>https://www.abkhan.in/software/blog/37-threat-led-penetration-testing-under-dora/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/37-threat-led-penetration-testing-under-dora/</guid>
      <pubDate>Tue, 20 Oct 2026 09:00:00 GMT</pubDate>
      <description>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…</description>
      <category>Red teaming &amp; TLPT</category>
      <category>AuthorizationPolicy</category>
      <category>DORA</category>
      <category>mTLS</category>
      <category>SPIFFE</category>
      <category>Compliance evidence</category>
      <category>Microsoft Entra ID</category>
      <category>NIS2</category>
    </item>
    <item>
      <title>DORA third-party risk and the Register of Information — observed, not declared</title>
      <link>https://www.abkhan.in/software/blog/36-dora-third-party-risk-and-the-register-of-information/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/36-dora-third-party-risk-and-the-register-of-information/</guid>
      <pubDate>Wed, 14 Oct 2026 09:00:00 GMT</pubDate>
      <description>In Article 22 you switched the mesh's outbound traffic policy to REGISTRY_ONLY and wrote a ServiceEntry for every external host a workload is allowed to reach. You called it egress control. It was also something else: the only…</description>
      <category>Egress control</category>
      <category>Third-party risk</category>
      <category>DORA</category>
      <category>Red teaming &amp; TLPT</category>
      <category>Compliance evidence</category>
      <category>Policy as code</category>
    </item>
    <item>
      <title>NIS2 and the Austrian NISG 2026 — when the platform is the compliance measure and the board is on the hook</title>
      <link>https://www.abkhan.in/software/blog/35-nis2-and-the-austrian-nisg-2026/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/35-nis2-and-the-austrian-nisg-2026/</guid>
      <pubDate>Sat, 10 Oct 2026 09:00:00 GMT</pubDate>
      <description>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.</description>
      <category>NIS2</category>
      <category>DORA</category>
      <category>Policy as code</category>
      <category>Compliance evidence</category>
      <category>mTLS</category>
      <category>Supply-chain signing</category>
      <category>Istio</category>
      <category>Microsoft Entra ID</category>
    </item>
    <item>
      <title>DORA for platform engineers — what the Act actually asks of your cluster</title>
      <link>https://www.abkhan.in/software/blog/34-dora-for-platform-engineers/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/34-dora-for-platform-engineers/</guid>
      <pubDate>Sat, 26 Sep 2026 09:00:00 GMT</pubDate>
      <description>You have spent thirty‑three articles building one system: a regulated .NET platform on AKS, Istio and Entra, where every request is authenticated, authorised, encrypted and logged, and where the logs are signed and the posture is…</description>
      <category>DORA</category>
      <category>Compliance evidence</category>
      <category>NIS2</category>
      <category>.NET &amp; C#</category>
      <category>Istio</category>
      <category>Microsoft Entra ID</category>
    </item>
    <item>
      <title>The reference architecture — thirty-two pieces, one system</title>
      <link>https://www.abkhan.in/software/blog/33-the-reference-architecture/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/33-the-reference-architecture/</guid>
      <pubDate>Sat, 19 Sep 2026 09:00:00 GMT</pubDate>
      <description>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.</description>
      <category>Ambient mesh</category>
      <category>Compliance evidence</category>
      <category>Microsoft Entra ID</category>
      <category>AuthorizationPolicy</category>
      <category>Passwordless</category>
      <category>Drift &amp; posture</category>
      <category>Istio</category>
      <category>mTLS</category>
    </item>
    <item>
      <title>Sidecar to ambient — what gets cheaper, what just moves house</title>
      <link>https://www.abkhan.in/software/blog/32-sidecar-to-ambient/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/32-sidecar-to-ambient/</guid>
      <pubDate>Fri, 18 Sep 2026 09:00:00 GMT</pubDate>
      <description>"Sidecarless mesh, zero downtime" is a half-truth — and the missing half is exactly the one a regulated cluster cares about.</description>
      <category>Ambient mesh</category>
      <category>Service mesh</category>
      <category>Microsoft Entra ID</category>
      <category>mTLS</category>
      <category>AuthorizationPolicy</category>
      <category>Compliance evidence</category>
      <category>Audit logging</category>
      <category>GitOps</category>
    </item>
    <item>
      <title>GitOps for the mesh — when the pull request becomes the change record</title>
      <link>https://www.abkhan.in/software/blog/31-gitops-for-the-mesh/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/31-gitops-for-the-mesh/</guid>
      <pubDate>Wed, 16 Sep 2026 09:00:00 GMT</pubDate>
      <description>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.</description>
      <category>GitOps</category>
      <category>Microsoft Entra ID</category>
      <category>Compliance evidence</category>
      <category>AuthorizationPolicy</category>
      <category>Drift &amp; posture</category>
      <category>Policy as code</category>
      <category>Secrets &amp; certificates</category>
      <category>Ambient mesh</category>
    </item>
    <item>
      <title>Regional frameworks — one control surface, four rulebooks</title>
      <link>https://www.abkhan.in/software/blog/30-regional-frameworks/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/30-regional-frameworks/</guid>
      <pubDate>Mon, 14 Sep 2026 09:00:00 GMT</pubDate>
      <description>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.</description>
      <category>SAMA</category>
      <category>Compliance evidence</category>
      <category>CERT-In &amp; DPDP</category>
      <category>RBI</category>
      <category>Multi-cluster &amp; residency</category>
      <category>PCI DSS</category>
      <category>AuthorizationPolicy</category>
      <category>Drift &amp; posture</category>
    </item>
    <item>
      <title>Mapping controls to frameworks — PCI-DSS 4.0 on the mesh</title>
      <link>https://www.abkhan.in/software/blog/29-mapping-controls-to-frameworks/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/29-mapping-controls-to-frameworks/</guid>
      <pubDate>Sat, 12 Sep 2026 09:00:00 GMT</pubDate>
      <description>"Our service mesh makes us PCI compliant." If a vendor says that, end the meeting.</description>
      <category>PCI DSS</category>
      <category>AuthorizationPolicy</category>
      <category>Compliance evidence</category>
      <category>Drift &amp; posture</category>
      <category>mTLS</category>
      <category>Policy as code</category>
      <category>Audit logging</category>
      <category>Supply-chain signing</category>
    </item>
    <item>
      <title>Continuous posture and drift — proving the control is still holding</title>
      <link>https://www.abkhan.in/software/blog/28-continuous-posture-and-drift/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/28-continuous-posture-and-drift/</guid>
      <pubDate>Fri, 11 Sep 2026 09:00:00 GMT</pubDate>
      <description>Your admission controller said yes to the policy six months ago. Is the policy still there?</description>
      <category>Drift &amp; posture</category>
      <category>Policy as code</category>
      <category>Compliance evidence</category>
      <category>GitOps</category>
      <category>LGTM stack</category>
      <category>AuthorizationPolicy</category>
      <category>SAMA</category>
      <category>mTLS</category>
    </item>
    <item>
      <title>Turning telemetry into signed evidence</title>
      <link>https://www.abkhan.in/software/blog/27-turning-telemetry-into-signed-evidence/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/27-turning-telemetry-into-signed-evidence/</guid>
      <pubDate>Thu, 10 Sep 2026 09:00:00 GMT</pubDate>
      <description>You have the logs. That is not the same as having evidence.</description>
      <category>Compliance evidence</category>
      <category>Supply-chain signing</category>
      <category>LGTM stack</category>
      <category>Drift &amp; posture</category>
      <category>Multi-cluster &amp; residency</category>
      <category>Audit logging</category>
      <category>Distributed tracing</category>
      <category>PCI DSS</category>
    </item>
    <item>
      <title>Tracing identity through a request</title>
      <link>https://www.abkhan.in/software/blog/26-tracing-identity-through-a-request/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/26-tracing-identity-through-a-request/</guid>
      <pubDate>Tue, 08 Sep 2026 09:00:00 GMT</pubDate>
      <description>You turned on distributed tracing. Grafana draws the pretty waterfall. You feel covered.</description>
      <category>Distributed tracing</category>
      <category>LGTM stack</category>
      <category>Compliance evidence</category>
      <category>Istio</category>
      <category>OpenTelemetry</category>
      <category>.NET &amp; C#</category>
      <category>Audit logging</category>
    </item>
    <item>
      <title>The LGTM stack for compliance evidence</title>
      <link>https://www.abkhan.in/software/blog/25-the-lgtm-stack-for-compliance-evidence/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/25-the-lgtm-stack-for-compliance-evidence/</guid>
      <pubDate>Sun, 06 Sep 2026 09:00:00 GMT</pubDate>
      <description>Loki, Grafana, Tempo, Mimir. Four letters everyone treats as one observability blob. To a regulator they answer four different questions — and putting the wrong one in the wrong store is how evidence quietly disappears.</description>
      <category>LGTM stack</category>
      <category>Compliance evidence</category>
      <category>Distributed tracing</category>
      <category>Multi-cluster &amp; residency</category>
      <category>OpenTelemetry</category>
      <category>Drift &amp; posture</category>
      <category>.NET &amp; C#</category>
      <category>mTLS</category>
    </item>
    <item>
      <title>If you can’t prove it, it didn’t happen — audit logging in the mesh</title>
      <link>https://www.abkhan.in/software/blog/24-if-you-cant-prove-it-it-didnt-happen/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/24-if-you-cant-prove-it-it-didnt-happen/</guid>
      <pubDate>Sat, 05 Sep 2026 09:00:00 GMT</pubDate>
      <description>Your service mesh is already logging every request. Method, path, status code — for free.</description>
      <category>Audit logging</category>
      <category>Compliance evidence</category>
      <category>LGTM stack</category>
      <category>Istio</category>
      <category>.NET &amp; C#</category>
      <category>Distributed tracing</category>
      <category>Microsoft Entra ID</category>
      <category>SPIFFE</category>
    </item>
    <item>
      <title>Threat-modelling a meshed .NET API</title>
      <link>https://www.abkhan.in/software/blog/23-threat-modelling-a-meshed-dotnet-api/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/23-threat-modelling-a-meshed-dotnet-api/</guid>
      <pubDate>Thu, 03 Sep 2026 09:00:00 GMT</pubDate>
      <description>You've spent a dozen articles building controls. Now ask the question nobody budgets for: what does each one do when it BREAKS?</description>
      <category>Threat modelling</category>
      <category>AuthorizationPolicy</category>
      <category>Compliance evidence</category>
      <category>JWT validation</category>
      <category>CERT-In &amp; DPDP</category>
      <category>Egress control</category>
      <category>mTLS</category>
      <category>.NET &amp; C#</category>
    </item>
    <item>
      <title>Egress control and the locked-down cluster</title>
      <link>https://www.abkhan.in/software/blog/22-egress-control-and-the-locked-down-cluster/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/22-egress-control-and-the-locked-down-cluster/</guid>
      <pubDate>Tue, 01 Sep 2026 09:00:00 GMT</pubDate>
      <description>You locked the front door of your Kubernetes cluster. Ingress gateway, token validation, default-deny — the works.</description>
      <category>Egress control</category>
      <category>Service mesh</category>
      <category>Istio</category>
      <category>AuthorizationPolicy</category>
      <category>.NET &amp; C#</category>
      <category>Ambient mesh</category>
      <category>Azure</category>
      <category>Compliance evidence</category>
    </item>
    <item>
      <title>The policy you wrote isn’t the policy you enforce</title>
      <link>https://www.abkhan.in/software/blog/21-the-policy-you-wrote-isnt-the-policy-you-enforce/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/21-the-policy-you-wrote-isnt-the-policy-you-enforce/</guid>
      <pubDate>Mon, 31 Aug 2026 09:00:00 GMT</pubDate>
      <description>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.</description>
      <category>Policy as code</category>
      <category>Kubernetes</category>
      <category>AuthorizationPolicy</category>
      <category>Network policy</category>
      <category>Compliance evidence</category>
    </item>
    <item>
      <title>Network policy and mesh policy — belt and suspenders</title>
      <link>https://www.abkhan.in/software/blog/20-network-policy-and-mesh-policy/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/20-network-policy-and-mesh-policy/</guid>
      <pubDate>Sun, 30 Aug 2026 09:00:00 GMT</pubDate>
      <description>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.</description>
      <category>Network policy</category>
      <category>AuthorizationPolicy</category>
      <category>Policy as code</category>
      <category>SPIFFE</category>
      <category>Compliance evidence</category>
      <category>Istio</category>
      <category>Kubernetes</category>
      <category>PCI DSS</category>
    </item>
    <item>
      <title>Secrets and certificates — for the ones you couldn't eliminate</title>
      <link>https://www.abkhan.in/software/blog/19-secrets-and-certificates/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/19-secrets-and-certificates/</guid>
      <pubDate>Sat, 29 Aug 2026 09:00:00 GMT</pubDate>
      <description>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…</description>
      <category>Secrets &amp; certificates</category>
      <category>Kubernetes</category>
      <category>Workload identity</category>
      <category>GitOps</category>
      <category>Network policy</category>
    </item>
    <item>
      <title>Scopes, roles, and app roles — from claim to decision</title>
      <link>https://www.abkhan.in/software/blog/18-scopes-roles-and-app-roles/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/18-scopes-roles-and-app-roles/</guid>
      <pubDate>Fri, 28 Aug 2026 09:00:00 GMT</pubDate>
      <description>A valid token is not a permission. Authentication proves who you are; it doesn't say you're allowed to do THIS. Two Entra claims decide that — and confusing them is how a valid token does the forbidden thing.</description>
      <category>Scopes &amp; app roles</category>
      <category>Microsoft Entra ID</category>
    </item>
    <item>
      <title>Identity propagation across hops — keeping the user alive</title>
      <link>https://www.abkhan.in/software/blog/17-identity-propagation-across-hops/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/17-identity-propagation-across-hops/</guid>
      <pubDate>Wed, 26 Aug 2026 09:00:00 GMT</pubDate>
      <description>Your service needs to call the next service on a user's behalf. The instinct — forward the user's token — is the confused-deputy bug.</description>
      <category>On-behalf-of flow</category>
      <category>Microsoft Entra ID</category>
      <category>Scopes &amp; app roles</category>
      <category>Workload identity</category>
      <category>mTLS</category>
    </item>
    <item>
      <title>Default-deny — the AuthorizationPolicy that fails closed</title>
      <link>https://www.abkhan.in/software/blog/16-default-deny/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/16-default-deny/</guid>
      <pubDate>Tue, 25 Aug 2026 09:00:00 GMT</pubDate>
      <description>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.</description>
      <category>AuthorizationPolicy</category>
      <category>Network policy</category>
      <category>Istio</category>
      <category>Microsoft Entra ID</category>
      <category>SPIFFE</category>
    </item>
    <item>
      <title>Entra Workload ID Federation on AKS</title>
      <link>https://www.abkhan.in/software/blog/15-entra-workload-id-federation-on-aks/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/15-entra-workload-id-federation-on-aks/</guid>
      <pubDate>Mon, 24 Aug 2026 09:00:00 GMT</pubDate>
      <description>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?</description>
      <category>Microsoft Entra ID</category>
      <category>Workload identity</category>
      <category>Azure</category>
      <category>SPIFFE</category>
      <category>Secrets &amp; certificates</category>
      <category>AKS</category>
      <category>Kubernetes</category>
      <category>AuthorizationPolicy</category>
    </item>
    <item>
      <title>mTLS and SPIFFE — identity on the wire</title>
      <link>https://www.abkhan.in/software/blog/14-mtls-and-spiffe/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/14-mtls-and-spiffe/</guid>
      <pubDate>Sun, 23 Aug 2026 09:00:00 GMT</pubDate>
      <description>Everyone claims they have mTLS. Almost nobody can prove it to an auditor. Those are two different jobs.</description>
      <category>SPIFFE</category>
      <category>mTLS</category>
      <category>Istio</category>
      <category>AuthorizationPolicy</category>
      <category>Secrets &amp; certificates</category>
      <category>Compliance evidence</category>
      <category>Microsoft Entra ID</category>
      <category>Workload identity</category>
    </item>
    <item>
      <title>Defense in depth — validate at the mesh and in the code</title>
      <link>https://www.abkhan.in/software/blog/13-defense-in-depth/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/13-defense-in-depth/</guid>
      <pubDate>Fri, 21 Aug 2026 09:00:00 GMT</pubDate>
      <description>If the gateway already validated the token, why validate it again in the service? Because no single control is the control — and the question that decides your architecture is which direction your mistakes fail.</description>
      <category>mTLS</category>
      <category>Ambient mesh</category>
      <category>SPIFFE</category>
    </item>
    <item>
      <title>Validating Entra JWTs in C#</title>
      <link>https://www.abkhan.in/software/blog/12-validating-entra-jwts-in-csharp/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/12-validating-entra-jwts-in-csharp/</guid>
      <pubDate>Thu, 20 Aug 2026 09:00:00 GMT</pubDate>
      <description>An unverified token is just a string. A HALF-verified one is worse — it looks trusted, gets waved through, and carries an authority it never earned.</description>
      <category>Microsoft Entra ID</category>
      <category>.NET &amp; C#</category>
      <category>JWT validation</category>
    </item>
    <item>
      <title>Terminating user identity at the mesh edge</title>
      <link>https://www.abkhan.in/software/blog/11-terminating-user-identity-at-the-mesh-edge/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/11-terminating-user-identity-at-the-mesh-edge/</guid>
      <pubDate>Wed, 19 Aug 2026 09:00:00 GMT</pubDate>
      <description>A bug that ships to production quietly, in regulated shops, all the time:</description>
      <category>Microsoft Entra ID</category>
      <category>JWT validation</category>
      <category>OAuth 2.0 &amp; OIDC</category>
      <category>AuthorizationPolicy</category>
      <category>.NET &amp; C#</category>
      <category>Istio</category>
      <category>mTLS</category>
    </item>
    <item>
      <title>The integration thesis — Entra for users, Istio for workloads</title>
      <link>https://www.abkhan.in/software/blog/10-the-integration-thesis/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/10-the-integration-thesis/</guid>
      <pubDate>Tue, 18 Aug 2026 09:00:00 GMT</pubDate>
      <description>The most common identity mistake in a Kubernetes estate isn't a weak policy. It's a merged one.</description>
      <category>Microsoft Entra ID</category>
      <category>Workload identity</category>
      <category>Istio</category>
      <category>JWT validation</category>
      <category>mTLS</category>
      <category>SPIFFE</category>
      <category>OAuth 2.0 &amp; OIDC</category>
    </item>
    <item>
      <title>Going passwordless — for users and workloads</title>
      <link>https://www.abkhan.in/software/blog/09-going-passwordless/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/09-going-passwordless/</guid>
      <pubDate>Mon, 17 Aug 2026 09:00:00 GMT</pubDate>
      <description>"Just add an OTP" is now the compliance answer that fails the audit.</description>
      <category>Passwordless</category>
      <category>Microsoft Entra ID</category>
      <category>Conditional Access</category>
      <category>RBI</category>
      <category>SPIFFE</category>
      <category>Azure</category>
      <category>mTLS</category>
      <category>SAMA</category>
    </item>
    <item>
      <title>Workload identity — how machines prove who they are</title>
      <link>https://www.abkhan.in/software/blog/08-workload-identity/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/08-workload-identity/</guid>
      <pubDate>Sun, 16 Aug 2026 09:00:00 GMT</pubDate>
      <description>A user proves who they are with something they know, something they have, or something they are — a password, a passkey, a fingerprint. A service has none of those. It has no fingers, no phone, no memory between restarts. Yet the…</description>
      <category>Microsoft Entra ID</category>
      <category>Workload identity</category>
      <category>SPIFFE</category>
      <category>Azure</category>
      <category>Kubernetes</category>
      <category>AKS</category>
      <category>Passwordless</category>
      <category>.NET &amp; C#</category>
    </item>
    <item>
      <title>Microsoft Entra ID in plain language</title>
      <link>https://www.abkhan.in/software/blog/07-microsoft-entra-id-in-plain-language/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/07-microsoft-entra-id-in-plain-language/</guid>
      <pubDate>Fri, 14 Aug 2026 09:00:00 GMT</pubDate>
      <description>You moved your web apps to Kubernetes and the authentication story fell apart on the way in.</description>
      <category>Microsoft Entra ID</category>
      <category>.NET &amp; C#</category>
      <category>Scopes &amp; app roles</category>
      <category>Azure</category>
      <category>Kubernetes</category>
      <category>Workload identity</category>
      <category>Istio</category>
      <category>Passwordless</category>
    </item>
    <item>
      <title>Identity 101 — OAuth2, OIDC, and Tokens</title>
      <link>https://www.abkhan.in/software/blog/06-identity-101/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/06-identity-101/</guid>
      <pubDate>Wed, 12 Aug 2026 09:00:00 GMT</pubDate>
      <description>Ask five engineers on your team which OAuth flow their service uses. You will get three shrugs, one confident wrong answer, and one person who actually knows. That last person is the one who has read a token expiry error at 2am.…</description>
      <category>OAuth 2.0 &amp; OIDC</category>
      <category>JWT validation</category>
      <category>.NET &amp; C#</category>
      <category>Microsoft Entra ID</category>
      <category>Scopes &amp; app roles</category>
    </item>
    <item>
      <title>Istio Without the Overwhelm</title>
      <link>https://www.abkhan.in/software/blog/05-istio-without-the-overwhelm/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/05-istio-without-the-overwhelm/</guid>
      <pubDate>Tue, 11 Aug 2026 09:00:00 GMT</pubDate>
      <description>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…</description>
      <category>Istio</category>
      <category>Service mesh</category>
      <category>Ambient mesh</category>
      <category>mTLS</category>
      <category>Kubernetes</category>
      <category>.NET &amp; C#</category>
      <category>AuthorizationPolicy</category>
    </item>
    <item>
      <title>What a Service Mesh Actually Does (and What It Doesn't)</title>
      <link>https://www.abkhan.in/software/blog/04-what-a-service-mesh-actually-does-and-what-it-doesnt/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/04-what-a-service-mesh-actually-does-and-what-it-doesnt/</guid>
      <pubDate>Mon, 10 Aug 2026 09:00:00 GMT</pubDate>
      <description>A service mesh is a layer of proxies. That's the whole idea, stripped of the conference-stage mystique. Next to every pod, you run a second container — an Envoy proxy, the "sidecar" — and you route all of that pod's traffic…</description>
      <category>Istio</category>
      <category>Service mesh</category>
      <category>mTLS</category>
      <category>.NET &amp; C#</category>
    </item>
    <item>
      <title>Your First .NET 8 Service on Kubernetes</title>
      <link>https://www.abkhan.in/software/blog/03-your-first-dotnet-8-service-on-kubernetes/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/03-your-first-dotnet-8-service-on-kubernetes/</guid>
      <pubDate>Mon, 10 Aug 2026 09:00:00 GMT</pubDate>
      <description>You have the mental model now. Article 2 gave you a .NET 8 minimal API and the Deployment plus Service YAML that fronts it. Both sit on your disk, doing nothing. A YAML file is not a running service. A cluster does not care about…</description>
      <category>.NET &amp; C#</category>
      <category>Kubernetes</category>
      <category>Docker &amp; containers</category>
    </item>
    <item>
      <title>Kubernetes in Five Boxes</title>
      <link>https://www.abkhan.in/software/blog/02-kubernetes-in-five-boxes/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/02-kubernetes-in-five-boxes/</guid>
      <pubDate>Sat, 08 Aug 2026 09:00:00 GMT</pubDate>
      <description>You've decided to move to Kubernetes. Good. Then you open the documentation and meet forty resource types, three networking layers, and a YAML file that wants to know your pod's DNS policy. This is the moment most people quietly…</description>
      <category>Kubernetes</category>
      <category>.NET &amp; C#</category>
    </item>
    <item>
      <title>What Regulated Enterprises Can't Ignore</title>
      <link>https://www.abkhan.in/software/blog/01-what-regulated-enterprises-cant-ignore/</link>
      <guid isPermaLink="true">https://www.abkhan.in/software/blog/01-what-regulated-enterprises-cant-ignore/</guid>
      <pubDate>Wed, 05 Aug 2026 09:00:00 GMT</pubDate>
      <description>You're moving your web apps to Kubernetes. The kind of apps that ran happily on Windows servers for years. Back there, authentication was almost free. They sat inside the domain, Windows-integrated auth did the quiet work, LDAP…</description>
      <category>mTLS</category>
      <category>Kubernetes</category>
      <category>Istio</category>
      <category>Microsoft Entra ID</category>
      <category>Ambient mesh</category>
      <category>Service mesh</category>
      <category>LGTM stack</category>
      <category>OAuth 2.0 &amp; OIDC</category>
    </item>
  </channel>
</rss>
