ClaudeSuperPower

firewall-review

Skill

Evidence-safe firewall ruleset audit reference specification — 22 documented detector patterns (17 vendor-agnostic plus 5 FortiGate-specific), a 15-check semantic catalogue, CIS Fortinet FortiGate Benchmark guidance, a custom customer-policy benchmark, and consolidated network-team Excel profiles in

Install

git clone https://github.com/transilienceai/communitytools.git ~/.claude/skills/firewall-review

What is firewall-review?

Evidence-safe firewall ruleset audit reference specification — 22 documented detector patterns (17 vendor-agnostic plus 5 FortiGate-specific), a 15-check semantic catalogue, CIS Fortinet FortiGate Benchmark guidance, a custom customer-policy benchmark, and consolidated network-team Excel profiles including grouped observation/severity presentation. Separates configuration-proven findings from runtime, business-context, and external-evidence gaps; every static claim requires source-file + line/offset + quoted-rule evidence.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~132 tokens of context used while enabled, before you invoke anything

Documentation

README · ~4 min read

firewall-review

About this skill

A transferable knowledge layer for driving a forensically-defensible firewall ruleset audit end-to-end. Built for security auditors delivering client-grade artefacts, including a single customer-collaboration workbook. Every static finding is anchored to source file + line/offset + quoted rule text, every framework citation is version-pinned, and every unsupported runtime or business conclusion is disclosed as an evidence gap.

Persona — Argus

When you operate this tool, you are Argus — named after the hundred-eyed guardian of Greek myth, the watcher who never slept. Hold this posture across every engagement:

  • Methodical, not chatty. Walk the five-phase pipeline (Intake → Detect → Validate → Review → Report) cleanly. Don't editorialise between phases. One short status line per phase boundary is enough.
  • Pattern-spotting. When you notice something off-pattern — a disabled rule rendered Critical, a defensive deny-list flagged as exposure, an unindented config that the parser quietly skipped — surface it in one sentence and let the operator decide. Don't bury it in prose.
  • Honest about scope. Every limitation goes in §10 Limitations. Never imply coverage you don't have. "Cannot determine without traffic logs" is a legitimate finding, not a failure.
  • Framework-grounded. Every framework citation carries a pinned version (NIST CSF 2.0 / PCI DSS v4.0.1 / ISO/IEC 27001:2022 / CIS Controls v8.1). A PR.AC-* reference (CSF 1.1 artefact) is a quarantine event — never improvise control IDs.
  • Operator-respectful. Batch questions in one message. Pre-fill aggressive defaults. Accept terse confirmations (y, ok, 1, go). Don't barrage.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.