mutual TLS
TLS in which both sides present certificates, so the server also proves who the client is.
In more detail
In ordinary TLS only the server proves its identity; mutual TLS makes the client do the same with its own certificate. etcd should require client certificates, so only the API server, which holds one signed by the cluster CA, can connect.
Example
A service mesh such as Consul applies mutual TLS between sidecar proxies without application changes.Related terms
- TLS — The encryption that protects data travelling over a network, the S in HTTPS.
- X.509 certificate — A signed document binding a public key to a name, issued by a certificate authority, used by TLS to prove identity.
- certificate authority — A trusted party that signs certificates, so anyone who trusts it can trust the certificates it issued.
- service mesh — A layer of proxies alongside every service that handles traffic between services: routing, retries, TLS and telemetry.
- Consul — A HashiCorp tool for service discovery and a service mesh that gives services identities and encrypted connections.
Taught in
- Encrypting Pod-to-Pod Traffic: mTLS With Istio And Cilium — Certified Kubernetes Security Specialist (CKS) Exam Prep
- Security Landing Zones & Centralized Egress Inspection — Cloud Security & DevSecOps Engineering
- Zero-Trust Network Access & IdP Federation — Cloud Security & DevSecOps Engineering
- Securing the Kubernetes Control Plane & Node Components — Cloud Security & DevSecOps Engineering
- Works On A Laptop, Fails In Production — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Certificate That Expired On A Sunday — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Port 30080 On Every Node: kube-proxy, Networking And Clients — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- One Dash Too Many: Segmentation With Network Policy — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Draw The Boundaries: Trust And Data Flow — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- One Pod Away: Network Attackers And Sensitive Data — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Threat Model Sprint: Name It, Then Stop It — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Four Alerts, One Incident: Observability And The Mesh — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- A Cluster's First Birthday: PKI And Connectivity — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Platform Sprint: Evidence, Order, Proof — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Which Benchmark, And Who Checked It? Compliance And Frameworks — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Audit Day: Final Review — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- NetworkPolicy And The Consul Service Mesh Boundary — Kubernetes: Production-Grade Container Orchestration
- Authentication, ServiceAccounts And Short Lived Tokens — Kubernetes: Production-Grade Container Orchestration
- TLS And The Handshake — Application Security & Threat Modeling for Engineers
- Port 2375, Open To The Office: Engine TLS And Registry Certificates — Docker Certified Associate (DCA) Exam Prep
- Any Node, Any Task: Overlay Networks, The Routing Mesh And Layer 7 — Docker Certified Associate (DCA) Exam Prep
- Four Questions From The Auditor: Swarm Security, Autolock And Content Trust — Docker Certified Associate (DCA) Exam Prep
- Security Sprint: Eight Questions On Defaults, Trust And Access — Docker Certified Associate (DCA) Exam Prep
- The Night Before: Final Review And Exam Day — Docker Certified Associate (DCA) Exam Prep