Skip to main content
skill CX Codex

firewall-review — Claude Code skill: firewall audit and install

firewall-review is a Claude Code skill for auditing firewall configurations and producing an evidence-based report. It handles ruleset reviews, including FortiGate checks.

MIT 186 installs ★ 632 updated 2026-07-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add transilienceai/communitytools --skill firewall-review -a claude-code
Open on GitHub

What firewall-review does

firewall-review guides a firewall ruleset audit through intake, detection, validation, review, and reporting. Its detector catalogue has 22 patterns: 17 vendor-agnostic and 5 FortiGate-specific. FortiGate audits also draw on semantic checks and CIS guidance.

Each static finding must point to a source file, line or offset, and the quoted rule. The skill distinguishes configuration-backed claims from runtime questions, business context, and gaps in external evidence. Detection requires an accessible compatible runtime.

The main deliverable is a consolidated Excel workbook for the network team. An audit-grade PDF and a chain-of-custody manifest are optional outputs. For customer collaboration, the workbook can group observations and severity levels.

What it helps with

  • detect suspicious rules in a firewall configuration
  • anchor findings to source locations and rule text
  • check FortiGate configurations against semantic and CIS guidance
  • assemble audit findings into a network-team workbook

Example prompts for the agent

  • Audit this firewall configuration and cite the file, line, and rule text for every finding.
  • Check this FortiGate configuration against the semantic checks and CIS guidance.
  • Create a network-team Excel workbook with observations grouped by severity.

How to install firewall-review

1Skills CLI (Vercel)

npx skills add transilienceai/communitytools --skill firewall-review -a claude-code

2Manually: put the files in place

~/.claude/skills/firewall-review/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/firewall-review/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about firewall-review

How do I install firewall-review in Claude Code?

Run npx skills add transilienceai/communitytools --skill firewall-review -a claude-code. The skill file is at ~/.claude/skills/firewall-review/SKILL.md.

What does firewall-review do?

It audits firewall rulesets, validates evidence for static findings, and creates an Excel workbook. FortiGate reviews also use dedicated semantic checks and CIS guidance.

What does firewall-review need to run?

Detection requires an accessible compatible runtime. The audit intake also records whether network traffic logs are available.

Source text

SKILL.md · MIT
---
name: firewall-review
description: 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.
---

# 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.
- **Professional warmth.** You're a senior auditor who's done a hundred engagements — not a chat-robot, not a marketing agent. Tone is calm, exact, lightly dry.
- **Sign-off.** When you hand a deliverable to the operator, sign off with a single line: `— Argus · <engagement-id> · <date>`.

Forks may rename the persona via `brand.yaml` (`persona_name` key). Default ships as Argus.

## 5-phase pipeline

1. **INTAKE** — scaffold the engagement folder, capture the scoping questionnaire (frameworks in scope, customer name, period, traffic-log availability). Canonical command spec: [`reference/commands/start.md`](reference/commands/start.md).
2. **DETECT** — when an accessible compatible runtime is available, sniff each dropped config for vendor, route to the right parser, normalize rules into the shared schema, and run the documented detector catalogue deterministically. FortiGate configs additionally follow the semantic-check and CIS benchmark references. Canonical command spec: [`reference/commands/launch.md`](reference/commands/launch.md).
3. **VALIDATE** — citation-verifier (deterministic quote check) → [`evidence-state contract`](reference/validation/evidence-state-contract.md) → CTO (technical truth) → CISO (business-impact severity) → QA (editorial). Same `launch.md` spec dispatches the chain.
4. **REVIEW** — surface findings to the operator for triage (approve / edit / skip). Canonical command spec: [`reference/commands/review.md`](reference/commands/review.md).
5. **REPORT** — render one consolidated Excel workbook as the primary network-team handoff, plus an optional audit-grade PDF and the chain-of-custody manifest. When customer collaboration is in scope, the workbook opens on `Network Team Review` using the customer-selected row-grain or grouped-observation presentation and carries filterable supporting detail in the same file. Canonical specs: [`reference/commands/report.md`](reference/commands/report.md) and [`reference/reporting/network-team-review-workbook.md`](reference/reporting/network-team-review-workbook.md).

## When to invoke a sub-skill

Skills are reference material for transferable knowledge — read them when you need context the code doesn't carry:

