Home/Refreshers/Encrypt and authorise every call between services: refresher
Encrypt and authorise every call between services
Mutual TLS between every service, and a deny-by-default rule for which service may call which.
Remember
- Service A calls service B: inside the cluster.
- The mesh checks both identities: mutual TLS.
- An authorisation rule decides: deny unless allowed.
- Refusals are logged: with the caller's identity, at Standard.
| Platform | Uses | The part that catches people |
|---|---|---|
| Kubernetes | Istio in strict mutual TLS mode with deny-by-default authorisation, deployed by Argo CD | Istio applies policies in its root namespace to every workload, including the ingress gateway, which outside users reach with no mesh identity. |
Run the quick start
| Check which cluster | kubectl config current-context |
| Apply | kubectl apply -k . |
| Watch it sync | kubectl -n argocd get applications |
Watch out
- Mutual TLS gives every workload an identity from its service account.
- Roll out one namespace at a time: sidecars first, then strict mutual TLS, then deny by default with the allow rules you need.
Check it worked
From a pod with no permission, call a protected service. The call is refused with 403. At Standard, the refusal is logged with the caller's identity.