We may be moving toward zero trust, and it sounds like a lot of processes could change. What should we expect from the implementation?
What's it actually like implementing zero trust?
Answers
Expect the application inventory and compatibility work to be a bigger deal than the kickoff. Some applications may not fit the access model cleanly, so you'll need to identify exceptions and decide how to handle them rather than assuming everything can move at once.
It also helps to make this an actual project with a clear owner and decisions from management. Without that, it's easy to end up with different parts of the organization deploying different things.
Reply to this answer
Users may push back on MFA enrollment or complain about extra prompts. Plan for the rollout and support, not just the technology. If enrollment is optional in practice, that can leave a big gap in the deployment.
Reply to this answer
Zero trust doesn't necessarily mean asking everyone for another code every few minutes. The access model can replace broad VPN access to a server subnet with more granular access to applications, while using single sign-on and stronger authentication.
For a Windows environment, Windows Hello is worth looking at as an option for a smoother sign-in experience. Security keys are another option to consider. Compare them with phone-based authentication for your users and applications rather than assuming the experience will be the same.
Reply to this answer
Budget time for organizational friction. Leadership needs to settle who can make decisions and how exceptions get approved. Otherwise the work can drag on while teams disagree over ownership or whether they even want the change.
Reply to this answer
Add your answer
Answers are reviewed before publication.
q.307+tramnotch:
Prompt fatigue isn't inevitable, though. The authentication setup and session policies make a difference to how often people are interrupted.