Project & Development
Zero Trust Migration Roadmap: Rate Five Pillars and Pick Your Next Move
Advanced | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)
Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.
This zero trust migration roadmap template rates your current stage on the five CISA Zero Trust Maturity Model pillars and turns it into a four-quarter plan. Four stages (Traditional, Initial, Advanced, Optimal) and three cross-cutting capabilities (Visibility and Analytics, Automation and Orchestration, Governance) are checked. Names and boundaries can change, so check the latest CISA material. Instead of replacing an inside-is-safe VPN setup at once, you choose moves by impact and user burden and place them in Now / Next / Later. Four pitfalls (a product seen as the finish line, network work before identity, extra user effort breeding workarounds, exception VPNs that never close) are guarded against by an identity-first order and a closing date per exception. Start by copying the account count, MFA rate, and VPN user count from your identity admin console as evidence. The whiteboard has four pages; the task board has five columns, 4 parent tasks and 12 subtasks.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Zero Trust Migration Roadmap
How to use (4 pages): ① Write the goal and setup, check the 5 pillars and 3 capabilities (boards①–⑤) → ② Rate each pillar with evidence, check the pitfalls (boards⑥–⑨) → ③ Narrow the next moves by impact vs. user burden (boards⑩⑪) → ④ Place them in Now / Next / Later and decide on exceptions (boards⑫–⑭)
1/4 Set the goal and baseline
① Goal and baseline (start writing here)
- Goal of the migration e.g. Remote work has reached 60% of staff, and we want to fix VPN congestion and the design where anyone inside can reach anything
- Baseline (in numbers) e.g. One identity platform with 1,200 accounts. MFA rate 85%. 900 people use the VPN
- Scope and period e.g. Staff and contractors at HQ and 2 sites. Move in stages over 1 year (4 quarters)
② The 5 pillars of the Zero Trust Maturity Model (CISA, today's setup in one line each)
- The 5 pillars
(today's setup)
- Identity e.g. 30% of the 85% MFA rate in ① is SMS (better than nothing, but weaker than authenticator apps or passkeys)
- Devices e.g. 800 company PCs are in the inventory. Nobody knows how many personal phones read email
- Networks e.g. Sites and remote staff use the VPN. Once connected, every internal server is reachable
- Applications and Workloads e.g. 12 business apps; 4 are legacy and work only from the internal network
- Data e.g. Customer lists live in 3 places, and there is no inventory of what is where
③ Visibility and Analytics (cross-cutting capability)
- Which pillars' logs can you see in one place?
- e.g. Identity sign-in logs are visible. Device and VPN logs are scattered
- How to check: Check each console for log retention and who can view
④ Automation and Orchestration (cross-cutting capability)
- Which tasks are still done by hand?
- e.g. Disabling a leaver's ID waits for word from HR and is manual
- How to check: Count days from leaving date to deactivation in the change log
⑤ Governance (cross-cutting capability)
- Who decides policy and exceptions, and when are they reviewed?
- e.g. An access policy exists but has not been updated in 2 years
- How to check: Check the policy document's update date and approver
2/4 Rate each pillar
⑥ Current stage of each ② pillar (Traditional, Initial, Advanced, Optimal) and evidence
| Current stage | Evidence (where checked) | Pain point | Target stage in 1 year | |
|---|---|---|---|---|
| Identity | e.g. Initial | e.g. Admin console shows MFA at 85%, 30% by SMS | e.g. Disabling a leaver's ID takes 5 days on average | e.g. Advanced (needs phishing-resistant authentication such as passkeys; authenticator apps alone fall short) |
| Devices | e.g. Traditional | e.g. Inventory covers company PCs only. No record for personal devices | e.g. Device health cannot feed access decisions | e.g. Initial |
| Networks | e.g. Traditional | e.g. VPN settings show access to the whole internal network | e.g. Contractor and remote devices can see servers they do not need | e.g. Initial |
| Apps and workloads | e.g. Initial | e.g. 8 of 12 apps support single sign-on | e.g. The 4 old apps work only over the VPN | e.g. Stay at Initial (move 3 of the 4 old apps to single sign-on) |
| Data | e.g. Traditional | e.g. No inventory of where data lives (ask the owners) | e.g. Customer lists are in 3 places | e.g. Initial |
⑦ Pitfall: Believing a product purchase finishes the job
- What happens: e.g. The product goes in, but policy and exceptions stay undecided and the old VPN remains
- How to check: e.g. Compare the ⑥ stage before and after rollout in the evidence column
- Counter-move: e.g. Write results as the stage raised per pillar, not per product
- Verdict now: e.g. Partly applies
⑧ Pitfall: Starting with the network before tidying identity
- What happens: e.g. Traffic is split finely, but who holds which rights is vague, so exceptions pile up
- How to check: e.g. See in ⑥ whether Identity sits below Networks
- Counter-move: e.g. Put the identity inventory cleanup and full MFA in Now first
- Verdict now: e.g. Applies
⑨ Pitfall: More user effort creates workarounds
- What happens: e.g. Extra authentication prompts push some people to pass files through personal cloud accounts
- How to check: e.g. Count complaints in the help desk log and user interviews
- Counter-move: e.g. Pair it with a move that cuts effort, such as passkeys or single sign-on
- Verdict now: e.g. Partly applies
3/4 Narrow the next moves
⑩ Next-move candidates from the ⑥ pain points (impact vs. user burden)
Vertical axis: Impact (higher = bigger) / Horizontal axis: User burden (further right = heavier)
- Do first (high impact, low burden) e.g. Disable a leaver's ID on the day HR notifies you, as a set procedure
- Pair with a burden-reducing move (high impact, high burden) e.g. Switch everyone to passkeys or an authenticator app, department by department
- Do alongside (low impact, low burden) e.g. Rewrite the access policy and set an approver and review date
- Skip this time (low impact, high burden) e.g. Segment the traffic of every site at once. Identity comes first; for now exceptions would pile up and the effect would be small. Revisit once identity and devices are in shape
⑪ Moves chosen from ⑩, prerequisites, and risks
| What the move involves (pillar) | Prerequisite | Risk and counter-measure | |
|---|---|---|---|
| Move A | e.g. Disable a leaver's ID on the day (Identity) | e.g. An agreement that HR notifies you of departures that day | e.g. Missed notice → reconcile the identity inventory with the staff roster monthly |
| Move B | e.g. Move authentication to passkeys or an authenticator app (Identity) | e.g. A list of old apps that do not support it | e.g. More inquiries → stagger the timing by department |
| Move C | e.g. Move the 4 old business apps to single sign-on (Apps) | e.g. Ask the vendor whether it is possible and the cost | e.g. Apps that cannot move → record them as exceptions in ⑭ |
| Option skipped | e.g. Segment traffic at every site (Networks) | e.g. After Identity reaches Advanced and Devices reach Initial or above | e.g. While skipped → narrow what the VPN reaches, department by department |
4/4 Move step by step
⑫ Roadmap (place the moves chosen in ⑪ into Now / Next / Later)
Now Do now
- e.g. Move A: Disable a leaver's ID on the day
- e.g. Move B: Pilot the authentication switch in one department
Next Do next
- e.g. Move B: Roll the authentication switch out to all departments
- e.g. Move C: Move the 4 old business apps to single sign-on
Later Do later
- e.g. Skipped option: Segment traffic at every site
- e.g. Use device health in access decisions
⑬ Pillars and results per quarter (split ⑫ across the year)
| Pillar and move | Result (how to check) | Owner | |
|---|---|---|---|
| Quarter 1 | e.g. Identity: Move A and Move B (1 department) | e.g. Deactivation on the day. Admin console shows 20% switched over | e.g. IT team |
| Quarter 2 | e.g. Identity: Move B for all departments | e.g. 80% use passkeys or an authenticator app | e.g. IT team and department contacts |
| Quarter 3 | e.g. Apps: Move C | e.g. Apps usable only over the VPN drop from 4 to 1 | e.g. App owners and the vendor |
| Quarter 4 | e.g. Devices and Networks: prepare for Later | e.g. Re-rate the ⑥ stages and compare with targets | e.g. Head of IT |
⑭ Pitfall: Exception VPNs that never close (set how exceptions are handled)
- What happens e.g. A VPN kept for apps that cannot move quietly ends up used by more and more people
- How to check e.g. Review reason, owner, end date, and number of users per exception in the exceptions register every quarter
- Counter-move e.g. Give every exception an end date and an owner. When the date passes, take it back to the ⑬ table and decide to extend or retire it
Task board contents
Not started 16 items
Set goal and setup
On page 1, write the migration goal and today's setup in numbers, then check the 5 pillars and 3 cross-cutting capabilities in one line each. The numbers written here become the evidence for the stages on page 2. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.
Pull 3 IdP numbers
The first job is just to pick up three numbers. Open the admin console of your identity platform (e.g. Microsoft Entra ID or the Google Workspace admin console) and note the active account count and the share of people with MFA on. Count VPN users from the VPN admin screen or a user list. Write the three numbers on the Baseline sticky note on board ①. Done when all three are filled in.
One line per pillar
For each of the 5 pillars on board ②, write today's setup in one line. If a pillar cannot be confirmed from an inventory or settings screen, write "unknown" and make it something to check on page 2.
Note 3 capabilities
On boards ③ to ⑤, write today's state of visibility and analytics, automation and orchestration, and governance. Done when each frame has one way to check.
Rate each pillar
On page 2, rate today's stage of each of the 5 pillars with evidence and check whether the 3 pitfalls apply. If stages are not rated the same way, the priority of the moves chosen on page 3 will wobble.
Stage each pillar
In the table on board ⑥, write each pillar's current stage (Traditional, Initial, Advanced, Optimal) and which console or inventory confirmed it. Check stage boundaries against the latest CISA material. Done when all 5 evidence cells are filled in.
Note pains, targets
In the remaining 2 columns of the board ⑥ table, write each pillar's pain point and the stage you aim for in a year. Pain points become the source of the page 3 candidates.
Check 3 pitfalls
On boards ⑦ to ⑨, write for each pitfall what happens, how to check, and the counter-move, then set today's verdict (applies, partly applies, does not apply).
Pick next moves
On page 3, draw candidate moves from the page 2 pain points, plot them by impact and user burden, and narrow them to 3. Only the moves chosen here go onto the page 4 roadmap.
Plot candidates
Draw moves from the board ⑥ pain points and place them in the 4 quadrants of board ⑩. Done when each quadrant has at least one.
Narrow to 3 moves
From Do first and Pair with a burden-reducing move on board ⑩, choose 3 and write them in rows Move A to C on board ⑪. Write one skipped option too.
Write needs, risks
In the board ⑪ table, write each move's prerequisites and risk counter-measures. If a vendor or another department must confirm something, note who to ask.
Migrate in phases
On page 4, place the chosen moves in Now / Next / Later and the quarterly table, and decide how exception VPNs are handled. Move the chosen moves on the task board from Planned to Migrating to track them.
Fill Now/Next/Later
In the 3 columns of board ⑫, place moves A to C from board ⑪ and the skipped option. Put a move that includes identity cleanup in Now.
Plan the quarters
In the board ⑬ table, write the pillar and move, result (how to check), and owner for quarters 1 to 4. The quarter 4 result is re-rating the board ⑥ stages.
Set VPN exceptions
On board ⑭, write what happens, how to check, and the counter-move for exception VPNs, and set the reason, owner, and end date for each exception.