liveBook · Manning

Zero-trust architecture

Also called Zero Trust model, zero-trust approach, zero-trust security

Zero-trust architecture is a security model that grants no implicit trust based on network location or prior access and explicitly verifies and authorizes access requests.

How 7 Manning books explain it

Grokking Software Architecture

Zero trust architecture is a system design that applies zero-trust principles through explicit verification and access controls.

How it is used
Replaces perimeter-only trust with explicit verification for internal and external requests in distributed architectures.
How deep it goes
Defines request verification and explains mTLS, service meshes, segmentation, and automated guardrails without a deployment walkthrough.
Examples
Illustrates lateral movement through an analytics service and the Target HVAC vendor breach.
What you can do after
Evaluate and understand internal trust boundaries and identify controls that could contain a compromised service or vendor.

Read how Grokking Software Architecture explains zero-trust architecture →

Authorization in Action

A zero-trust environment is a security architecture that grants no implicit trust based solely on network location or system boundary.

How it is used
Uses continuous authorization to replace implicit network-location trust in distributed enterprise access.
How deep it goes
Explains request evaluation, policy layers, signal governance, deployment options, and independent progress measures.
Examples
Illustrates document permissions constrained by company-managed devices and extra safeguards outside business hours.
What you can do after
Evaluate and understand zero-trust architecture through policy coverage, signal quality, consistency, perimeter reliance, and exceptions.

Read how Authorization in Action explains zero-trust architecture →

Secure APIs

A security model that continuously verifies requests, denies implicit trust, and grants only explicitly authorized access regardless of network location or origin.

How it is used
Applies security-by-design principles to API requests, responses, internal services, third-party systems, databases, and operational traffic.
How deep it goes
Explains the trust failure, access principles, validation practices, monitoring, and lifecycle placement, while deferring detailed policy implementation.
Examples
Uses complex API data flows, an e-commerce catalog, internal-API exposure, DTOs, parameterized queries, and fuzz-testing tools.
What you can do after
Apply it by validating all data, enforcing explicit access controls, protecting internal APIs, and testing implementations with security tools.

Read how Secure APIs explains zero-trust architecture →

Effective Platform Engineering

A zero-trust network control restricts network access based on explicit verification and policy rather than implicit trust in network location.

How it is used
Applies security assessment to every connected system without treating network location as an implicit trust boundary.
How deep it goes
Explains the principle, contrasts network-layer enforcement, and works through service-only API access without detailing implementation internals.
Examples
Uses Epetech’s service-only APIs, IP and pod-network rules, and a REGISTRY_ONLY outbound traffic policy.
What you can do after
Apply it by securing systems independently and enforcing portable trust requirements through platform policy-as-code.

Read how Effective Platform Engineering explains zero-trust architecture →

Google Anthos in Action

A zero-trust policy requires each access request to be explicitly authenticated and authorized instead of trusting a network location by default.

How it is used
Implements identity-based access controls for hybrid clusters, service-to-service traffic, users, and Google Cloud APIs.
How deep it goes
Explains certificate authorities, workload identities, mTLS, claims-aware policies, and API boundaries, while deferring detailed policy procedures.
Examples
Uses regulated hybrid applications, pod-to-pod restrictions, JWT claims, and managed or enterprise-configured certificate authorities.
What you can do after
Apply declarative identity, encryption, and authorization controls without modifying application code.

Read how Google Anthos in Action explains zero-trust architecture →

Software Security for Developers

The zero-trust principle is a security approach that requires continuous verification and grants no implicit trust based on network location or prior access.

How it is used
Protects service-to-service and external requests by replacing implicit network trust with identity verification and authorization.
How deep it goes
Explains the principle through a concrete impersonation failure and surveys tokens, signing, mTLS, gateways, and replay protection.
Examples
Uses a Kubernetes debug pod, forged service header, fake invoices, request signing, and service-mesh sidecars.
What you can do after
Apply it by requiring verifiable service identity, authenticating every request, enforcing authorization, and rejecting replayed credentials.

Read how Software Security for Developers explains zero-trust architecture →

Microsoft Azure in Action

Zero trust is a security model that grants no implicit trust and continuously verifies each identity and access request before authorizing resource access.

How it is used
Applies deny-by-default identity controls across Azure resources, using Entra ID to manage authentication and authorization.
How deep it goes
Explains the access principle and connects it to Entra ID, MFA, and RBAC, but stops short of detailed network-policy configuration.
Examples
Demonstrates creating an Entra ID user, withholding default access, and granting scoped permissions to subscriptions or resources.
What you can do after
Configure it through Entra ID by creating identities, requiring MFA, and assigning narrowly scoped RBAC permissions.

Read how Microsoft Azure in Action explains zero-trust architecture →

Also covered in

What to know first

Related concepts

Questions about zero-trust architecture

What is zero-trust architecture?

Zero-trust architecture is a security model that grants no implicit trust based on network location or prior access and explicitly verifies and authorizes access requests.

Which Manning books explain zero-trust architecture?

Grokking Software Architecture, Authorization in Action, Secure APIs, Effective Platform Engineering, Google Anthos in Action, Software Security for Developers and Microsoft Azure in Action.

What should I know before learning zero-trust architecture?

Manning books that teach zero-trust architecture usually introduce authentication, TLS, JSON Web Token and mutual TLS first.

What is the difference between zero-trust architecture and implicit trust?

Zero-trust architecture is a security model that grants no implicit trust based on network location or prior access and explicitly verifies and authorizes access requests. Implicit trust is acceptance of a request, recommendation, or action as reliable or safe without independently verifying its basis.

What are the parts of zero-trust architecture?

Zero-trust architecture includes assumed breach and principle of least privilege.

What is zero-trust architecture also called?

Zero-trust architecture is also called Zero Trust model, zero-trust approach or zero-trust security.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.