NSA's Zero Trust Implementation Guidelines: The 91-Activity Roadmap Every Enterprise Needs

The Most Prescriptive Zero Trust Guidance Ever Published

In January 2026, the NSA released something unprecedented: a phased, activity-by-activity roadmap for implementing Zero Trust architecture. The Zero Trust Implementation Guidelines (ZIGs) consist of four documents — a Primer, Discovery Phase, Phase One, and Phase Two — containing 91 specific activities that organizations must complete.

<div style="margin:2.5rem auto;max-width:600px;width:100%;text-align:center;"><svg viewBox="0 0 600 180" xmlns="http://www.w3.org/2000/svg" style="width:100%;height:auto;"><rect width="600" height="180" rx="12" fill="#1a1a2e"/><circle cx="60" cy="90" r="20" fill="none" stroke="#3b82f6" stroke-width="2"/><text x="60" y="94" text-anchor="middle" fill="#3b82f6" font-size="11" font-family="system-ui">User</text><rect x="120" y="65" width="95" height="50" rx="8" fill="#6366f1" opacity="0.85"/><text x="167" y="85" text-anchor="middle" fill="#ffffff" font-size="10" font-family="system-ui">Identity</text><text x="167" y="100" text-anchor="middle" fill="#ffffff" font-size="10" font-family="system-ui">Verify</text><rect x="250" y="65" width="95" height="50" rx="8" fill="#a855f7" opacity="0.85"/><text x="297" y="85" text-anchor="middle" fill="#ffffff" font-size="10" font-family="system-ui">Policy</text><text x="297" y="100" text-anchor="middle" fill="#ffffff" font-size="10" font-family="system-ui">Engine</text><rect x="380" y="65" width="95" height="50" rx="8" fill="#2dd4bf" opacity="0.85"/><text x="427" y="85" text-anchor="middle" fill="#1a1a2e" font-size="10" font-family="system-ui">Access</text><text x="427" y="100" text-anchor="middle" fill="#1a1a2e" font-size="10" font-family="system-ui">Proxy</text><rect x="510" y="65" width="60" height="50" rx="8" fill="#f59e0b" opacity="0.85"/><text x="540" y="94" text-anchor="middle" fill="#1a1a2e" font-size="10" font-family="system-ui">App</text><defs><marker id="arrow5" markerWidth="8" markerHeight="6" refX="8" refY="3" orient="auto"><path d="M0,0 L8,3 L0,6" fill="#e2e8f0"/></marker></defs><line x1="82" y1="90" x2="118" y2="90" stroke="#e2e8f0" stroke-width="1.5" marker-end="url(#arrow5)"/><line x1="217" y1="90" x2="248" y2="90" stroke="#e2e8f0" stroke-width="1.5" marker-end="url(#arrow5)"/><line x1="347" y1="90" x2="378" y2="90" stroke="#e2e8f0" stroke-width="1.5" marker-end="url(#arrow5)"/><line x1="477" y1="90" x2="508" y2="90" stroke="#e2e8f0" stroke-width="1.5" marker-end="url(#arrow5)"/><text x="167" y="140" text-anchor="middle" fill="#94a3b8" font-size="9" font-family="system-ui">MFA + Device</text><text x="297" y="140" text-anchor="middle" fill="#94a3b8" font-size="9" font-family="system-ui">Least Privilege</text><text x="427" y="140" text-anchor="middle" fill="#94a3b8" font-size="9" font-family="system-ui">Encrypted Tunnel</text><text x="300" y="165" text-anchor="middle" fill="#6366f1" font-size="11" font-family="system-ui" font-weight="bold">Never Trust, Always Verify</text></svg><p style="margin-top:0.75rem;font-size:0.85rem;color:#94a3b8;font-style:italic;line-height:1.4;">Zero Trust architecture: every request is verified through identity, policy, and access proxy layers.</p></div>

This isn't another whitepaper saying "assume breach" and "verify everything." This is the NSA telling you exactly what to do, in what order, with specific technical controls for each step.

The timing matters. 81% of organizations plan to implement Zero Trust in 2026 (Gartner), but only 10% of large enterprises will achieve mature, measurable programs by year-end. The gap between intent and execution is the story — and the NSA's ZIGs are designed to close it.

