SkillVaultskills Browse all 500 skills

Infrastructure · Version 1.4.0 · Reviewed 2026-08-02

Network Policy Designer

Review and harden default-deny rollout and egress control design with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 5 diagnostic checks 7 quality gates

Designs default-deny network policy, egress control, and DNS handling with a rollout order that does not cause an outage.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Default-deny rollout
  • Egress control design
  • Policy debugging

How Network Policy Designer works

You provide

Namespace topology, required flows, and egress needs

It inspects

DNS reachability first, then workload-to-workload flows

It decides

Default-deny rollout order with audit-mode staging

You verify

Real traffic passes in audit mode before enforcing

What it checks first

Network Policy Designer designs default-deny network policy, egress control, and DNS handling with a rollout order that does not cause an outage. Use it when the work involves Default-deny rollout, Egress control design, Policy debugging.

  1. Whether the obligation is a legal requirement, a contractual commitment, or an internal policy — the escalation path differs.
  2. The specific data categories and lawful basis, rather than a general statement about compliance.
  3. Data flows across jurisdictions and processors, which determine transfer obligations.
  4. Retention and deletion behavior in every downstream copy, including backups and analytics.
  5. Who is accountable for the decision, since a compliance analysis without an owner is not actionable.

Failure modes it recognizes

  • Deletion implemented in the primary store while copies persist in backups, exports, logs, and warehouses.
  • Consent collected for one purpose and reused for another without a valid basis.
  • A subprocessor added without a data-processing agreement or customer notification.
  • Retention policy defined but never enforced by an automated job.
  • A control documented in policy but not implemented in the system it describes.

Answers it will reject

  • Providing a definitive legal conclusion rather than a structured analysis for qualified review.
  • Treating a compliance certification as evidence that a specific control works.
  • Relying on contractual language to mitigate a technical risk that is technically preventable.
  • Presenting risk without severity, likelihood, and the accountable owner.

Decision rules it applies

  • Separate legal requirement, contractual obligation, and internal policy in every finding.
  • Escalate to qualified counsel for anything that constitutes legal advice, and say so plainly.
  • Map every obligation to a specific implemented control and its evidence, or mark it as a gap.
  • Prefer technical enforcement over documented intent, because documented intent is not a control.

Evidence it asks for

  • Build a data inventory: category, source, purpose, basis, location, retention, and downstream copies.
  • Trace one deletion request end to end and enumerate every store it must reach.
  • Record the evidence artifact that would satisfy an auditor for each control.

The method inside

  1. Turn default-deny rollout into explicit functional requirements and quality-attribute constraints.
  2. Model the critical path, state, trust, and failure boundaries that govern egress control design.
  3. Compare viable designs for policy debugging against weighted constraints and operational ownership.
  4. Select a design with consequences, rollout stages, observability, and a reversible adoption path.

Deliverables

  • Default-deny rollout assessment
  • Egress control design decision and action plan
  • Policy debugging verification checklist

Evidence requirements

  • Infrastructure code or configuration
  • Runtime topology and environment constraints
  • Plan, events, policies, and failure symptoms

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We want default-deny networking in our cluster without breaking everything on the first day.

Expected output

The step that breaks clusters is DNS: a default-deny policy blocks resolution to kube-dns and every workload fails in a way that looks unrelated to networking. Allow DNS egress explicitly first, roll out in audit mode per namespace, and verify with real traffic before enforcing...

Boundaries and compatibility

Ideal for

  • Default-deny rollout: produce a decision or artifact grounded in supplied evidence.
  • Egress control design: produce a decision or artifact grounded in supplied evidence.
  • Policy debugging: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Applying infrastructure changes without approval
  • Assuming cloud access or live resource visibility

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.