Cisco FMC Optimization Checklist
Use this checklist to improve policy quality and migration readiness before large-scale FMC modernization or ASA-to-FMC transitions.
Checklist
- Inventory ACP rule volume and identify oversized sections.
- Find duplicate or stale network/service objects.
- Flag shadowed and redundant policy logic.
- Validate NAT policy consistency with security policy intent.
- Confirm naming standards for objects and rules.
- Prioritize high-risk rules for manual review.
- Run pre-deployment validation on remediated output.
- Roll out optimization changes in controlled waves.
How to use this checklist on a real FMC
Cisco FMC rule optimization starts from a snapshot, not from a live session in the hosted product. The read-only collector uses GET requests and packages one fmc_audit ZIP. A capture marked partial or error is a gap. Do not analyze it as if the domain were complete. The hosted service writes nothing back to FMC.
Work the access control policy in the order the checklist names: volume, duplicate objects, shadowed and redundant rules, then NAT that no longer matches the security policy. Shadowed rules are a review item, not an automatic delete. Unused objects are candidates, not proof they are safe to remove if a policy outside the snapshot still references them.
Cisco FTD on its own, including FTD show running-config text, is a roadmap item. If the FTD devices are managed by FMC, collect them through the FMC snapshot. Optimization findings are structural. They are not hit counts, and they are not a statement that validation is complete.
When the same FMC is also a migration source, use the snapshot for FMC to Palo Alto or FMC to FortiGate. Cleaning shadowed rules before that translation gives the engineer a smaller policy to review. It does not remove the need to read NEEDS REVIEW and BLOCKED findings. Deterministic checks set that status. AI can explain a finding and never sets it.