Zero trust is a security strategy built on one idea: never trust, always verify. No user, device or network location is trusted by default, and every request for access is checked against identity, device health and policy before it is granted. It is not a product you buy. It is a series of improvements you make in stages, starting with the identities and systems that matter most.
Key takeaways
- Zero trust replaces the idea of a trusted internal network with continuous, per-request verification.
- NIST SP 800-207 defines the architecture, and CISA’s Zero Trust Maturity Model gives you a way to measure progress.
- Start with an inventory of what you are protecting, then strengthen identity, devices, network segmentation, applications and data in that order.
- Test each stage. A control that has not been validated is an assumption, not a protection.
What zero trust actually means
Traditional security treated the network like a castle: once you were inside the walls, you were trusted. That model breaks down when staff work remotely, applications live in the cloud, and attackers use stolen credentials to walk straight through the front gate.
NIST SP 800-207 describes the alternative. In a zero trust architecture:
- Every resource is protected on its own. Data, applications and services are secured individually, not by the network they sit on.
- Access is granted per session. Being allowed into one system does not grant access to the next.
- Policy is dynamic. Decisions consider who the user is, the state of their device, what they are asking for and whether the behavior is normal.
- Breach is assumed. Systems are designed to limit how far an attacker can move once inside.
Four common zero trust myths
- “We can buy zero trust.” Vendors sell tools that support it, but zero trust is an architecture and a set of policies. No single product delivers it.
- “It means we don’t trust our employees.” It means trust is based on verification rather than location, which protects employees whose credentials are stolen.
- “It requires replacing everything.” Most organizations build on the identity, network and endpoint tools they already own.
- “It is only for large enterprises and federal agencies.” The principles scale down well. Smaller organizations often make faster progress because their environments are simpler.
Measure progress with a maturity model
The CISA Zero Trust Maturity Model organizes zero trust into five pillars, supported by three cross-cutting capabilities: visibility and analytics, automation and orchestration, and governance. Each pillar moves through four stages: Traditional, Initial, Advanced and Optimal.
| Pillar | The question to ask | A practical first step |
|---|---|---|
| Identity | Do we verify every user strongly, every time? | Enforce multifactor authentication, starting with administrators and remote access |
| Devices | Do we know every device that connects, and is it healthy? | Build a complete device inventory and manage every endpoint |
| Networks | Could one compromised machine reach everything? | Separate critical systems from general user networks |
| Applications and workloads | Is access granted per application, or to the whole network? | Put sensitive applications behind identity-aware access |
| Data | Do we know where sensitive data lives and who can reach it? | Classify sensitive data and encrypt it at rest and in transit |
Use the model to record where you are today for each pillar and to set a realistic target for the next twelve months. You do not need to reach Optimal everywhere; you need to reach the right level for the risks you face.
A staged zero trust roadmap
Stage 1: Know what you are protecting
Identify your most important systems and data, sometimes called the protect surface. Map who and what needs to reach them, and how data flows between them. This step sets the priorities for everything that follows.
Stage 2: Strengthen identity
Identity is the foundation of zero trust. Clean up your directory, remove stale and shared accounts, apply least privilege, and control privileged access separately. Move to phishing-resistant multifactor authentication where you can, starting with administrators and remote access.
Stage 3: Know and manage your devices
Keep an accurate inventory of every device that connects to your systems. Make sure each one is managed, patched and protected, and use device health as a condition for access to sensitive resources.
Stage 4: Segment the network
Divide a flat network into zones so a single compromised device cannot reach everything else. Isolate critical systems first, then tighten the rules between segments until each connection is one you have deliberately allowed.
Stage 5: Protect applications and data
Grant access to individual applications instead of the whole network, so a user who needs one system does not get a path to all of them. Classify sensitive data, encrypt it, and control where it can be shared.
Stage 6: Monitor, test and improve
Centralize logs from identity, devices, network and applications so you can spot unusual behavior. Then test your controls. A penetration test shows whether segmentation and access rules actually stop an attacker, and where gaps remain.
Zero trust in the federal space
Federal agencies are already on this path. OMB Memorandum M-22-09 set specific zero trust goals for civilian agencies, and the Department of Defense has published its own zero trust strategy. Contractors that support these agencies are increasingly expected to understand and align with the same principles.
How to tell if it is working
Track a small set of measures that show real progress:
- The share of accounts protected by phishing-resistant multifactor authentication.
- The number of privileged accounts, and how often their access is reviewed.
- The share of devices that are managed and meet your health requirements.
- Whether critical systems are reachable from general user networks.
- Findings from your latest penetration test, and how quickly they were fixed.
How WITS helps
WITS helps organizations work through zero trust in three steps. We assess your network, identity setup and the systems you most need to protect. We recommend a staged roadmap that fits your priorities, budget and current technology. Then we help implement each stage and test it to confirm it works. Learn more about our zero trust architecture services, or see how our managed IT services keep identity, devices and patching in good shape day to day.
Frequently asked questions
How long does it take to implement zero trust?
Zero trust is a journey rather than a single project. Most organizations see meaningful improvement within months by focusing on identity and their most critical systems, then continue to mature over several years.
Do we need to replace our VPN or firewall?
Not necessarily. Many organizations keep their existing tools and change how they are used, for example by narrowing VPN access or adding application-level access for sensitive systems. Replacement decisions come later, based on your roadmap.
Is zero trust only for government organizations?
No. The principles apply to any organization that uses cloud services, supports remote work or holds sensitive data. Federal guidance simply provides a well-documented model to follow.
Where should a small organization start?
Start with identity. Turn on multifactor authentication everywhere, remove unused accounts, and limit administrator rights. These steps are affordable and close many of the paths attackers use most often.
Ready to plan your first stage? Contact WITS and we will help you decide where zero trust should begin in your environment.
