parsing-firepower-configs

Parse Cisco Firepower FMC and FDM JSON exports into a vendor-neutral firewall schema.

9|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/fastrevmd-lab/fwskillsshare --skill parsing-firepower-configs-fastrevmd-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parsing-firepower-configs
Source: https://github.com/fastrevmd-lab/fwskillsshare/tree/main/skills/parsing-firepower-configs
Command: npx skills add https://github.com/fastrevmd-lab/fwskillsshare --skill parsing-firepower-configs-fastrevmd-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Cisco Firepower configurations exported from FMC or FDM arrive as dozens of separate REST API JSON responses with UUID-based references, making manual review, auditing, and cross-vendor migration slow and error-prone. This Skill normalizes those exports into one shared intermediate schema so access rules, objects, NAT, VPN, and HA settings can be analyzed consistently. ## Core Features & Use Cases - Full FMC/FDM JSON parsing: Extracts access control rules, prefilter rules, security zones, network/service objects and groups, NAT rules, intrusion and file policies, static routes, HA, VPN, and admin users into the shared firewall schema. - Rule ordering and action fidelity: Flattens prefilter, mandatory, default, and implicit default-action rules into true evaluation order with _rule_index, and flags non-terminal MONITOR rules and FASTPATH bypasses with mandatory warnings. - Audit-ready quality gates: Detects truncated paging, unresolved references, shadowed rules, overly permissive any/any rules, unused objects, and missing logging, and masks secrets while distinguishing absent versus redacted keys. - Use Case: Given a keyed envelope of FMC API responses, produce a single schema document per access control policy with object counts, warnings, and unresolved references, ready to feed conversion, diff, or audit skills. ## Quick Start Ask the agent to parse the attached FMC JSON export into the intermediate schema and report any truncated collections, unresolved references, and shadowed rules.

Frequently Asked Questions about parsing-firepower-configs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I parse a Cisco FMC configuration export into JSON?

Collect REST API responses from the FMC endpoints (objects, policies, rules, devices) and provide them as a keyed envelope, bundle, or single response. The parser extracts zones, objects, rules, NAT, VPN, and HA into the shared intermediate schema with warnings for incomplete data.

What is the difference between parsing FMC JSON and ASA running-config?

FMC and FDM exports are structured JSON from the REST API and are handled by this parser. ASA-style LINA running-config text with access-list, nameif, and object network commands belongs to the parsing-cisco-configs skill instead.

Can this parser handle FDM exports as well as FMC?

Yes, it supports both. FDM uses ruleAction and eventLogAction fields instead of FMC's action and logBegin/logEnd, and has no policy sections or inheritance; the parser maps both variants into the same schema.

Why does the parser warn about truncated collections?

When paging.count exceeds the number of items actually returned, the export is incomplete. The parser records a warning and qualifies all audit findings, because missing objects cause false unresolved references and unreliable shadowing analysis.

What file formats are not supported for Firepower parsing?

The parser refuses .sfo policy bundles, PDF policy reports, and HTTPS configuration backups because they lack a documented structured format. Only FMC or FDM REST API JSON exports are accepted.

How are MONITOR rules handled in the parsed output?

MONITOR rules are non-terminal: they log and continue evaluation. The schema has no non-terminal action, so they map to allow with a mandatory warning stating that shadowing and terminal-deny conclusions are unreliable across them.