The Zero Trust Policy Change
One change to the access rules on the zero-trust network you already run — up to three rules on one group, granted or taken away. You see who loses what before we touch anything, and we run the way back before we need it. Priced per change, so you buy one whenever a rule needs to move.
Changing an access rule is a two-minute job with a bad afternoon attached. Tighten the wrong line and the people who still need that server find out by not being able to work, and you find out from them.
Before we change a character, you get a page naming who reaches each affected resource today, who reaches it afterwards, and the part you are worrying about: who carries on as they were. Then we write the way back and run it, so the undo is known to work rather than known to exist.
Our engineers build these networks, and they have watched a policy reload take an estate offline, so a change that takes access away happens with you on the call and your sessions held open. You pay per change: buy one when a rule needs to move, or two or three when an access review turns up a short list.
What's included
A written page, before anything changes, naming who reaches each affected resource today, who reaches it afterwards, and who carries on untouched
Rules taken away as well as added, which is the half most people would rather not own — done with you on the call, your sessions held open, and each machine checked the moment it lands
The way back written and run before we need it, then handed to you, so the undo is proved rather than promised
The result proved from both sides: the people who should reach it do, and the ones who should not are refused, tested from real machines rather than from the policy checker
A second route into every affected machine, tested on the day. If one does not work we hand you the edit and the tested way back instead of making a change we cannot walk back
Your policy otherwise left as we found it. Anything that looks wrong to us goes in the report, and we correct none of it on the way past
A record of the policy before and after, side by side, with the evidence and the date against it
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 group, whether you are granting, removing or moving access, and up to three host:port rules (copied exactly from your policy for a removal)
One identity that should reach the resource afterwards, one that should not, and machines we can test from
A second way into every machine the change could affect, and a time with you on the call if access is being taken away
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 Offboarding
One person taken off the zero-trust network you already run, with proof they are off: their own live connection cut while you watch, and the joining key they still hold refused when we try it. Priced per person, so you buy one the day somebody leaves.
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.