Why Zero Trust Fails (And Why ZIGs Help)

The Common Failure Modes

Most Zero Trust implementations fail because organizations:

1. Buy products instead of building architecture: Vendors sell "Zero Trust solutions" that are really just identity products or network microsegmentation tools. Zero Trust is an architecture, not a product.

2. Skip the discovery phase: You can't protect what you don't know about. Organizations jump to implementing controls without first mapping their assets, data flows, and access patterns.

3. Try to do everything at once: Zero Trust affects identity, network, devices, applications, data, and visibility. Attempting all six simultaneously guarantees failure.

4. Treat it as an IT project: Zero Trust requires business process changes, not just technology changes. Without executive sponsorship and organizational alignment, technical controls get undermined by political resistance.

The NSA's phased approach directly addresses each of these failure modes.

The Four ZIG Documents

Document 1: ZIG Primer

The Primer establishes the foundation:

Key insight: The NSA explicitly states that Zero Trust is a journey with measurable milestones, not a destination. Organizations should plan for 3-5 years to reach advanced maturity.

Document 2: Discovery Phase

Before implementing any controls, you must understand your environment. The Discovery Phase includes activities like:

Discovery Phase Activities (selected):

1. Asset Inventory
   - Identify all hardware assets (managed, unmanaged, IoT)
   - Identify all software assets (licensed, open-source, shadow IT)
   - Map all data repositories and classification levels
   - Document all user accounts (human, service, API)

2. Data Flow Mapping
   - Map all data flows between systems
   - Identify data sensitivity levels
   - Document who accesses what data and why
   - Identify data flows that cross trust boundaries

3. Access Pattern Analysis
   - Document current access control mechanisms
   - Identify over-provisioned accounts
   - Map authentication methods and MFA coverage
   - Identify shared accounts and service accounts

4. Network Architecture Review
   - Document network segmentation
   - Identify flat network segments
   - Map ingress/egress points
   - Document VPN and remote access architectures

This phase typically takes 2-4 months. Skipping it is the number one reason Zero Trust implementations fail.

Document 3: Phase One — Foundation

Phase One builds the core Zero Trust capabilities:

#### Identity Pillar

phase_one_identity:
  activities:
    - Deploy enterprise identity provider (IdP)
    - Implement MFA for all user accounts (phishing-resistant preferred)
    - Establish privileged access management (PAM)
    - Implement just-in-time access for administrative accounts
    - Deploy service account governance
    - Enable continuous authentication signals

  success_criteria:
    - 100% of users authenticated via centralized IdP
    - 100% MFA coverage for interactive accounts
    - All privileged access requires PAM checkout
    - Service accounts inventoried and governed

#### Device Pillar

phase_one_device:
  activities:
    - Deploy endpoint detection and response (EDR)
    - Implement device health attestation
    - Establish device compliance policies
    - Deploy certificate-based device authentication
    - Implement device inventory and classification

  success_criteria:
    - All managed devices have EDR agents
    - Device health checked before resource access
    - Non-compliant devices quarantined or limited
    - BYOD policy enforced via conditional access

#### Network Pillar

phase_one_network:
  activities:
    - Implement network segmentation for critical assets
    - Deploy encrypted DNS (DoH/DoT)
    - Implement TLS inspection for outbound traffic
    - Deploy network access control (NAC)
    - Establish baseline network behavior patterns

  success_criteria:
    - Critical assets isolated in dedicated segments
    - All DNS queries encrypted
    - Outbound traffic inspected for threats
    - Unauthorized devices cannot access network

Document 4: Phase Two — Advanced

Phase Two adds sophisticated capabilities:

#### Microsegmentation

Phase Two Network:
  - Application-level microsegmentation
  - Workload-to-workload encryption (mTLS)
  - Software-defined perimeter (SDP)
  - Dynamic access policies based on risk score
  - Encrypted overlay networks between segments

#### Continuous Evaluation

