Article

Zero Trust Doesn’t Have to Mean Zero Productivity

Security controls that frustrate people get circumvented. Designed well, Zero Trust can make daily work simpler rather than harder.

2 min read
Share

Zero Trust has an image problem. The name suggests suspicion, and the implementations people have experienced often deliver exactly that: more prompts, more approvals, more waiting.

That is a design failure, not a property of the model. The core principle — verify explicitly rather than assume trust based on network location — says nothing about making life harder for employees.

Why friction is a security problem

Security controls that get in the way of legitimate work do not simply annoy people. They get routed around. Someone forwards a document to personal email because the sanctioned path took too long. Someone shares a password because requesting proper access takes three days.

Where Zero Trust can reduce friction

Single sign-on removes logins rather than adding them

Done properly, consolidating identity means one strong authentication in the morning instead of a dozen weaker ones through the day. The security improves and the experience improves at the same time.

Device trust can replace repeated challenges

If the organization can verify that a device is managed, encrypted and current, that signal can substitute for prompting the human repeatedly. The device proves itself so the person does not have to.

Conditional access targets risk instead of everyone

Rather than applying the strictest possible control universally, access decisions can respond to context — who, what device, what application, what sensitivity. Most activity is routine and can be treated as such.

Passwordless is both stronger and faster

Authentication methods bound to a device and a biometric are harder to phish than a password and quicker to use. This is one of the few places in security where the stronger option is also the more pleasant one.

A reasonable sequence

  1. Consolidate identity, so there is one place where access decisions are made.
  2. Get multi-factor authentication in place using phishing-resistant methods where you can.
  3. Establish device management and a clear definition of a healthy device.
  4. Introduce conditional access policies, starting in report-only mode to see what they would have done.
  5. Reduce standing privilege — most administrative access does not need to be permanent.

The question worth asking

For any proposed control, ask what it costs the person doing legitimate work. If the honest answer is “several seconds, occasionally”, that is a reasonable trade. If it is “a support ticket and a day”, expect to be worked around, and design something better.

Working through something like this?

If any of this is relevant to a decision you are facing, we are happy to talk it through — no obligation either way.