Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is mTLS?

Mutual TLS authenticates both ends of a connection with certificates, not just the server. It removes shared secrets from service-to-service traffic and adds a lifecycle to manage.

Illustration for the cybersecurity term mTLS
Home / Blog / Cybersecurity Terms / What Is mTLS?
17 November 2026

What Is mTLS?

What Is mTLS?

In an ordinary HTTPS connection, only the server proves who it is. The client validates the certificate, establishes an encrypted channel, and then authenticates itself inside that channel with a password, a token, or an API key. Mutual TLS moves the client’s identity into the handshake itself: the server requests a certificate, the client presents one and proves possession of the matching private key, and the connection is refused if that fails. Nothing gets to the application layer unless both parties are authenticated.

What Changes in the Handshake

The server sends a CertificateRequest message, optionally naming the certificate authorities whose certificates it will accept. The client responds with its certificate chain and a CertificateVerify containing a signature over the handshake transcript, which proves it holds the private key rather than merely a copy of the certificate.

The server then validates the chain, checks expiry and revocation, and — crucially — applies authorisation. This last step is where deployments go wrong. A valid certificate from a trusted authority proves identity, not entitlement. If your trust store contains a public certificate authority, every certificate that authority has ever issued is accepted, which is almost never what anyone intends. Use a private certificate authority dedicated to this purpose, and match on the subject or SAN explicitly rather than accepting anything the chain validates.

Where It Earns Its Keep

What It Actually Prevents

Credential stuffing and password spraying stop working, because there is no password. Stolen bearer tokens become useless on their own, since the token must be presented over a connection authenticated by a key the attacker does not have. Server impersonation and most man-in-the-middle positions collapse, because the proxy cannot produce a client certificate. An attacker who reaches a service over the network but holds no key simply cannot open a session, which closes off the scanning-and-probing stage entirely.

The Lifecycle Problem

This is the reason mTLS is less common than it should be. Every client needs a certificate, every certificate expires, and an expired certificate is an outage rather than a warning. Organisations that deploy mTLS and then manage renewals by spreadsheet get one or two years of benefit followed by a production incident.

Make issuance and renewal automatic. ACME, SPIFFE and SPIRE, cloud certificate services, and service mesh control planes all do this. Prefer short lifetimes — hours or days — so that renewal is exercised constantly and a leaked key has little value; a certificate valid for a year is a credential you cannot revoke reliably, because revocation checking is uneven in practice. Keep private keys in a TPM, a hardware security module, or at minimum a file the application user alone can read, never in a repository or a container image.

Plan the rollout in permissive mode, where the server accepts both authenticated and unauthenticated clients while you migrate, then switch to strict. Monitor certificate expiry centrally and alert well ahead. And remember that terminating mTLS at a load balancer means the application behind it sees nothing unless the balancer forwards the client identity in a header that the application trusts only from that source.

Our Infrastructure Security Testing Services check whether mTLS endpoints authorise properly or merely validate a chain.

FAQ – Frequently Asked Questions

Does mTLS Replace API Keys and Tokens?

It can replace them for authentication, and it strengthens them when used together. A token presented over an mTLS connection is bound to the client certificate, so stealing the token alone achieves nothing. Many organisations keep tokens for fine-grained authorisation, carrying scopes and claims, while mTLS establishes who the calling workload is at the transport layer.

What Certificate Lifetime Should I Use?

As short as your automation comfortably supports. Service meshes commonly issue certificates valid for hours and rotate continuously. Days to weeks is reasonable for workloads with ACME or an internal issuing service. Long-lived certificates measured in years are effectively unrevocable credentials, because revocation checking is inconsistent, and they hide renewal failures until they cause an outage.

Can mTLS Work Through a Load Balancer?

Yes, in two ways. The balancer can pass TCP through untouched, letting the backend terminate mTLS directly, which preserves end-to-end authentication. Or it can terminate and forward the verified client identity in a header. The second approach requires the backend to accept that header only from the balancer, otherwise a client can forge its own identity.

Is a Valid Certificate Enough to Authorise a Client?

No, and treating it as such is the most common mTLS flaw. Chain validation proves the certificate was issued by a trusted authority, not that the holder may call this service. Maintain a dedicated private authority rather than trusting public ones, and check the specific subject or SAN against an authorisation policy before granting access.

Related Terms

You May Be Interested In These

What Is the FREAK Attack?

Cybersecurity Terms

17 November 2026

What Is the FREAK Attack?

Read More
What Is Velociraptor?

Cybersecurity Terms

17 November 2026

What Is Velociraptor?

Read More
What Is the OSI Model?

Cybersecurity Terms

17 November 2026

What Is the OSI Model?

Read More