In standard TLS, the server proves its identity with a certificate. In mutual TLS (mTLS), the client presents one too, so both services verify each other before exchanging data. section 11.3.3
Two services check each other
When the Order Service contacts the Customer Service, both present certificates and verify each other’s identities. The Order Service then presents an application token, which the Customer Service checks for least-privilege access. section 11.3.3
Figure 11.5 In a Zero Trust world, you don't take anyone's word for it. mTLS is the "blind date" of architecture: neither party moves forward until both have verified each other's identity.
The blind-date analogy shows why mTLS requires both sides to verify identity before proceeding. section 11.3.3
















