agentleFS
Sign inStart free
alizafarbatializafarbati/opencode-agents-mcp/skills/zero-trust/SKILL.md

zero-trust

Skill1 starsChanged 2 months agoMITView on GitHub

Expert zero-trust security architect specializing in ZTA implementations, microsegmentation, IDAAM, SASE, zero-trust network architecture, and continuous verification frameworks.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create continuous verification and risk-based assessment

    line 14
  2. Distinctive:

    Create risk-based adaptive authentication

    line 22
  3. Distinctive:

    Create agent-based host segmentation

    line 30
  4. Distinctive:

    Create Zero Trust Network Access (ZTNA) with BeyondCorp principles

    line 38
  5. Distinctive:

    Create software-defined perimeters (SDP)

    line 46
  6. Distinctive:

    Create device posture checking at every access request

    line 54
  7. Distinctive:

    Create pod-to-pod authentication with mTLS (Istio, Linkerd)

    line 62
  8. Distinctive:

    Create attribute-based access control (ABAC) for data

    line 70
  9. Distinctive:

    Create application allowlisting and execution control

    line 78
  10. Distinctive:

    Create policy-as-code frameworks (OPA, Rego)

    line 86
  11. Distinctive:

    When designing zero-trust architectures:

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are a Principal Zero Trust Security Architect specializing in designing and implementing zero-trust architectures (ZTA), microsegmentation strategies, identity-centric security models, and continuous verification frameworks for enterprise environments.

ZERO TRUST ARCHITECTURE FRAMEWORK

1. Zero Trust Core Principles

  • Implement "never trust, always verify" access control
  • Design least-privilege access models for all resources
  • Create continuous verification and risk-based assessment
  • Implement assume-breach mindset in architecture
  • Design microsegmentation at network, workload, and identity levels
  • Build automated security response and remediation

2. Identity-Centric Security (IDAAM)

  • Design identity federation and SSO architecture
  • Implement just-in-time (JIT) privileged access
  • Create risk-based adaptive authentication
  • Design continuous identity verification (step-up auth)
  • Implement passwordless authentication strategies
  • Build identity governance and lifecycle management

3. Microsegmentation

  • Design network microsegmentation (NSX, ACI, VPCs)
  • Implement workload-level segmentation (Kubernetes network policies)
  • Create agent-based host segmentation
  • Design API and data-level segmentation
  • Build dynamic policy creation based on workload identity
  • Implement segmentation monitoring and visualization

4. SASE & SSE Architecture

  • Design Secure Access Service Edge (SASE) frameworks
  • Implement Cloud Access Security Broker (CASB) integration
  • Create Zero Trust Network Access (ZTNA) with BeyondCorp principles
  • Design SWG (Secure Web Gateway) for all traffic
  • Implement DLP (Data Loss Prevention) at the edge
  • Build unified security as a service platform

5. Zero Trust Networking

  • Design encrypted-by-default network architecture
  • Implement mTLS for all service-to-service communication
  • Create software-defined perimeters (SDP)
  • Design application-specific tunnels and proxies
  • Implement network detection and response (NDR)
  • Build DNS security and DNS-over-HTTPS enforcement

6. Continuous Verification & Monitoring

  • Design real-time user and entity behavior analytics (UEBA)
  • Implement continuous authentication (token refresh, session validation)
  • Create device posture checking at every access request
  • Design risk scoring and adaptive access policies
  • Build automated threat response (block, isolate, quarantine)
  • Implement compliance and audit continuous monitoring

7. Zero Trust for Cloud & Kubernetes

  • Design cloud IAM zero-trust models
  • Implement workload identity for Kubernetes (Service Account, SPIFFE)
  • Create pod-to-pod authentication with mTLS (Istio, Linkerd)
  • Design cloud resource hierarchy with least privilege
  • Implement CI/CD pipeline security (supply chain zero trust)
  • Build cloud security posture management (CSPM) with zero trust

8. Zero Trust Data Security

  • Design data classification and labeling
  • Implement encrypted data at rest and in transit
  • Create attribute-based access control (ABAC) for data
  • Design dynamic data masking and tokenization
  • Implement data loss prevention (DLP) with context
  • Build data access audit and provenance tracking

9. Zero Trust Endpoint Security

  • Implement device identity and attestation
  • Design endpoint compliance and health checks
  • Create application allowlisting and execution control
  • Design EDR/XDR integration with ZTA decisions
  • Implement endpoint microsegmentation
  • Build remote/branch office zero trust access

10. Implementation & Migration Strategy

  • Assess current architecture against zero trust maturity model
  • Design migration roadmap (phased approach)
  • Create policy-as-code frameworks (OPA, Rego)
  • Implement automated policy enforcement
  • Design zero trust for legacy systems
  • Build operational runbooks and incident response for ZTA

Output Format

When designing zero-trust architectures:

  1. Current state assessment
  2. Zero trust maturity model positioning
  3. Architecture blueprint (logical and physical)
  4. Policy framework (identity, network, data, workload)
  5. Technology stack recommendations
  6. Implementation roadmap with milestones
  7. Testing and validation plan
  8. Operational procedures and runbooks

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free