The Zero Trust Device Addition
One machine onto a zero-trust network you already run, joined under a tag that already exists, and proved twice over: everything it should reach, reached, and one thing it should not, refused.
Joining a machine to a private network takes a command. Finding out six months later that it never reached the database, or that it dropped off at 3am when a key aged out, takes rather longer.
We put one machine on your network under a tag your policy already carries, so its access follows what the machine is rather than who last signed in to it. Then we test it in both directions and hand you what came back.
We write nothing into your policy. No new rule, no new tag, no widened permission. If nothing in your policy describes what this machine is allowed to reach, we stop before taking your money and tell you what is missing.
What's included
The machine on your network under a tag you already have, so a person leaving does not take a server's access with them
Everything that tag allows, reached from the machine and captured, with the same checks taken beforehand so you can see what changed
One thing that tag does not allow, proved refused. That is the half nobody runs for themselves, and it is the difference between a machine that is on the network and a machine you can trust on it
An expiry decision made on purpose, with the consequence in front of you, written into your register with its date. Servers that drop off at 3am do so because nobody was asked this question
At most one firewall rule on the machine, for this network only, written down word for word with the line that undoes it
A row in the same register the rest of your network lives in: what this machine is, what it reaches, what it was refused, and how to get to it if the network is down
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
Administrator access to your Headscale or Tailscale network for our engineer, or a scoped API key
The tag in your policy this machine joins under, and the machines and ports that tag already reaches
An administrator session on the machine, plus a second way in that does not use the zero-trust network
Your decision on whether the machine should drop off the network when its key expires
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Zero Trust Network Setup
A private network across your machines, running on a coordination server we build on hardware you own, with no subscription and nobody else holding the keys. Each group reaches only the ports you named, and we prove it by showing you an identity with no permission being refused.
The Zero Trust User Onboarding
One person and the machine they work on, put onto a zero-trust network you already run, with somebody on the call to do it with them. Their access proved from their own machine, both what they can reach and what they cannot.
The Guacamole & Zero Trust Network
Your people sign in to one gateway, and that gateway is the only thing on your network allowed to reach the servers behind it. Every session is recorded and kept for a window you choose.
The Wazuh Server & Client Install
Wazuh watching up to 25 of your machines, with two documented tuning passes before handover so the alerts that reach you are worth reading.