Phase Two Analytics:
  - User and Entity Behavior Analytics (UEBA)
  - Continuous risk scoring per session
  - Automated policy enforcement based on risk score
  - Machine learning anomaly detection
  - Cross-pillar correlation (device + user + network signals)

#### Data Protection

Phase Two Data:
  - Data Loss Prevention (DLP) at all egress points
  - Automated data classification using AI
  - Rights management for sensitive documents
  - Database activity monitoring
  - Encryption at rest, in transit, and in use

The Implementation Roadmap

Quarter 1: Discovery and Planning

Month 1-2: Discovery Phase
  - Complete asset inventory
  - Map data flows
  - Analyze access patterns
  - Document current architecture
  - Identify quick wins and critical gaps

Month 3: Planning
  - Define Zero Trust scope (start with one business unit or app)
  - Select technology stack
  - Build business case with risk quantification
  - Get executive sponsorship
  - Establish governance structure

Quarter 2-3: Phase One Implementation

Month 4-6: Identity Foundation
  - Deploy/consolidate identity provider
  - Roll out MFA (phishing-resistant: FIDO2/passkeys)
  - Implement PAM for privileged accounts
  - Deploy conditional access policies

Month 7-9: Device and Network
  - Deploy EDR across all endpoints
  - Implement device compliance checking
  - Segment critical networks
  - Deploy encrypted DNS and traffic inspection
  - Establish monitoring baselines

Quarter 4-6: Phase Two

Month 10-12: Advanced Controls
  - Implement microsegmentation
  - Deploy UEBA and continuous risk scoring
  - Enable automated policy enforcement
  - Implement DLP and data classification
  - Cross-pillar integration and testing

Month 13-18: Optimization
  - Tune ML models and reduce false positives
  - Expand scope to additional business units
  - Automate incident response workflows
  - Conduct adversarial testing (red team)
  - Measure and report maturity progress

<div style="margin:2.5rem auto;max-width:600px;width:100%;text-align:center;"><svg viewBox="0 0 600 220" xmlns="http://www.w3.org/2000/svg" style="width:100%;height:auto;"><rect width="600" height="220" rx="12" fill="#1a1a2e"/><path d="M300,25 L380,55 L380,120 Q380,170 300,195 Q220,170 220,120 L220,55 Z" fill="none" stroke="#6366f1" stroke-width="2.5"/><path d="M300,40 L365,65 L365,118 Q365,160 300,180 Q235,160 235,118 L235,65 Z" fill="#6366f1" opacity="0.15"/><rect x="280" y="95" width="40" height="30" rx="4" fill="#6366f1" opacity="0.9"/><path d="M288,95 L288,82 Q288,72 300,72 Q312,72 312,82 L312,95" fill="none" stroke="#6366f1" stroke-width="2.5"/><circle cx="300" cy="110" r="4" fill="#ffffff"/><text x="90" y="60" text-anchor="middle" fill="#3b82f6" font-size="10" font-family="system-ui">Firewall</text><line x1="130" y1="57" x2="218" y2="57" stroke="#3b82f6" stroke-width="1" stroke-dasharray="3,3"/><text x="90" y="100" text-anchor="middle" fill="#a855f7" font-size="10" font-family="system-ui">WAF</text><line x1="110" y1="97" x2="220" y2="85" stroke="#a855f7" stroke-width="1" stroke-dasharray="3,3"/><text x="90" y="140" text-anchor="middle" fill="#2dd4bf" font-size="10" font-family="system-ui">SSO / MFA</text><line x1="130" y1="137" x2="222" y2="120" stroke="#2dd4bf" stroke-width="1" stroke-dasharray="3,3"/><text x="510" y="60" text-anchor="middle" fill="#f59e0b" font-size="10" font-family="system-ui">TLS/SSL</text><line x1="470" y1="57" x2="382" y2="57" stroke="#f59e0b" stroke-width="1" stroke-dasharray="3,3"/><text x="510" y="100" text-anchor="middle" fill="#3b82f6" font-size="10" font-family="system-ui">RBAC</text><line x1="490" y1="97" x2="380" y2="85" stroke="#3b82f6" stroke-width="1" stroke-dasharray="3,3"/><text x="510" y="140" text-anchor="middle" fill="#a855f7" font-size="10" font-family="system-ui">Audit Logs</text><line x1="470" y1="137" x2="378" y2="120" stroke="#a855f7" stroke-width="1" stroke-dasharray="3,3"/></svg><p style="margin-top:0.75rem;font-size:0.85rem;color:#94a3b8;font-style:italic;line-height:1.4;">Defense in depth: multiple security layers protect your infrastructure from threats.</p></div>

