CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/Cybersecurity

πŸ” Cybersecurity Β· Network

DMZ Network Architecture

A classic secure network layout: internet-facing services in a DMZ between two firewalls, with internal systems and databases never exposed directly.

More Cybersecurity templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Only the DMZ is reachable from the internet
  • Internal apps and databases sit behind a second firewall
  • Admin access goes through a bastion host with MFA

Prompt used

DMZ network architecture: internet traffic passes a DDoS protection service and an outer firewall/WAF into the DMZ, which holds the reverse proxy/load balancer, mail relay and VPN gateway. An inner firewall allows only specific ports from the DMZ to the internal app servers; databases are in a restricted data zone behind another firewall rule set. Administrators reach servers only through a bastion host with MFA; the office LAN reaches internal apps.

Mermaid code
flowchart LR
  NET((Internet)) -->|"HTTPS / SMTP / IPsec"| DDOS[DDoS Protection]
  DDOS -->|"Clean traffic"| FW1{{Outer Firewall + WAF}}
  subgraph DMZ[DMZ]
    RP[Reverse Proxy / Load Balancer]
    MAIL[Mail Relay]
    VPN[VPN Gateway]
  end
  FW1 -->|"HTTPS 443"| RP
  FW1 -->|"SMTP 25"| MAIL
  FW1 -->|"IPsec / TLS VPN"| VPN
  RP -->|"HTTPS 8443"| FW2{{Inner Firewall}}
  VPN -->|"Remote users"| FW2
  subgraph INT[Internal Zone]
    APP[App Servers]
    BAST[Bastion Host - MFA]
  end
  subgraph DATA[Restricted Data Zone]
    DB[(Databases)]
  end
  FW2 -->|"HTTPS 8443"| APP
  FW2 -->|"SSH 22"| BAST
  APP -->|"SQL 5432"| FW3{{Data Firewall}}
  FW3 -->|"SQL 5432"| DB
  BAST -->|"SSH 22"| APP
  LAN[Office LAN] -->|"HTTPS / SSH"| FW2

Inside this diagram

A network diagram with 12 components in 3 zones and 13 connections.

Zones and their devices

  • DMZ: Reverse Proxy / Load Balancer, Mail Relay and VPN Gateway
  • Internal Zone: App Servers and Bastion Host - MFA
  • Restricted Data Zone: Databases

Outside the zones

  • Internet
  • DDoS Protection
  • Outer Firewall + WAF
  • Inner Firewall
  • Data Firewall
  • Office LAN

Data stores

  • Databases

Connections

  • Internet β†’ DDoS Protection: HTTPS / SMTP / IPsec
  • DDoS Protection β†’ Outer Firewall + WAF: Clean traffic
  • Outer Firewall + WAF β†’ Reverse Proxy / Load Balancer: HTTPS 443
  • Outer Firewall + WAF β†’ Mail Relay: SMTP 25
  • Outer Firewall + WAF β†’ VPN Gateway: IPsec / TLS VPN
  • Reverse Proxy / Load Balancer β†’ Inner Firewall: HTTPS 8443
  • VPN Gateway β†’ Inner Firewall: Remote users
  • Inner Firewall β†’ App Servers: HTTPS 8443
  • Inner Firewall β†’ Bastion Host - MFA: SSH 22
  • App Servers β†’ Data Firewall: SQL 5432
  • Data Firewall β†’ Databases: SQL 5432
  • Bastion Host - MFA β†’ App Servers: SSH 22
  • Office LAN β†’ Inner Firewall: HTTPS / SSH

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

C4 ArchitectureProCybersecurity

Zero Trust Architecture

A zero trust access model: every request to an internal app is checked for user identity, device health and policy, whether it comes from the office or home.

FlowchartCybersecurity

Security Incident Response Workflow

A security incident response process based on the NIST lifecycle: detect, triage, contain, eradicate, recover and learn.

Data FlowCybersecurity

SIEM Log Pipeline

How security logs from across an organisation reach the SIEM: collection, parsing, enrichment, detection rules and alerts for the SOC.

SequenceCybersecurity

SAML Single Sign-On Login

How SAML single sign-on works when an employee opens a SaaS app: redirect to the company identity provider, MFA and a signed assertion.

MindmapCybersecurity

Threat Model Mindmap (STRIDE)

A STRIDE threat model for a web application, listing example threats in each category with the main mitigations.

State MachineCybersecurity

Vulnerability Management Lifecycle

The life of a vulnerability finding: discovered by a scanner, triaged, assigned, fixed, verified and closed, or accepted as risk.