Implicit trust treats a request as safe because it has crossed the perimeter and is moving inside the network. That shortcut can let an attacker who breaches an analytics dashboard pivot into a payment database. section 11.3.3
Zero Trust replaces that assumption with a stricter rule:
- Verify every request, whether it comes from the internet or an internal service, by authenticating and authorizing it and validating it cryptographically. section 11.3.3
- For service-to-service communication, use mutual TLS so both client and server verify each other’s identities. 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 illustrates why neither service should proceed without verifying the other. section 11.3.3