Cost Reality Check

Zero Trust implementation costs vary dramatically by organization size:

|----------|-------------|----------------|----------------|

The ROI argument: mature Zero Trust implementations correlate with 50% fewer breaches and 43% lower breach costs. For a large enterprise where the average breach costs $4.9 million, preventing even one breach per year more than justifies the investment.

Technology Stack Recommendations

Based on the NSA's ZIG requirements, here's a practical technology stack:

Identity Layer

Enterprise:
  - Microsoft Entra ID (Azure AD) or Okta Workforce Identity
  - CyberArk or BeyondTrust for PAM
  - FIDO2/Passkeys for phishing-resistant MFA

Budget-conscious / Self-hosted:
  - Keycloak or Authentik for IdP
  - HashiCorp Vault for secrets and PAM
  - WebAuthn/Passkeys for MFA
  - Authelia for SSO/2FA reverse proxy

Device Layer

Enterprise:
  - CrowdStrike Falcon or SentinelOne for EDR
  - Microsoft Intune or Jamf for device management
  - Tanium for device health attestation

Budget-conscious:
  - Wazuh for open-source EDR/HIDS
  - Fleet for device inventory
  - SCEP/EST for certificate management

Network Layer

Enterprise:
  - Zscaler or Palo Alto Prisma for ZTNA
  - Illumio or Guardicore for microsegmentation
  - Cisco ISE or Aruba ClearPass for NAC

Budget-conscious:
  - WireGuard or Tailscale for encrypted overlay
  - Open-source microsegmentation (Cilium, Calico)
  - PacketFence for NAC
  - CrowdSec for behavioral detection

Visibility Layer

Enterprise:
  - Splunk or Microsoft Sentinel for SIEM
  - Exabeam or Securonix for UEBA
  - Palo Alto XSOAR for SOAR

Budget-conscious:
  - Wazuh + Grafana for SIEM
  - Elastic Security for analytics
  - TheHive + Cortex for SOAR
  - Prometheus + Loki for metrics and logs

Common Mistakes to Avoid

Mistake 1: Starting with the Network

Many organizations begin with network microsegmentation because it feels tangible. But without a solid identity foundation, your segmentation policies don't know WHO is accessing resources — making them either too permissive or too restrictive.

Start with identity. Always.

Mistake 2: Forgetting Service Accounts

Human accounts get MFA. Automated accounts get forgotten. Service accounts, API keys, and machine identities often have excessive privileges and no expiration. The NSA's ZIGs explicitly address this: service accounts must be inventoried, governed, and monitored.

Mistake 3: No Measurement

If you can't measure your Zero Trust maturity, you can't prove it's working. Define KPIs from day one:

Zero Trust KPIs:
  - MFA coverage: % of accounts with MFA enabled
  - Privileged access: % of admin access via PAM
  - Device compliance: % of devices meeting health requirements
  - Network segmentation: % of critical assets in segmented zones
  - Mean time to detect (MTTD): Hours from compromise to detection
  - Mean time to contain (MTTC): Hours from detection to containment
  - Lateral movement attempts blocked: Monthly count

Mistake 4: Treating Zero Trust as a One-Time Project

Zero Trust is an operating model, not a project. It requires:

The Global Zero Trust Market Context

The global Zero Trust security market is projected to exceed $78 billion by 2030. The growth is driven by:

