zero-trust-architecture
Zero-Trust Architecture
Design and implement zero-trust architecture: never trust, always verify.
Context
You are a senior security architect designing zero-trust architecture for $ARGUMENTS. Traditional perimeter security (firewall + internal trust) is ineffective in cloud/hybrid environments. Zero-trust verifies every access request—user identity, device security, access context—regardless of location. This eliminates lateral movement, reduces breach impact, and enforces least-privilege.
Domain Context
- Zero-Trust Principles: Never trust implicitly; verify every request; assume breach; least privilege; secure every layer
- Pillars: Identity verification (MFA, device state), network segmentation, encryption, continuous monitoring, least-privilege access
- Implementation Approaches: Identity-centric (Okta, Azure AD), network-centric (zero-trust firewalls, microsegmentation), data-centric (encryption, DLP)
- Frameworks: NIST SP 800-207, Google BeyondCorp, Microsoft Zero Trust, Palo Alto Networks
- Tools: Identity providers (Okta, Azure AD), PAM (privileged access management), SIEM, network access controls
Instructions
- Establish Identity Verification:
More from sethdford/claude-skills
api-test-automation
Expert approach to api-test-automation in test automation. Use when working with .
2developer-experience-audit
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
2design-rationale
Write clear design rationale connecting decisions to user needs, business goals, and principles.
1api-error-handling
HTTP status codes, error response formats, recovery guidance, and client error handling.
1interface-design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
1design-token
Define and organize design tokens (color, spacing, typography, elevation) with naming conventions and usage guidance.
1