-
Workload identity — how machines prove who they are
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…
-
Going passwordless — for users and workloads
"Just add an OTP" is now the compliance answer that fails the audit.
-
The integration thesis — Entra for users, Istio for workloads
The most common identity mistake in a Kubernetes estate isn't a weak policy. It's a merged one.
-
Defense in depth — validate at the mesh and in the code
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.
-
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
-
If you can’t prove it, it didn’t happen — audit logging in the mesh
Your service mesh is already logging every request. Method, path, status code — for free.
-
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…
-
One detection pipeline, four confession clocks — incident reporting across DORA, NIS2, CERT-In and DPDP
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?
-
Multi-cluster mesh for data residency — residency is a topology decision, not a config flag
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…
Multi-cluster & residencyCompliance evidenceSPIFFEAmbient meshIstio