Mutual TLS (mTLS) Implementation Patterns

Standard TLS authenticates only the server to the client via a certificate. Mutual TLS (mTLS) extends this: both parties present and verify certificates. The client presents a client certificate after the server requests it (via CertificateRequest in the TLS handshake). The server verifies the client certificate against a trusted CA. mTLS is the foundation of zero-trust networking: instead of relying on network perimeter security, services authenticate each other cryptographically on every connection. Service meshes like Istio, Linkerd, and Consul Connect implement mTLS transparently between microservices.

The mTLS handshake extends TLS 1.3 as follows: after ServerHello and server certificate/Finished, the server sends a CertificateRequest message specifying acceptable certificate authorities and signature algorithms. The client responds with its Certificate (client cert chain) and CertificateVerify (a signature over the transcript using the client's private key). The server verifies the client certificate chain against its trusted CA store and validates the CertificateVerify signature. If both verifications pass, the connection is mutually authenticated. The client cannot forge a CertificateVerify without the private key corresponding to the certificate.