Skip to content
Security
Skill

/network-segmentation-review

Review network segmentation and firewall/ACL design for security: zone separation, ruleset hygiene, lateral-movement containment, and zero-trust / microsegmentation. Use to assess or design network architecture defensively (not active testing).

From plugin
awesome-claude-security
6111 skills17 agents13 commands1 MCP
Install
$ npx -y skills add jassics/awesome-claude-security --skill network-segmentation-review --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/network-segmentation-review

Context preview

The summary Claude sees to decide when to auto-load this skill.

Review network segmentation and firewall/ACL design for security: zone separation, ruleset hygiene, lateral-movement containment, and zero-trust / microsegmentation. Use to assess or design network architecture defensively (not active testing).

SKILL.md

network-segmentation-review.SKILL.md
name: network-segmentation-review
description: >-
  Review network segmentation and firewall/ACL design for security: zone
  separation, ruleset hygiene, lateral-movement containment, and zero-trust /
  microsegmentation. Use to assess or design network architecture defensively (not
  active testing).

Goal

An assessment of how well the network limits blast radius: are zones separated, are firewall rules least-privilege, and is lateral movement contained — with prioritized fixes.

What to review

1. **Zoning & trust** — segmentation between internet/DMZ/internal/management/OT, per-environment (prod/dev) and per-tenant separation; where trust changes. 2. **Firewall / ACL hygiene** — overly broad rules (`any/any`), unused/shadowed rules, stale entries, missing egress filtering, default-allow. 3. **Lateral-movement containment** — is the internal network flat? Can one compromised host reach the whole estate? East-west controls, microsegmentation. 4. **Management & sensitive planes** — isolated management network, jump hosts, restricted access to admin interfaces, OT/ICS separation. 5. **Zero-trust posture** — identity-aware access vs. pure network location; explicit allow-listing.

Steps

1. Gather topology, firewall rulesets/ACLs, and zone definitions. 2. Assess against the areas above; flag broad/stale rules and flat segments. 3. Model the lateral-movement blast radius from a typical foothold. 4. Recommend segmentation, rule tightening (least privilege, default-deny egress), and management isolation, prioritized by blast-radius reduction.

Output

A review: zone/rule · issue · severity · fix, plus a target segmentation design and egress policy. Visualize zones with `security-diagramming:architecture-diagram`; report with `security-reporting`.

Notes

Flat networks are the force-multiplier behind most breaches — containing east-west movement limits blast radius more than almost any other network control. Hunt broad (`any/any`) and stale firewall rules; default-deny egress is commonly missing and high-value. Pairs with `network-pentest` (which demonstrates the lateral paths).

Read more
Ships withawesome-claude-security

A Claude Code plugin marketplace for the full cybersecurity & GenAI-security lifecycle — from recon and threat modeling to detection engineering, GRC, and CISO-level strategy. A pentester knows which OWASP test bends a broken-access-control endpoint.

Get the whole plugin

Other skills on awesome-claude-security.