DMZ vs Intranet

Published
Length
3 min read

Luis Felipe Dias

All posts

When comparing a dmz vs intranet, the main difference is public exposure. Teams use a DMZ for public apps and an intranet for private tools. A demilitarized zone, or DMZ, sits between the public web and your private network. It holds web servers, mail relays, and DNS hosts that talk to outside users. An intranet is a closed network where your staff and private databases live. Firewalls block outside traffic from reaching the intranet directly. Both zones work together to stop attackers from rea

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

When comparing a dmz vs intranet, the main difference is public exposure. Teams use a DMZ for public apps and an intranet for private tools.

A demilitarized zone, or DMZ, sits between the public web and your private network. It holds web servers, mail relays, and DNS hosts that talk to outside users. An intranet is a closed network where your staff and private databases live. Firewalls block outside traffic from reaching the intranet directly. Both zones work together to stop attackers from reaching your core data.

How dmz vs intranet architectures work in your stack

Network teams split their cloud and local servers into clear security zones. The DMZ acts as a buffer zone at the edge of your network. You place dual firewalls around the DMZ or use a single firewall with three legs. Outside users can reach web servers inside the DMZ over standard web ports. If an attacker breaks into a DMZ host, the inner firewall blocks them. They cannot jump straight into your private network.

The intranet sits behind that inner firewall and stays hidden from the public web. You put internal wikis, source code, and production databases inside the intranet. Only your staff and trusted internal services can send traffic into this private zone. Remote workers must use a VPN or private link to enter the intranet. This setup keeps sensitive business records away from public scanning tools.

In modern cloud setups, these zones map to public and private subnets. A public subnet has a route to an internet router, much like a DMZ. A private subnet has no direct route out, acting like a classic intranet. Teams run load balancers in the public zone and app servers in the private zone. Only specific ports open between the two zones so web traffic can flow.

Tradeoffs and limits of static network zones

Perimeter zones like a DMZ and an intranet solve network routing problems well. Still, IP rules and firewalls cannot see who is running a command. Once an engineer enters the intranet via VPN, the network often trusts them too much. They can reach many databases and servers without further checks. Static firewall rules also grow complex as teams add more cloud services.

A stolen VPN key lets an attacker walk right into your intranet. From there, they can scan internal ports and query private data stores. Network zones also do not log the exact queries a user runs. A firewall log shows a packet moved from one IP to another. It does not show if a user read sensitive customer phone numbers or card numbers.

K8s RBAC Role vs ClusterRole: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

To fix this gap, teams pair network zones with runtime session controls. Network firewalls still block raw public traffic at the edge. Inside the intranet, identity checks verify each user before they open a database session. Granular rules inspect commands in real time instead of trusting an IP address. Data masking can also rewrite emails and national IDs in query results.

When to use each zone in practice

Place any service that accepts unprompted traffic from the internet into the DMZ. This includes public APIs, static asset hosts, and customer login pages. Keep all state and customer data out of the DMZ whenever you can. If a server stores data, move it to the intranet and restrict traffic.

Use the intranet for databases, internal admin tools, and build servers. Never expose intranet databases to the DMZ without strict port and role checks. Combine both zones with user identity checks for complete protection across your stack.

Check database and API queries on the wire

Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev runs beside those services as an open-source proxy, a sidecar for your Postgres or API. It inspects requests coming in and results going back on the wire.

Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run. On responses, hoop.dev data masking rewrites matched sensitive values in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.

Frequently asked questions

Can a server in the DMZ talk to the intranet?

Yes, but only through strict firewall rules on specific ports. Most teams allow DMZ web servers to query intranet databases over one locked port. All other traffic from the DMZ to the intranet stays blocked by default.

Is a cloud public subnet the same as a DMZ?

Yes, a public subnet serves the exact same role in cloud networks. It holds public load balancers and web hosts that need direct internet routes. Private subnets act like the intranet and hold your backend apps and data.

Do we still need an intranet if we use zero trust?

Yes, private networks still add a strong layer of defense against network scans. Zero trust identity checks work best when paired with private intranet subnets. Together, they hide your servers from the web and verify every user session.

The query runs. The emails stay hidden.