firewall-management
Skill1 starsChanged 32 days agoApache-2.0View on GitHub
Create, read, update, and delete firewall security policy objects (rules, address/service objects, NAT rules) on a supported firewall platform — currently Palo Alto Networks PAN-OS/Panorama (REST API), Fortinet FortiOS/FortiGate (CLI), Cisco ASA (CLI, with limited confirmed REST coverage), Juniper SRX/Junos OS (CLI), Fortinet FortiManager (JSON-RPC, central policy packages), WatchGuard Firebox (WatchGuard Cloud REST API), AWS Network Firewall (rule groups and policies via API), Zscaler ZIA cloud firewall filtering rules (REST API), and Cloudflare Network Firewall (custom and managed rules via the Rulesets API). Assumes an authenticated client for the target platform's API/CLI is already available; this skill does not provision or authenticate it. Does not cover Cisco FTD/FMC.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- alert-monitor-managementSkill
- automation-job-executionSkill
- casb-policy-managementSkill
- casb-posture-assessmentSkill
- certificate-managementSkill
- change-managementSkill
- cloud-security-group-auditSkill
- cmdb-asset-managementSkill
- compute-instance-provisioningSkill
- config-backup-managementSkill
- connector-tunnel-managementSkill
- container-workload-deploymentSkill
- crm-contact-managementSkill
- dcim-asset-managementSkill
- dhcp-scope-managementSkill
- dns-record-managementSkill
- dns-zone-managementSkill
- incident-managementSkill
- infrastructure-plan-executionSkill
- interface-link-troubleshootingSkill
- ipam-allocationSkill
- load-balancingSkill
- log-querySkill
- metric-querySkill
- network-access-control-managementSkill
- network-health-verificationSkill
- network-state-collectionSkill
- notificationsSkill
- repository-pull-request-managementSkill
- routing-troubleshootingSkill
- sdwan-policy-managementSkill
- sdwan-site-onboardingSkill
- secret-retrievalSkill
- software-upgrade-lifecycleSkill
- vpn-tunnel-managementSkill
- vulnerability-lookupSkill
- waf-managementSkill
- wireless-network-managementSkill
- zero-trust-access-policy-managementSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Not for application-layer (HTTP) web application firewall (WAF) rules, rate-limit rules, or managed-ruleset bindings — see waf-management …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Firewall Management
Manages firewall security policy objects — rules, address/service objects, NAT rules — on whichever firewall platform the caller is targeting, following that platform's own documented procedure exactly.
When to use this skill
- Creating, reading, updating, or deleting a firewall rule, address/service object, or NAT rule on a supported platform.
- Not for application-layer (HTTP) web application firewall (WAF) rules, rate-limit rules, or
managed-ruleset bindings — see
waf-managementfor that. A platform may offer both network-layer and application-layer protection under one product line; this skill covers only the network-layer rule/object model.
Universal concepts (shared firewall vocabulary, not a wire standard)
There is no wire-level standard behind firewall rule/object management the way DNS has RFC 1035 —
every claim below was checked against the vendors currently listed in references/INDEX.md
(PAN-OS, FortiOS, Cisco ASA, Juniper SRX, FortiManager, WatchGuard Firebox, AWS Network Firewall,
Zscaler ZIA, Cloudflare Network Firewall)
and holds as stated; it is not assumed to extend automatically to a platform not yet added.
- A rule matches traffic by referencing named objects (addresses, and where the platform defines them, services), and some platforms also accept raw values inline. PAN-OS, FortiOS, Cisco ASA, Juniper SRX, FortiManager and WatchGuard model an address as its own named object that a rule references by name — read or confirm an object's current definition separately from the rule. AWS Network Firewall has no address objects, Zscaler ZIA rules take both inline addresses and references to IP groups by id, and Cloudflare Network Firewall rules carry their match values in an expression, optionally naming an account IP list, so check each procedure.
- Deleting an object or rule that something else still depends on is not something to assume the platform blocks for you. Enforcement varies and is partial at best. PAN-OS, FortiOS, Cisco ASA, FortiManager and WatchGuard procedures found no platform-enforced reference check preventing deletion of an in-use object or rule (ASA's docs explicitly note this for network-service objects). Zscaler ZIA and Cloudflare Network Firewall document no reference check on rule deletion, and ZIA's referenced objects are not edited by its procedure. Juniper SRX documents some commit-time enforcement for specific cases only, and AWS Network Firewall rejects deleting something still in use. Treat "check for existing references before deleting" as this skill's own discipline in every vendor procedure, not a safety net the platform itself is confirmed to provide.
- How a write becomes "live" varies by vendor and is not safe to assume uniform. PAN-OS and Juniper SRX have a documented candidate/commit model where nothing takes effect until a separate commit step. FortiManager and WatchGuard stage changes centrally and need a separate push to the devices, and Zscaler ZIA stages each change until the tenant configuration is activated (a tenant-wide step). Cisco ASA's REST API is documented as writing only to the running configuration, requiring a separate persist step to survive a reload. AWS Network Firewall applies writes without a commit step, and Cloudflare Network Firewall documents none, but check each procedure for how changes propagate. Whether FortiOS's and ASA's CLI writes apply immediately was not independently confirmed. Don't assume "the write call returned success" means "this is now enforced" — check each vendor's own procedure for what apply/commit/persist step (if any) it requires.
- NAT is not modeled the same way across vendors — don't assume a shared shape. PAN-OS treats NAT rules as their own separate rule family (parallel to security rules); FortiOS's VIP table covers destination NAT specifically, separate from its firewall-policy table and from source NAT (configured differently, at the policy level); Cisco ASA nests static/auto NAT as a subcommand inside the network object it translates, not as an independent rule list; Juniper SRX keeps NAT in its own rule sets, separate from security policies. NAT modeling for FortiManager, WatchGuard, AWS Network Firewall and Zscaler ZIA was not confirmed, and Cloudflare Network Firewall documents no NAT. Confirm the target vendor's own NAT model before assuming any of these shapes carries over to another platform.
See references/INDEX.md for which platforms have a procedure, and each platform file for how it
implements this shape concretely.
Procedure
- Identify the target platform — from the caller's request or the
platformargument. Checkreferences/INDEX.md; if no matching row exists, stop: this skill doesn't cover it yet. - Open
references/<platform>/procedure.mdand follow it exactly — it contains that platform's full operational procedure, error handling, patterns, known limitations, tools, and verification checklist. - Report the outcome using that platform procedure's own status vocabulary — don't normalize it away.
Known limitations
- Covers PAN-OS/Panorama, FortiOS/FortiGate, Cisco ASA, Juniper SRX, FortiManager, WatchGuard Firebox, AWS Network Firewall, Zscaler ZIA and Cloudflare Network Firewall only — see
references/INDEX.mdfor exactly what's confirmed for each. A platform not listed there (including Cisco FTD/FMC) needs a new reference file before this skill can be used for it. - Each vendor file also carries its own gaps (e.g. PAN-OS's NAT-rule REST path, FortiOS's REST API surface, ASA's FTD/FMC distinction) — check that vendor's own Known limitations before assuming full coverage of every operation named in this skill's description.
Contributing to this skill
SKILL.md only changes for two reasons: a bug in the universal concepts/router logic above, or
adding a pointer to a newly-supported platform. Platform-specific procedure changes — a new error
code, a corrected field, a changed call mechanism detail — belong in that platform's own
references/<platform>/procedure.md, never here.
Tools
Each platform assumes its own authenticated client — see references/INDEX.md for which, and that
platform's procedure.md for the specific operations.
Verification checklist
- Target platform confirmed against
references/INDEX.mdbefore proceeding - That platform's own
procedure.mdwas followed, including its own confirmation gates on destructive changes (rule/object deletion, NAT rule removal) - Outcome reported using the platform procedure's own status vocabulary
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

