parsing-cisco-configs

Parse Cisco ASA and FTD running configurations 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-cisco-configs-fastrevmd-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parsing-cisco-configs
Source: https://github.com/fastrevmd-lab/fwskillsshare/tree/main/skills/parsing-cisco-configs
Command: npx skills add https://github.com/fastrevmd-lab/fwskillsshare --skill parsing-cisco-configs-fastrevmd-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Cisco ASA and FTD running configurations are dense, line-oriented text that is hard to audit, compare, or migrate by hand. This Skill parses show running-config output into a structured vendor-neutral JSON schema so ACLs, NAT rules, objects, and routes can be analyzed, audited, or converted reliably. ## Core Features & Use Cases - Full config extraction: Parses interfaces, nameif-derived zones, network/service objects and groups, ACLs with access-group bindings, object and twice NAT, static routes, OSPF/BGP, VPN/IPsec, failover, DHCP, and admin users. - Built-in audit checks: Detects unused objects, shadowed ACL entries, overly permissive rules, missing logging, unbound ACLs, empty groups, and weak VPN algorithms like DES/3DES or MD5. - Conversion-ready output: Emits the shared intermediate schema consumed by downstream conversion and diff skills, with port-to-application mapping, implicit deny rules, residual capture, and secret masking. - Use Case: Paste an ASA running config and receive normalized JSON of all security policies and NAT rules plus a findings report flagging a permit ip any any rule and an unused object group before a migration to Palo Alto. ## Quick Start Ask the agent to parse the attached Cisco ASA running configuration into the shared firewall schema and report any audit findings.

Frequently Asked Questions about parsing-cisco-configs

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

FAQPage Schema
How do I parse a Cisco ASA running config into JSON?

Provide the `show running-config` output and the parser extracts interfaces, objects, ACLs, NAT, routes, and VPN settings into the shared intermediate schema. It also runs quality gates reporting object counts, unresolved references, and warnings.

What security audit checks does Cisco ASA config parsing include?

The parser flags unused objects, shadowed ACL entries, overly permissive rules like permit ip any any, missing logging on permits, inactive entries, duplicate objects, empty groups, unbound ACLs, and weak VPN algorithms such as DES, 3DES, MD5, and DH group 5 or lower.

Does this skill parse Firepower FMC or FDM configurations?

No. FMC and FDM JSON exports have no syntactic overlap with LINA CLI and are routed to the parsing-firepower-configs skill instead. This skill only handles ASA and ASA-style FTD line-oriented running configurations.

How are ASA ACLs converted to zone-based firewall policies?

ACLs are combined with access-group bindings to derive zones: for an inbound binding, the ingress interface nameif becomes the source zone, and the destination zone is inferred or set to any with a warning. Implicit per-binding deny rules are appended after explicit entries.

Are passwords and pre-shared keys exposed in the parsed output?

No. Tunnel-group pre-shared keys, user password hashes, BGP neighbor passwords, and SNMP communities are masked as "****" or reduced to presence flags, with a metadata warning noting the redaction.

What happens to config lines the parser does not recognize?

Unrecognized top-level commands are captured verbatim in residual_raw, categorized under labels like VPN/IPsec, AAA, QoS, or PKI/Certificates, so nothing is silently dropped and unsupported constructs remain available for manual review.