~kris/dots

srice

ref: e98f3b030dc24445bd55c68d95d2d81933fd68b3 srice/doc/networking/zero-trust/overview.md -rw-r--r-- 2.5 KiB
e98f3b03 — Kris Yotam chore: sync local state after restore (push updates, no pull) a month ago

#Zero Trust Architecture

#NIST SP 800-207

The canonical document. Three core components:

  • Policy Engine (PE): makes access decisions
  • Policy Administrator (PA): translates decisions into action
  • Policy Enforcement Point (PEP): enforces decisions

Seven tenets. Three deployment models: enhanced identity governance, micro-segmentation, SDP.

#DoD/DISA Zero Trust Reference Architecture v2.0

152 zero trust activities across seven pillars. Thunderdome hit 152/152 by May 2025. All defense components must achieve target ZTA by FY2027.

#CISA Zero Trust Maturity Model v2.0

Five pillars: Identity, Devices, Networks, Apps/Workloads, Data Three cross-cutting: Visibility/Analytics, Automation/Orchestration, Governance Four stages: Traditional, Initial, Advanced, Optimal

#Google BeyondCorp

Core architecture: Device Inventory DB, Device Identity, SSO, Access Control Engine, Access Proxy, Trust Inferrer. No VPN required. All internal apps through access proxy.

#Tailscale as ZT Overlay

WireGuard-based mesh VPN through NAT/firewalls. Zero-config encrypted networking.

Headscale: open-source self-hosted control server alternative.

#Home Lab ZT Implementation

Practical approach:

  1. Tailscale/WireGuard mesh for all inter-host communication
  2. OPNsense firewall with default-deny + VLAN segmentation
  3. mTLS for service-to-service communication
  4. fwknop SPA for any exposed services
  5. Certificate-based device identity (step-ca or cfssl)
  6. Centralized logging and monitoring