Platform-led Zero Trust service networking for Fintech
summary
A fintech platform enforces Zero‑Trust by default: clusters deploy mTLS via Istio sidecars and a global deny‑all by default authorization; workload modules auto‑inject sidecars and emit Istio AuthorizationPolicies from a developer whitelist; plans run through Open Policy Agent (OPA) tri‑state plan validation (accept / require approval / reject) before apply; Terraform plans provide preflight checks, pipelines pause for human approval, and canary monitors trigger alerts and auto PRs to remove stale permissions.
AI-written summary · about
chapters (13)
- 0:00Platform-led Zero Trust intro
- 2:25Fintech compliance challenges
- 5:09East-west service security
- 7:31How mutual TLS works
- 9:49Fine-grained auth policies
- 12:10Zero Trust in platform modules
- 13:23Kubernetes cluster security
- 15:33Microservice workflow security
- 18:16Service mesh control plane
- 20:03Trust surface auditing
- 22:49Compliance via automation
- 23:36Key takeaways
- 24:32Q&A
related talks
29mZero Trust for APIs: From Edge to Mesh with Istio
18mImplementing Zero Trust at Enterprise Scale
32mImplementing Zero Trust in a Kubernetes Cluster with Istio
01h 02mIntroduction to Zero Trust Security
35mDemystifying Zero-Trust for Cloud Native Technologies
29mZero Trust Security with Service Mesh
24mZero Trust for Fintech: Building Secure Banking Infrastructure Wit...
40mClarifying Zero Trust: The Model, the Philosophy, the Ethos