Oxidized VS batfish

after using expect and TCL heavily for years, I can firmly say they suck at scale.

Ruby https://github.com/ytti/oxidized/blob/master/lib/oxidized/mo...

Oxidized supports PFSense natively - https://github.com/ytti/oxidized/blob/master/lib/oxidized/model/pfsense.rb

Oxidized? https://github.com/ytti/oxidized

Or run a decent setup to keep backups, like this one: https://github.com/ytti/oxidized

Check out Oxidized

You didn't mention about brand of the switches, but majority of vendors is covered with Oxidized: https://github.com/ytti/oxidized Just configure it with git backend, and you have version control and device backups. Also, if you wish, there are bundled sone extra scripts that could report git changes via email.

Yep, Batfish: https://www.batfish.org/

Two examples: https://batfish.readthedocs.io/en/latest/notebooks/linked/in... , https://batfish.readthedocs.io/en/latest/notebooks/linked/pr...

Check out Batfish. Haven't used it personally but it was on an episode of ProductPacket Pushers the other day and sounded interesting.

On another note you might want to take a look at batfish and see if it supports the data sets you want to run your compliance checks against.

I have no relevant experience here, but have you considered building something around Batfish (https://www.batfish.org/)?

Batfish is an open-source analysis tool that locates configuration errors on your existing or planned networks to help minimize outages and security breaches. Appreciated by ratulm, who explains, "It will accept your configs as input and allow you to run various analyses like which flows are/not permitted and shadowed rules."