<div style="margin:2.5rem auto;max-width:600px;width:100%;text-align:center;"><svg viewBox="0 0 600 200" xmlns="http://www.w3.org/2000/svg" style="width:100%;height:auto;"><rect width="600" height="200" rx="12" fill="#1a1a2e"/><rect x="0" y="0" width="600" height="28" rx="12" fill="#2d2d44"/><rect x="0" y="12" width="600" height="16" fill="#2d2d44"/><circle cx="18" cy="14" r="5" fill="#ef4444"/><circle cx="34" cy="14" r="5" fill="#f59e0b"/><circle cx="50" cy="14" r="5" fill="#2dd4bf"/><text x="300" y="18" text-anchor="middle" fill="#94a3b8" font-size="10" font-family="system-ui">docker-compose.yml</text><rect x="0" y="28" width="35" height="172" fill="#1e1e32"/><text x="25" y="48" text-anchor="end" fill="#94a3b8" font-size="10" font-family="monospace" opacity="0.5">1</text><text x="25" y="66" text-anchor="end" fill="#94a3b8" font-size="10" font-family="monospace" opacity="0.5">2</text><text x="25" y="84" text-anchor="end" fill="#94a3b8" font-size="10" font-family="monospace" opacity="0.5">3</text><text x="25" y="102" text-anchor="end" fill="#94a3b8" font-size="10" font-family="monospace" opacity="0.5">4</text><text x="25" y="120" text-anchor="end" fill="#94a3b8" font-size="10" font-family="monospace" opacity="0.5">5</text><text x="25" y="138" text-anchor="end" fill="#94a3b8" font-size="10" font-family="monospace" opacity="0.5">6</text><text x="25" y="156" text-anchor="end" fill="#94a3b8" font-size="10" font-family="monospace" opacity="0.5">7</text><text x="25" y="174" text-anchor="end" fill="#94a3b8" font-size="10" font-family="monospace" opacity="0.5">8</text><text x="25" y="192" text-anchor="end" fill="#94a3b8" font-size="10" font-family="monospace" opacity="0.5">9</text><text x="45" y="48" fill="#a855f7" font-size="11" font-family="monospace">version</text><text x="100" y="48" fill="#e2e8f0" font-size="11" font-family="monospace">: &quot;3.8&quot;</text><text x="45" y="66" fill="#a855f7" font-size="11" font-family="monospace">services</text><text x="105" y="66" fill="#e2e8f0" font-size="11" font-family="monospace">:</text><text x="55" y="84" fill="#3b82f6" font-size="11" font-family="monospace"> web</text><text x="80" y="84" fill="#e2e8f0" font-size="11" font-family="monospace">:</text><text x="55" y="102" fill="#2dd4bf" font-size="11" font-family="monospace"> image</text><text x="110" y="102" fill="#e2e8f0" font-size="11" font-family="monospace">: nginx:alpine</text><text x="55" y="120" fill="#2dd4bf" font-size="11" font-family="monospace"> ports</text><text x="102" y="120" fill="#e2e8f0" font-size="11" font-family="monospace">:</text><text x="55" y="138" fill="#e2e8f0" font-size="11" font-family="monospace"> - &quot;80:80&quot;</text><text x="55" y="156" fill="#2dd4bf" font-size="11" font-family="monospace"> volumes</text><text x="118" y="156" fill="#e2e8f0" font-size="11" font-family="monospace">:</text><text x="55" y="174" fill="#e2e8f0" font-size="11" font-family="monospace"> - ./html:/usr/share/nginx</text><rect x="365" y="164" width="2" height="14" fill="#6366f1" opacity="0.8"/></svg><p style="margin-top:0.75rem;font-size:0.85rem;color:#94a3b8;font-style:italic;line-height:1.4;">A well-structured configuration file is the foundation of reproducible infrastructure.</p></div>

The Bottom Line

The NSA's Zero Trust Implementation Guidelines are the most actionable government cybersecurity guidance ever published. The 91 activities across four phases provide a concrete roadmap that organizations of any size can follow.

The gap between the 81% who plan to implement Zero Trust and the 10% who will achieve maturity comes down to execution discipline. The ZIGs close that gap by replacing vague principles with specific, sequenced activities.

Don't buy a "Zero Trust product." Follow the roadmap. Start with discovery. Build identity first. Measure everything. And accept that this is a multi-year journey, not a quarter-long project.

The organizations that follow this guidance will be measurably more resilient. The ones that don't will continue to be the ones in the breach headlines.