Access Gate plugs in beside the network you already have, so plugging it in changes nothing. You then move your machines behind it, usually a whole subnet at once with one rule on your router. This page shows where the gate goes for your setup and how much of your traffic it ends up protecting.
You do not redesign anything. The gate works with what you already run: DNS, a router, a managed or an unmanaged switch, even networks that are not routed at all. What you have decides how much it can protect.
Pick your setup below to see where the gate goes, what you do, and the coverage you get.
How much of your traffic gets protected?
| Coverage | What it means | When you get it |
|---|---|---|
| Full Zero-Trust | The gate sees and controls every flow that matters | Your network is routed, and you have DNS or a managed switch to send traffic through the gate |
| Partial Zero-Trust | The gate controls what it sees. Traffic that stays on the switch never reaches it, so it stays unprotected | You have an unmanaged switch, or protocols that are not routed |
On the partial side the gate can still filter what reaches it by type of traffic or by device (EtherType or MAC). That is coarse: it blocks or allows a type of traffic, not a person on a session.
What decides where the gate goes?
Three questions about your network:
- Is your traffic routed? Most is. Some exotic or custom protocols are not.
- What is on the network? DNS, a router without DNS, or only a switch.
- Is your switch managed? A managed switch can steer VLANs (it supports PVLAN). An unmanaged one is flat.
From those answers, the gate goes beside your router, in place of your router, or as the switch your machines connect to. The tree above gives the answer for your case.
How do you move your machines behind the gate?
Plugging in the gate is the first half. The second half is sending your machines' traffic through it. Your machines keep their own addresses. Nothing is installed on them, renumbered or rewired. Access Gate gives each one a twin address beside its real one.
There are three ways to do it:
- One rule on your router (recommended). Start here, as in the quick start. The rule sends everything from a subnet or VLAN through the gate (source-based), or a route sends everything going to the machines you name (destination-based). Nothing on the machines changes. To undo, remove the rule.
- One machine at a time. Use names or twin addresses to try the path on a single machine first, or when you cannot add a rule on your router. You move one machine, check it, and can stop or roll back at any point.
- Rules outside the gate (advanced). IP NAT or ARP NAT, when the first two are not possible. They rely on rules you build and maintain on your own router or switches, so support for them is best-effort.
At a large manufacturer in North Carolina, a running production line was moved behind Access Gate in under a minute with one rule on the existing Cisco switch. Production kept running.
Next steps
- Quick start: protect your plant in four steps.
- Architecture overview: the four ways to deploy Access Gate, Lollipop, In-Line, Bastion and Multi-Site Mesh.
- Choose how to connect your machines: the three ways compared, with a guide for each.