Contract
- Input: current architecture, identity provider, network topology, compliance requirements.
- Output: zero trust architecture + identity model + segmentation policy + policy rules.
- Scope: designs architecture and policy; does not modify production auth or network config unless explicitly instructed.
- Rule: designs architecture and policy; does not modify production auth or network config unless explicitly instructed.
- Rule: documented standards override defaults; explicit project rules take precedence.
- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.
Provenance
| Question |
Answer |
| What is the source of truth? |
The user's request, originating spec/issue, and the skill's declared outputs |
| What is in scope? |
Work covered by the skill's acceptance criteria and completion rules |
| What is explicitly out of scope? |
Files, behaviors, and decisions outside the skill's declared boundary |
| Who or what consumes this artifact afterward? |
The next skill in the workflow or the user |
| What evidence proves it is done? |
Completion criteria met, artifact saved, validation passed |
| What risk remains? |
Subjective judgment calls, missing context, or external dependency failures |
Artifact
Emit ZeroTrustArtifact as both:
- JSON:
.agents/skills/platform/artifacts/zero-trust/{identifier}.json
- Markdown view: same filename with
.md extension
Zero Trust Architecture
Design a zero trust architecture — identity, per-request auth, microsegmentation, policy — with explicit trust tiers, continuous verification, and least-privilege enforcement.
Process
1. Define trust model
- Core principle: never trust, always verify; assume breach.
- Trust tiers (device posture, user identity, network location, application state).
- Continuous verification signals (MFA, device health, behavioural analytics, geo-risk).
- Session posture (short-lived tokens, step-up auth, conditional access).
Completion criterion: trust model and verification signals documented.
2. Identity fabric
- Identity provider (IdP) and federation (SSO, SAML, OIDC).
- User lifecycle (joiner, mover, leaver; just-in-time provisioning).
- MFA policy (required, step-up for sensitive actions, phishing-resistant).
- Service identity (machine-to-machine, workload identity, SPIFFE).
- Privileged access management (break-glass, just-in-time elevation, session recording).
Completion criterion: identity fabric with IAM policies and MFA requirements defined.
3. Per-request authentication and authorisation
- Authentication (identity proof at every request, token validation, session binding).
- Authorisation model (RBAC, ABAC, PBAC, ReBAC).
- Fine-grained permissions (resource-level, action-level, attribute-based).
- API gateway and service mesh enforcement (mTLS, JWT validation, rate limiting).
Completion criterion: per-request auth model and enforcement points defined.
4. Microsegmentation
- Network zones (internal, DMZ, database, management).
- Workload segmentation (namespace, cluster, application tier).
- East-west traffic rules (default deny, explicit allow, service-to-service auth).
- Data segmentation (classification, encryption, access logging).
Completion criterion: microsegmentation policy with default-deny rules defined.
5. Policy engine
- Policy as code (OPA / Rego, Cloud IAM, Kubernetes admission).
- Policy categories (identity, network, data, infrastructure).
- Decision flow (who can access what, under which conditions).
- Audit and observability (policy decisions logged, denied requests alerted).
Completion criterion: policy engine rules, decision flow, and enforcement points defined.
6. Monitoring and verification
- Telemetry (auth events, policy decisions, network flows,异常访问).
- Dashboards (trust score, policy violation rate, MFA adoption).
- Alerting (privileged access anomalies, impossible travel, token reuse).
- Periodic red teaming and breach simulation.
Completion criterion: monitoring, dashboard, and alerting rules defined.
Rules
- Rule: start with identity; zero trust without strong identity is theatre.
- Rule: enforce least privilege by default; allow-list exceptions with time-bound approval.
- Rule: encrypt all traffic (mTLS east-west, TLS north-south); verify certificates at every hop.
- Rule: log every auth decision and policy evaluation; make logs queryable for incident response.
- Rule: phase rollout by workload criticality; never deploy all-or-nothing zero trust.
Completion
- the skill's completion criteria are explicitly checked
- the artifact is saved and validated
- any blockers or skipped validations are documented
- the next consumer is identified or the work is handed off
@include .agents/skills/platform/contract-base.xml
1---2name: "zero-trust"3category: "sec"4maturity: "stable"5version: "1"6description: "Design zero trust architecture — identity, per-request auth, microsegmentation, policy — with explicit trust tiers, continuous verification, and least-privilege enforcement."7license: "MIT"8capabilities:9 - apply zero trust methods within explicit sec boundaries10 - analyze design zero trust architecture — identity, per-request auth, microsegmentation, policy — with explicit trust tiers, continuous verification, and least-privilege enforcement with assumptions, constraints, and failure modes11 - produce and validate a sec artifact with evidence, decisions, and next steps12outputs: "zero trust architecture + identity model + segmentation policy + policy rules."13sideEffects: []14dependencies: []15stopCondition: "Architecture documented; identity model defined; segmentation and policy rules documented."16risk: "medium"17trustTier: "3"18maxIterations: "6"19promptVersion: "2.0"20artifactType: "sec"21modelTier: "reasoning"22evaluators: ["behavioral", "regression"]23fixturesPath: .agents/skills/platform/fixtures/behavioral/zero-trust.json24diataxis: "how-to"25tags: ["sec"]26compatibility: []27approvalRequired: "true"28approvalFor: []29metadata:30 source: https://skillmd.com/skills/quantumquirkxyz/zero-trust31---3233## Contract3435- Input: current architecture, identity provider, network topology, compliance requirements.36- Output: zero trust architecture + identity model + segmentation policy + policy rules.37- Scope: designs architecture and policy; does not modify production auth or network config unless explicitly instructed.38- Rule: designs architecture and policy; does not modify production auth or network config unless explicitly instructed.39- Rule: documented standards override defaults; explicit project rules take precedence.40- Rule: if blocked by missing context or dependencies, surface the blocker before proceeding.4142## Provenance4344| Question | Answer |45|---|---|46| What is the source of truth? | The user's request, originating spec/issue, and the skill's declared outputs |47| What is in scope? | Work covered by the skill's acceptance criteria and completion rules |48| What is explicitly out of scope? | Files, behaviors, and decisions outside the skill's declared boundary |49| Who or what consumes this artifact afterward? | The next skill in the workflow or the user |50| What evidence proves it is done? | Completion criteria met, artifact saved, validation passed |51| What risk remains? | Subjective judgment calls, missing context, or external dependency failures525354## Artifact5556Emit `ZeroTrustArtifact` as both:57- JSON: `.agents/skills/platform/artifacts/zero-trust/{identifier}.json`58- Markdown view: same filename with `.md` extension596061# 62# 63# Zero Trust Architecture6465Design a **zero trust architecture** — identity, per-request auth, microsegmentation, policy — with explicit trust tiers, continuous verification, and least-privilege enforcement.6667## Process6869### 1. Define trust model70- Core principle: never trust, always verify; assume breach.71- Trust tiers (device posture, user identity, network location, application state).72- Continuous verification signals (MFA, device health, behavioural analytics, geo-risk).73- Session posture (short-lived tokens, step-up auth, conditional access).7475**Completion criterion:** trust model and verification signals documented.7677### 2. Identity fabric78- Identity provider (IdP) and federation (SSO, SAML, OIDC).79- User lifecycle (joiner, mover, leaver; just-in-time provisioning).80- MFA policy (required, step-up for sensitive actions, phishing-resistant).81- Service identity (machine-to-machine, workload identity, SPIFFE).82- Privileged access management (break-glass, just-in-time elevation, session recording).8384**Completion criterion:** identity fabric with IAM policies and MFA requirements defined.8586### 3. Per-request authentication and authorisation87- Authentication (identity proof at every request, token validation, session binding).88- Authorisation model (RBAC, ABAC, PBAC, ReBAC).89- Fine-grained permissions (resource-level, action-level, attribute-based).90- API gateway and service mesh enforcement (mTLS, JWT validation, rate limiting).9192**Completion criterion:** per-request auth model and enforcement points defined.9394### 4. Microsegmentation95- Network zones (internal, DMZ, database, management).96- Workload segmentation (namespace, cluster, application tier).97- East-west traffic rules (default deny, explicit allow, service-to-service auth).98- Data segmentation (classification, encryption, access logging).99100**Completion criterion:** microsegmentation policy with default-deny rules defined.101102### 5. Policy engine103- Policy as code (OPA / Rego, Cloud IAM, Kubernetes admission).104- Policy categories (identity, network, data, infrastructure).105- Decision flow (who can access what, under which conditions).106- Audit and observability (policy decisions logged, denied requests alerted).107108**Completion criterion:** policy engine rules, decision flow, and enforcement points defined.109110### 6. Monitoring and verification111- Telemetry (auth events, policy decisions, network flows,异常访问).112- Dashboards (trust score, policy violation rate, MFA adoption).113- Alerting (privileged access anomalies, impossible travel, token reuse).114- Periodic red teaming and breach simulation.115116**Completion criterion:** monitoring, dashboard, and alerting rules defined.117118## Rules119120- Rule: start with identity; zero trust without strong identity is theatre.121- Rule: enforce least privilege by default; allow-list exceptions with time-bound approval.122- Rule: encrypt all traffic (mTLS east-west, TLS north-south); verify certificates at every hop.123- Rule: log every auth decision and policy evaluation; make logs queryable for incident response.124- Rule: phase rollout by workload criticality; never deploy all-or-nothing zero trust.125126## Completion127128- the skill's completion criteria are explicitly checked129- the artifact is saved and validated130- any blockers or skipped validations are documented131- the next consumer is identified or the work is handed off132---133@include .agents/skills/platform/contract-base.xml