Zero trust architecture diagram template

A zero trust access layout. User devices, whether remote, in the office or mobile, reach private applications only through an identity-aware access proxy. The proxy checks every request with the identity provider (SSO and MFA) and a device posture service, and sends its access logs to a SIEM.

The applications have no inbound Internet access of their own. The office network is treated the same as any other network: being on it grants nothing.

Use this template freeIn the editor: File → New from template → Zero trust access
Users - any locationControl plane10.20.1.0/24Private applicationsHR app10.20.10.0/24 · VLAN 110Finance app10.20.20.0/24 · VLAN 120Remote staffOffice staffMobile devicesAccess proxy10.20.0.10Identity provider10.20.1.10Device posture10.20.1.20SIEM10.20.1.30hr-app10.20.10.11hr-db10.20.10.21fin-app10.20.20.11fin-db10.20.20.21
The template as it opens in Schema: 11 devices, 5 zones and segments, 10 connections.

How it's laid out

  • The access proxy is the policy enforcement point. The identity provider, device posture service and SIEM sit together in a control plane segment.
  • Each application has its own segment and VLAN, with its database alongside it.
  • It comes with a zero trust rule pack: user devices must not connect directly to applications, the proxy must be connected to an identity provider and to logging, and applications must not be reachable from the Internet.

Networks and segments

NameKindSubnetVLANNotes
Users - any locationZone--The office network is treated the same as home Wi-Fi: no implicit trust
Control planeZone10.20.1.0/24--
Private applicationsZone--No inbound Internet access - reachable only via the access proxy
HR appSegment10.20.10.0/24110-
Finance appSegment10.20.20.0/24120-

Device inventory

In Schema this table isn't a separate document. It's generated from the diagram, can be edited in place, and exports as CSV.

DeviceTypeHostnameIP addressRoleOwnerSegment
Remote staffLaptop--End User DeviceITUsers - any location
Office staffLaptop--End User DeviceITUsers - any location
Mobile devicesPhone--End User DeviceITUsers - any location
Access proxyLockaccess.corp.example10.20.0.10Policy Enforcement PointSecurity-
Identity providerDirectory / IdPidp.corp.example10.20.1.10SSO + MFASecurityControl plane
Device postureHealthy-10.20.1.20MDM / Device TrustITControl plane
SIEMSIEM-10.20.1.30Logging & DetectionSecurityControl plane
hr-appServerhr-app-0110.20.10.11Application ServerHR systemsHR app
hr-dbDatabasehr-db-0110.20.10.21PrimaryHR systemsHR app
fin-appServerfin-app-0110.20.20.11Application ServerFinance systemsFinance app
fin-dbDatabasefin-db-0110.20.20.21PrimaryFinance systemsFinance app

Rules it checks

The template comes with these rule packs switched on. Schema checks them as you edit and marks anything that breaks a rule on the canvas. Every rule can be edited, turned off or deleted.

Documentation completeness

Every server, database and network device has the fields someone on call at 3am will need: an address, an owner, a role.

  • Servers must have an IP address
  • Servers must have an owner
  • Servers must have a role
  • Servers must record their OS
  • Databases must have an IP address
  • Databases must have an owner
  • Firewalls must have an IP address
  • Routers must have an IP address

Zero trust access

User devices reach applications only through an access proxy, the proxy checks identity and logs every request, and applications aren't exposed to the Internet.

  • Laptops must connect through an access proxy
  • Workstations must connect through an access proxy
  • Mobile devices must connect through an access proxy
  • Laptops must not connect directly to servers
  • Workstations must not connect directly to servers
  • Workstations must not connect directly to databases
  • Servers must not connect directly to the Internet
  • Databases must not connect directly to the Internet
  • Servers reached across a segment boundary must go through an access proxy
  • Access proxies must be connected to a directory or identity provider
  • Access proxies should send their logs to a SIEM
  • Laptops must have an owner

Start from this template

Open it in Schema, replace the example addresses with yours, and you have a diagram, an inventory and a written report of your network. Free during early access.

Use this template free

Other templates