liveBook · Manning

Mutual TLS

As explained in Grokking Software Architecture

A TLS configuration in which both communicating endpoints authenticate each other using certificates.

Mutual TLS (mTLS) is a two-way ID check for a secure connection. In a typical HTTPS connection, the server presents a certificate to prove its identity to the client. With mTLS, the client also presents a certificate, so both endpoints verify each other before exchanging application data. section 11.3.3

An order service calls a customer service

The two services may share an internal network, but neither assumes the other is safe. They first use mTLS to verify each other’s identity. The order service then presents an application token, which the customer service checks to determine whether the request has the necessary permissions. section 11.3.3

That distinction matters: mTLS establishes who is communicating; authorization checks what the caller is allowed to do. In a Zero Trust architecture, an internal network location is not a substitute for either check. Mutual authentication also helps defend against spoofing, such as a rogue container pretending to be a legitimate service. section 11.3.3 section 11.6

The protection comes with an operational cost. One approach uses a service mesh with sidecar proxies to automate encryption of internal traffic, but deploying that infrastructure adds overhead. Treat mTLS as one layer of a broader security architecture, not as a replacement for application authorization. section 12.6.1 section 11.4 section 11.3.3

How Grokking Software Architecture covers it

How deep it goes
Explains two-way certificate verification and a subsequent token check, without providing configuration steps.
Examples
Illustrates an order service calling a customer service and a rogue container impersonating a service.
What you can do after
Evaluate/understand how mutual authentication fits alongside authorization and the operational overhead of a service mesh.
How it connects
Connects mutual TLS to Zero Trust, authorization, least privilege, service meshes, and spoofing.

Also explained in

Compare how 9 books explain mutual TLS →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.