parsing-srx-configs

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Juniper SRX configurations are dense, hierarchical, and error-prone to interpret by hand, and generic AI agents often produce plausible but wrong readings of zones, policies, and NAT. This Skill converts display-set or curly-brace Junos configs into a structured, vendor-neutral JSON schema so audits, conversions, and diffs rest on verified extraction rather than guesswork. ## Core Features & Use Cases - Full config extraction: Parses zones, address books, address-sets, applications, security policies, NAT rules, interfaces, routing (static, BGP, OSPF/OSPFv3), VPN IKE/IPsec chains, chassis cluster HA, DHCP, syslog, and logical-systems/tenants. - Built-in audit checks: Detects unused objects, shadowed policies, overly permissive rules, missing logging, disabled policies, duplicate objects, empty groups, and weak VPN algorithms (DES/3DES, MD5, DH group ≤ 5). - Quality gates and safety: Preserves rule ordering, disabled state, and residuals; masks pre-shared keys and credentials; flags unresolved references and assumptions in metadata warnings. - Use Case: Paste an SRX show configuration | display set export and receive normalized JSON conforming to the shared intermediate schema, ready to feed firewall-config-conversion, firewall-config-diff, or a compliance audit. ## Quick Start Ask the agent to parse the attached Juniper SRX configuration into the shared firewall schema and report any unused objects or shadowed policies.

Frequently Asked Questions about parsing-srx-configs

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

FAQPage Schema
How do I parse a Juniper SRX configuration file?

Provide the SRX config in either display-set format (set security zones ...) or hierarchical curly-brace format. The parser detects the format automatically, normalizes it, and extracts zones, policies, NAT, VPN, and routing into structured JSON.

What is the difference between display-set and hierarchical Junos config formats?

Display-set format lists flat 'set <path> <value>' lines from 'show configuration | display set', while hierarchical format uses nested braces from a plain 'show configuration'. The parser converts hierarchical input to set commands internally before extraction.

Does the parser support SRX logical systems and multi-tenant configs?

Yes. It detects logical-systems and tenants stanzas and parses each context independently, tagging extracted items with the logical-system or tenant name so policies and objects are not merged across contexts.

Can parsed SRX configs be converted to other firewall vendors?

Yes. The output follows a shared vendor-neutral schema consumed by the firewall-config-conversion and firewall-config-diff skills, with junos-* applications resolved to canonical names for cross-vendor mapping.

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

No. IKE pre-shared keys are masked as "****" and routing-protocol authentication keys are reduced to presence flags, with redaction noted in metadata warnings.

What security audit checks run on parsed SRX configs?

The parser reports unused address and service objects, shadowed policies, overly permissive any/any rules, permit rules missing session-close logging, deactivated policies, duplicate objects, empty groups, and weak VPN algorithms like DES, 3DES, MD5, or DH group 5 or lower.