liveBook · Manning

Demilitarized zone

As explained in Secure APIs

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

A demilitarized zone (DMZ), or perimeter network, is an internet-exposed network segment that buffers untrusted traffic from internal systems. It contains hardened components rather than application services themselves. section 9.2

Use a DMZ to reduce exposure and control inbound API traffic:

  • Channel inbound traffic through an API gateway, reverse proxy, load balancer, or similar internet-facing technology in the DMZ. section 9.2
  • Keep services in private subnets without direct internet access, allowing communication across segments only through controlled network bridges and access rules. section 9.2 section 9.5

API infrastructure layout

Place an API gateway and bastion server in the DMZ, route approved inbound requests toward private APIs, and restrict the bastion server to traffic from permitted origins. Keep internal databases and development endpoints out of the internet-facing segment.

How Secure APIs covers it

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.
How it connects
Connects network segmentation with API gateways, reverse proxies, load balancers, WAFs, bastion servers, and private subnets.

Also explained in

Compare how 2 books explain demilitarized zone →

Related concepts

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