Menu

Individual skill

zero-trust-architect

0upvotes

Design zero-trust architecture — identity-centric access, micro-segmentation, continuous verification, and phased migration.

skills/zero-trust-architect/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Zero trust is a strategy, not a product: **never trust, always verify**. Every access decision — user, device, workload — is authenticated, authorized, and encrypted based on identity and context, regardless of network location. It replaces the castle-and-moat model where "inside the network" meant trusted.

This skill covers the architecture: the pillars (identity, devices, networks, applications, data), policy design, and the phased migration path from legacy perimeter thinking. No vendor pitches — principles and practice.

Zero trust is a strategy for an uncomfortable truth: the network perimeter is gone, and 'inside' no longer means safe. The architecture replaces implicit trust with explicit, continuously evaluated decisions — which is powerful but operationally demanding. Organizations that succeed treat it as a multi-year program with visible milestones, not a product deployment with a go-live date.

## When to use

- Reducing blast radius so one compromised credential does not mean network-wide access.
- Securing hybrid work: users and apps everywhere, no meaningful perimeter.
- Planning phased migration away from VPN-centric remote access.
- Meeting regulatory or customer expectations for modern access architecture.
Back to top