Comwil

Security

Zero trust for mid-sized companies: the first 90 days

Zero trust sounds big, but you can start small. A practical 90-day plan for mid-sized organisations: identity first, then devices, then network and apps.

Published 7 November 20267 min readSecurity

Key takeaways

  • Zero trust means never trusting by default: verify every user and device, give only the access needed and assume a breach is possible.
  • Start with identity: multi-factor authentication and tidy admin accounts deliver the most for the least effort.
  • Add device health checks, segmentation and logging in the second month.
  • Finish with application access, remote access and a practiced incident drill.

What zero trust means

Zero trust replaces the idea of a trusted internal network with three principles: verify explicitly (every user, device and request), grant least privilege (only the access needed, only when needed) and assume breach (design so that one compromised account or device cannot reach everything).

Days 1 to 30: identity and basics

Identity is the new perimeter, so start there.

  • Turn on multi-factor authentication for everyone, administrators first.
  • Inventory users, devices, applications and data locations.
  • Separate administrator accounts from daily-use accounts.
  • Check that backups exist, are offline or immutable, and can actually be restored.
  • Remove accounts and access that nobody needs.

Days 31 to 60: devices, network, visibility

With identity in place, tighten the surroundings.

  • Require devices to meet a health baseline (updated, encrypted, protected) before they reach company data.
  • Use conditional access rules, such as blocking sign-ins from unexpected locations or unmanaged devices.
  • Segment the network so users, servers, guests and devices are separated.
  • Centralise logs for sign-ins, administrator actions and endpoint alerts.

Days 61 to 90: applications and response

Finally, extend control to applications and prepare for the worst.

  • Publish applications through identity-aware access instead of broad network access.
  • Replace legacy remote access with controlled, per-application access where feasible.
  • Write a short incident response plan with roles, contacts and first steps.
  • Run a tabletop exercise and fix what it reveals.

Pitfalls to avoid

Zero trust is a direction, not a product:

  • Buying tools before fixing identity and basics.
  • Rolling out strict rules without explaining them to users.
  • Skipping legacy systems that cannot support modern authentication, rather than isolating them.
  • Treating it as a one-off project instead of a continuous improvement.

Let’s talk about your IT

Tell us what you need. We will come back with a clear proposal and a named contact.