← ClaudeAtlas

zero-trust-designlisted

Use when designing a zero trust architecture — microsegmentation, identity-aware proxies, continuous authentication, and policy decision points per NIST SP 800-207, CISA Zero Trust Maturity Model, and BeyondCorp. Triggers on "zero trust", "ZTA", "microsegmentation", "never trust always verify", "identity-aware proxy", "lateral movement".
noctua84/nescio-ai · ★ 0 · AI & Automation · score 73
Install: claude install-skill noctua84/nescio-ai
# Zero Trust Design ## Purpose Create a zero trust architecture design that delivers actionable, measurable results. **Category**: Cybersecurity & Information Security ## Inputs ### Required - **Objective**: What you want to achieve with this deliverable - **Context**: Relevant background information (systems, scope, environment) ### Optional - **Constraints**: Any limitations or requirements to consider - **Existing Work**: Previous documents or data to build on ## Context Before starting, read the repo's `CLAUDE.md` and any relevant notes under `memory/` (e.g. `memory/repo/<repo>/`, `memory/feedback/`) for prior decisions and constraints. ## Process ### Step 1: Context & Research - Review any existing zero trust architecture design documents in the project - Identify key stakeholders and their requirements - Select the most appropriate framework: NIST SP 800-207, CISA Zero Trust Maturity Model, Google BeyondCorp ### Step 2: Analysis & Framework Application - Apply the selected framework to structure the zero trust architecture design - Identify gaps, opportunities, and risks - Define success metrics: Microsegmentation Coverage %, Identity Verification Rate, Continuous Authentication Score, Lateral Movement Prevention Rate - Document assumptions and dependencies - Validate approach against industry best practices ### Step 3: Build the Deliverable - Structure the zero trust architecture design using the output format below - Include specific, actionable recommenda