This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
ZTNA gives a person access to an application after a check, instead of placing the person on a whole subnet. The readiness list drafts questions. It does not deploy a broker and it does not replace your VPN until you have written what still needs the VPN.
The application, the identity provider, and the device check are three names. If any name is missing, you are not ready, and the honest result is the gap. Do not put the application on the internet with no check to make the diagram look finished.
One application. Management of the network devices is not the first ZTNA target. Secrets and tokens stay in the store.
This page is not a product certification and not a reason to disable the firewall.
The change you can finish
Apply nothing during the writing of the note. When the lab window opens, it is one change on the device named in the ticket. Read the draft, then the device, then decide.
Rollback is the file or the revision you saved first. You do not invent a rollback after the only copy is gone.
- Name one application.
- Name the identity check.
- Name what still needs the VPN.
- Write the gap if a name is missing.
- Do not publish the application to the world.
- Do not disable a firewall rule in this hour.
Mistakes that outlive the command
Zero Trust Network Access (ZTNA) Explained goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- The VPN removed with no replacement path.
- An application exposed with no check.
- Every application in one list.
- A certification claimed from the checklist.
- A token in the note.
Decisions to write down
One decision for Zero Trust Network Access (ZTNA) Explained: One application is named. Identity is named or the gap is. The VPN stays until the path is written. The firewall stays. And no token was saved.
Checks before you call it done
Confirm this before you call the change done: The application is in the note. The check is written. The VPN exception is written. Nothing was published. And nothing was disabled. If one of those fails, stop.
Before you leave the device
Zero Trust Network Access (ZTNA) Explained ends when the hostname on the device matches the hostname in the ticket. If it does not, you are on the wrong box. Stop. A command that succeeded on the wrong box is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the device and does not know which interface is the uplink. You delete a line that names a device, a zone, or a prefix you did not write down.
0.0.0.0/0 is not kept because a sample included it. A source you can say is the source you keep. 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. They belong in the note. They are not prefixes you type onto a production device because they appeared in a draft.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, a community string, or a pre-shared key you save in the ticket or in git. The real secret stays in the store.
One change is the window. A VLAN and a routing protocol and a VPN do not share it. If two things move and the result is wrong, you will not know which one did it. The next feature waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a device nobody can rebuild. Restore the copy you took first.
A second person reads the device name and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the device alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not a permission to touch a network you do not administer. The pillar guide owns the wider design. This page owns one lab proof.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.