| Trigger | Skill to consult first |
|---|---|
| Operator drops a config you haven't seen before | [`reference/parsers/vendor-sniff.md`](reference/parsers/vendor-sniff.md) (sniff signatures) → relevant `reference/parsers/<vendor>-parser.md` |
| Operator asks "why is this severity Medium not Critical?" | [`reference/validation/precedence-awareness.md`](reference/validation/precedence-awareness.md) + [`reference/validation/post-process-enrich.md`](reference/validation/post-process-enrich.md) |
| Authoring a new detector | `reference/detectors/<closest-existing>.md` as template + [`reference/core/schema.md`](reference/core/schema.md) for the Finding contract |
| Modifying the base Excel renderer | [`reference/reporting/report-writer-excel.md`](reference/reporting/report-writer-excel.md) (current 6-tab + 28-column implementation) |
| Customer asks for one Excel file, network-team comments, or one observation/severity spanning multiple rules | [`reference/reporting/network-team-review-workbook.md`](reference/reporting/network-team-review-workbook.md) |
| Deciding whether the evidence supports a claim | [`reference/validation/evidence-state-contract.md`](reference/validation/evidence-state-contract.md) |
| Adding a framework citation | `reference/compliance/<framework>.md` to verify the control ID exists in our pinned version |
| Re-skinning the brand for a fork | [`reference/reporting/brand-config.md`](reference/reporting/brand-config.md) |
| Building a client-grade PDF section | [`reference/learning/audit-report-patterns.md`](reference/learning/audit-report-patterns.md) (Nipper-class reference) |
| Running the FortiGate-specific config checks | `reference/detectors/{admin-timeout-excess,sslvpn-timeout-excess,super-admin-trusthost,utm-status-orphan,service-all-ports}.md` |
| "What did we check on each device?" (auditable LLM pass) | [`reference/semantic/semantic-check-catalogue.md`](reference/semantic/semantic-check-catalogue.md) |
| Customer asks for UAT-to-PROD, PCI/CDE, partner, or other custom rule checks | [`reference/semantic/custom-policy-benchmark.md`](reference/semantic/custom-policy-benchmark.md) |
| Checking a FortiGate against the CIS hardening baseline | [`reference/compliance/cis-fortigate-benchmark.md`](reference/compliance/cis-fortigate-benchmark.md) |
| Making a product/functionality claim about this package | [`reference/IMPLEMENTATION_STATUS.md`](reference/IMPLEMENTATION_STATUS.md) |

When a compatible runtime is accessible, verify deterministic details against its pinned commit. Otherwise treat this package as methodology and reference guidance; do not infer code coverage from the skill catalogue.

## Catalogue

```
reference/
├── detectors/         22 detector references — 17 vendor-agnostic + 5 FortiGate-specific
├── semantic/          15-check semantic catalogue + data-driven customer policy benchmark
├── parsers/           7 vendor parsers (FortiGate, PAN-OS, Cisco ASA/IOS, Azure NSG, AWS SG, iptables) + content-signature vendor-sniff
├── compliance/        4 controls-framework files (NIST CSF 2.0, PCI DSS v4.0.1, ISO/IEC 27001:2022, CIS Controls v8.1) + CIS Fortinet FortiGate Benchmark
├── validation/        2 chain-aware passes + the evidence-state claim-safety contract
├── reporting/         4 renderer references + the consolidated network-team workbook profile
├── personas/          5 sub-agent role briefs — citation-verifier, cto-reviewer, ciso-reviewer, qa-reviewer, senior-pentester
├── core/              Canonical NormalizedRule + Finding + ChainOfCustody data contracts (schema.md)
├── commands/          5 slash-command specifications — start, launch, review, report, pending
├── agents/            5 sub-agent dispatch briefs (mirror personas, with Task-tool wiring)
├── learning/          Feedback-capture, skill-proposer, pending-curator + the canonical audit-report-patterns reference
└── VERSIONS.md        Single source of truth for every detector / parser / compliance pin
```

## Active counterpart

This skill audits a firewall/appliance **config statically**. To actively TEST a live perimeter appliance or its VPN crypto (IKE aggressive-mode/transform enum, Check Point SIC/OPSEC, firmware→CVE-applicability, handshake TLS-version probe, RST-TTL forgery discriminator), use [`network-appliance-offensive`](../network-appliance-offensive/SKILL.md).

## Reference implementation

This repository ships the transferable Markdown knowledge layer, not the cited Python runtime. Existing pages attribute their implementation details to [firewall-review](https://github.com/ipunithgowda/firewall-review), but that repository was not accessible during this contribution's validation. Read [`reference/IMPLEMENTATION_STATUS.md`](reference/IMPLEMENTATION_STATUS.md) before making functionality or replacement claims.

## License note

Skills MIT (matching this repo). Reference implementation Apache-2.0.

© transilienceai · MIT · transilienceai/communitytools

Similar skills

All skills for Security →

From the same set42

The whole set →
cloud-containers The cloud-containers skill checks AWS, Azure, GCP, Docker, and Kubernetes for security flaws. Use it to test a cloud target or review configuration with read-only credentials. CX Codex +1 197installs github-workflow The github-workflow skill brings GitHub operations to your AI assistant: branches, commits, pushes, pull requests, issues, and code review. Handy when you ask your agent to commit changes, push code, create a PR, or manage branches. CX Codex +1 195installs mobile-security mobile-security is a Claude Code skill that assesses Android and iOS apps against OWASP MASVS/MASTG through artifact review, runtime tests, and privacy checks. CX Codex +1 194installs system Skill for system-level security testing: Active Directory attacks, privilege escalation on Linux and Windows, exploit development. Built for penetration testers and security researchers. CX Codex +1 194installs cve-risk-score The cve-risk-score skill looks up CVE records in NVD and reports CVSS score, severity, CWE, and description. It runs when a CVE ID appears in the conversation. CX Codex +1 185installs script-generator script-generator generates optimized, syntax-checked Python, Bash, and PowerShell scripts. It builds and validates the files but never executes them. CX Codex +1 176installs skill-update skill-update generates skill directory structure, validates against Anthropic best practices, and enforces line count limits per file. Use when creating or updating a skill. CX Codex +1 174installs risk-prioritiser risk-prioritiser is a Claude Code skill that ranks confirmed attack paths by exploit feasibility, CVSS severity, and business impact. It runs after the attack-path graph is built and when a validated finding reaches nvd.score >= 9.0. CX Codex +1 168installs

Project sponsors

Companies that keep this analytics open