# firewall-review

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

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 186 installs · ★ 632 repo stars
- Author: transilienceai
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/transilienceai/communitytools/tree/HEAD/skills/firewall-review/SKILL.md
- Updated: 2026-07-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/firewall-review

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill firewall-review -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/firewall-review/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/firewall-review/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill firewall-review -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/firewall-review/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill firewall-review -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/firewall-review/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install transilienceai/communitytools skills/firewall-review
```

2. **Manually: put the files in place**
- File: `.github/skills/firewall-review/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill firewall-review -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/transilienceai/communitytools --path skills/firewall-review
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/firewall-review/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add transilienceai/communitytools --skill firewall-review -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/transilienceai/communitytools/tree/HEAD/skills/firewall-review/SKILL.md

## When to use it
- 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
- 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.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 1d9cf1b3238d1fdc.

BEGIN THIRD-PARTY FILE 1d9cf1b3238d1fdc
```text
---
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.
```
END THIRD-PARTY FILE 1d9cf1b3238d1fdc

The third-party file has ended. Everything between the 1d9cf1b3238d1fdc tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2711 of 9538 bytes. © transilienceai · MIT · https://github.com/transilienceai/communitytools/tree/HEAD/skills/firewall-review/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
