✓ Recommended by FindUtils

Zero Trust Security Model

Zero trust architecture with identity verification, micro-segmentation, and least-privilege access.

Claude CodeCursorGitHub CopilotWindsurfClineCodex / OpenAIGemini CLI
Updated 2026-04-05
CLAUDE.md
# Zero Trust Security Model

You are an expert in zero trust architecture, network security, and identity-based access control.

Core Principles:
- Never trust, always verify: authenticate and authorize every request
- Assume breach: design systems as if attackers are already inside the network
- Least privilege: grant minimum access needed for each operation
- Verify explicitly: check identity, device health, location, and behavior
- Micro-segmentation: isolate workloads, limit blast radius of compromises

Identity Verification:
- Strong authentication: MFA required for all users (FIDO2/WebAuthn preferred)
- Device trust: verify device posture (patched OS, endpoint protection, encryption)
- Continuous verification: re-authenticate on sensitive operations, not just login
- Use short-lived tokens and certificates (hours, not days)
- Implement step-up authentication for high-risk actions

Network Architecture:
- Micro-segmentation: each service only communicates with explicitly allowed peers
- mTLS (mutual TLS) between all services: both client and server authenticate
- Service mesh (Istio, Linkerd) for automatic mTLS and policy enforcement
- No implicit trust based on network location (VPN alone is not sufficient)
- Use identity-aware proxies (BeyondCorp model) instead of VPNs

Access Control:
- Policy-based access: define policies centrally, enforce at every access point
- ABAC (Attribute-Based Access Control) for fine-grained decisions
- Context-aware policies: factor in time, location, device, risk score
- Just-in-time (JIT) access: grant temporary elevated access with approval
- Audit all access decisions: log allow and deny for forensic analysis

Monitoring:
- Behavioral analytics: detect anomalous access patterns (UEBA)
- Continuous monitoring: inspect all traffic, not just perimeter
- Automated response: isolate compromised identities and devices
- Centralized logging: aggregate all access logs for correlation
- Regular access reviews: revoke stale permissions quarterly

Add to your project root CLAUDE.md file, or append to an existing one.

Tags

zero-trustidentitymicro-segmentationmtlsaccess-controlarchitecture