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.
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
| Name | Kind | Subnet | VLAN | Notes |
|---|---|---|---|---|
| Users - any location | Zone | - | - | The office network is treated the same as home Wi-Fi: no implicit trust |
| Control plane | Zone | 10.20.1.0/24 | - | - |
| Private applications | Zone | - | - | No inbound Internet access - reachable only via the access proxy |
| HR app | Segment | 10.20.10.0/24 | 110 | - |
| Finance app | Segment | 10.20.20.0/24 | 120 | - |
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.
| Device | Type | Hostname | IP address | Role | Owner | Segment |
|---|---|---|---|---|---|---|
| Remote staff | Laptop | - | - | End User Device | IT | Users - any location |
| Office staff | Laptop | - | - | End User Device | IT | Users - any location |
| Mobile devices | Phone | - | - | End User Device | IT | Users - any location |
| Access proxy | Lock | access.corp.example | 10.20.0.10 | Policy Enforcement Point | Security | - |
| Identity provider | Directory / IdP | idp.corp.example | 10.20.1.10 | SSO + MFA | Security | Control plane |
| Device posture | Healthy | - | 10.20.1.20 | MDM / Device Trust | IT | Control plane |
| SIEM | SIEM | - | 10.20.1.30 | Logging & Detection | Security | Control plane |
| hr-app | Server | hr-app-01 | 10.20.10.11 | Application Server | HR systems | HR app |
| hr-db | Database | hr-db-01 | 10.20.10.21 | Primary | HR systems | HR app |
| fin-app | Server | fin-app-01 | 10.20.20.11 | Application Server | Finance systems | Finance app |
| fin-db | Database | fin-db-01 | 10.20.20.21 | Primary | Finance systems | Finance 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 freeOther templates
- Small office networkFirewall, a staff LAN, a server VLAN and isolated guest Wi-Fi - the classic single-site SMB layout.
- Three-tier web applicationDMZ, web, app and data tiers with addressed hosts, labelled flows and two firewall boundaries.
- Hybrid cloudA head office joined to a cloud VPC by site-to-site VPN, with public and private subnets.
- Home labRouter, managed switch and three VLANs - home, lab and IoT - for documenting your own setup.