liveBook · Manning

Demilitarized zone

A demilitarized zone is a separately controlled network segment between untrusted external networks and protected internal resources that hosts exposed systems while limiting internal access.

How 2 Manning books explain it

Secure APIs

A demilitarized zone is a hardened network segment exposed to untrusted external traffic and positioned between the internet and an internal network.

How it is used
Channels inbound API traffic through hardened internet-facing components while keeping backend services private.
How deep it goes
Defines the segment, identifies its gateway components, and connects it to subnet isolation and controlled cross-segment communication.
Examples
Uses API gateways and bastion servers in the DMZ, with private APIs, databases, and development endpoints kept internal.
What you can do after
Designs inbound API infrastructure that exposes selected endpoints while isolating internal services from direct internet traffic.

Read how Secure APIs explains demilitarized zone →

Acing the CCNA Exam: Volume 2 Advanced Networking and Security

A demilitarized zone is an isolated network segment for systems that must be reachable from untrusted networks while limiting exposure of internal hosts.

How it is used
Uses a separate zone to expose selected servers while limiting access to internal hosts.
How deep it goes
Explains DMZ placement and inter-zone policy relationships without detailing device-specific configuration.
Examples
Uses public-facing servers as the concrete example of systems placed in a DMZ.
What you can do after
Evaluate network layouts by identifying which internet-reachable servers belong in a DMZ rather than the Inside zone.

Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains demilitarized zone →

Related concepts

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.