Sign in Request access

Cisco FMC Rule Optimization

Audit and clean up Cisco Secure Firewall Management Center policy from a read-only snapshot. The FMC collector pulls your FMC configuration over the REST API with GET requests only, packages it as one fmc_audit ZIP, and you upload that ZIP to NetConverter for a reviewable report of shadowed rules, unused objects and other cleanup findings.

Start FMC Analysis Get the FMC collector

1. Collect, read-only

Run the FMC collector on your network. It sends only GET requests to the REST API of your FMC and never modifies your FMC.

2. Upload the snapshot

Upload the single fmc_audit_*.zip. It carries the configuration JSON, a manifest and the capture coverage of every endpoint.

3. Review the findings

Get prioritized rule and object recommendations that your team applies during a planned change window.

What the FMC Collector Pulls

The collector is open source, in the public collectors repository (cisco/fmc) and on the portal's Tools & Downloads page. It needs Python, HTTPS reach to the FMC and an API account with read access. One run captures:

The collector also writes an offline HTML view of the snapshot, so you can review what was captured before you upload anything. Nothing leaves your network until you upload the ZIP.

What the Optimizer Reports

Firepower Management Center policies accumulate debt the same way every long-lived firewall does: a rule added for a project that ended, an object cloned because nobody trusted the existing one, an any-any-allow left in during a cutover and never tightened. NetConverter parses the snapshot into a vendor-neutral model and runs deterministic hygiene checks across the rule base.

On the rule side, it reports shadowing (a higher rule that fully masks a lower one), redundancy, over-permissive allow rules, disabled rules and rules with an expired time range, NAT rules masked by an earlier NAT rule, and rules without logging. On the object side, it flags unused objects, duplicate objects that define the same value under different names, empty groups, redundant group members and overlapping networks. Findings come back as a prioritized, exportable report, not a black-box score.

Findings are structural. An API capture does not prove hit counts, deployment state or HA status, and an endpoint the collector could not capture in full is shown as a gap instead of being analyzed. The analysis is read-only and the hosted service never logs in to or writes to FMC.

Cisco Paths NetConverter Supports

Cisco FTD on its own, as FTD LINA show running-config text or as a target, is a roadmap item. For FTD devices managed by FMC, use the FMC collector. A raw FMC policy export is refused.

Frequently Asked Questions

What does Cisco FMC rule optimization actually check?
On the rule side NetConverter reports shadowed rules (a higher rule fully masks a lower one), redundant rules, overly permissive allow rules, disabled rules and rules whose time range has expired, NAT rules masked by an earlier NAT rule, and rules without logging. On the object side it reports unused objects, duplicate objects that define the same value under different names, empty groups, redundant group members and overlapping networks. Each finding is a structured recommendation an engineer reviews and applies during a change window.
Does NetConverter connect to my live FMC or work from an export?
From a snapshot that you collect. The read-only FMC collector runs on your network and issues only GET requests (plus the authentication token call) against the REST API of your FMC, then packages one fmc_audit_*.zip that you upload. The hosted service has no live FMC connection and does not read from or write to FMC. A raw FMC policy export and FTD show running-config text are refused as the Cisco FMC source.
Will FMC optimization change my policy automatically?
No. Optimization is analysis-only and produces a reviewable report (including Excel export) of prioritized recommendations. Your team decides what to apply. NetConverter never writes to FMC. A migration to FMC produces an FMC JSON file and an import package that you push on site with the fmc_import.py script from Tools & Downloads; the hosted service does not log in to FMC.
How does FMC optimization relate to an ASA to FMC migration?
They are complementary. Running optimization before migrating lets you drop dead rules and duplicate objects so you migrate a clean policy instead of carrying technical debt. Running it after migration, on a new collector snapshot, checks that the imported Access Control Policy is free of shadowing and object duplication introduced during consolidation. See the Cisco ASA → FMC migration guide and the FMC optimization checklist.
What Firepower/FMC versions are supported?
Analysis works from what the collector captured from your FMC, with an API account that has read access to the domains you collect. The snapshot records each endpoint as complete, partial or error; a partial or failed capture is reported as a gap and is not analyzed as if it were complete. An API capture does not prove hit counts, deployment state or HA status, so findings are structural, not traffic-based. Cisco FTD on its own, as FTD LINA show running-config text, is a roadmap item.