Skip to content
Vol. 1 · Ed. 2026
CyberGlossary
Entry № 801

Mutual TLS (mTLS)

Reviewed byCybersecurity entrepreneur & security researcher

What is Mutual TLS (mTLS)?

Mutual TLS (mTLS)An extension of TLS in which both the client and the server present X.509 certificates so that each side cryptographically authenticates the other.


Mutual TLS is a variant of the TLS handshake in which the server sends a CertificateRequest so that the client must present its own X.509 certificate in addition to the server's. Each side validates the other's certificate chain and verifies possession of the matching private key through the CertificateVerify message before any application data flows. In TLS 1.3 (RFC 8446) the client's Certificate and CertificateVerify are sent in the same encrypted flight as its Finished; TLS 1.2 (RFC 5246) exchanges them in the clear. RFC 8446 also defines a post_handshake_auth extension so a server can demand client authentication mid-session.

mTLS underpins zero-trust service-to-service traffic. SPIFFE/SPIRE (a CNCF project) mints short-lived SVID certificates encoding a workload identity URI, and meshes such as Istio and Linkerd rotate them automatically so every pod-to-pod call is mutually authenticated. Pitfalls are real: CVE-2026-55962 showed wolfSSL servers accepting a client's Finished without a valid certificate after a post-handshake CertificateRequest, defeating the authentication entirely.

Defences include short-lived certificates from a private CA, automated rotation, OCSP/CRL revocation checking, pinning identity to the certificate rather than a bearer token, and rejecting renegotiation that downgrades client auth.

flowchart TD
  A[Client Hello] --> B[Server: Hello + Certificate + CertificateRequest]
  B --> C{Client validates<br/>server chain}
  C -->|invalid| X[Abort handshake]
  C -->|valid| D[Client sends Certificate + CertificateVerify + Finished]
  D --> E{Server validates<br/>client chain & signature}
  E -->|invalid / missing| X
  E -->|valid| F[Mutually authenticated<br/>encrypted session]

● Examples

  1. 01

    A Kubernetes service mesh that issues SPIFFE identities so every pod-to-pod call uses mTLS.

  2. 02

    An API gateway that requires partner systems to present a client certificate signed by an internal CA.

● Frequently asked questions

What is Mutual TLS (mTLS)?

An extension of TLS in which both the client and the server present X.509 certificates so that each side cryptographically authenticates the other. It belongs to the Network Security category of cybersecurity.

What does Mutual TLS (mTLS) mean?

An extension of TLS in which both the client and the server present X.509 certificates so that each side cryptographically authenticates the other.

How do you defend against Mutual TLS (mTLS)?

Defences for Mutual TLS (mTLS) typically combine technical controls and operational practices, as detailed in the full definition above.

What are other names for Mutual TLS (mTLS)?

Common alternative names include: Two-way TLS, Client-authenticated TLS.

● Related terms

● See also