Some thoughts knowing that in huge policy packages it could be extremely hard work:
General / Structure
- Move most-used rules (high hit count) to the top
- Place specific rules before general ones
- Broad rules (Any / large networks) towards the bottom
- Use clear sections / inline layers for readability
Analysis & Maintenance
- Zero-hit rules:
- verify (shadowed vs. obsolete)
- remove or disable
- Merge duplicate or overlapping rules
- Maintain comments (rule purpose / business context)
Performance & Logging
- High-hit allow rules: consider Track = None if logging not absolutely necessary
- Log selectively, not everywhere
Tips to get rid of “Any” rules
- Temporarily enable logging on the Any rule
- Analyze in SmartLog / SmartEvent:
- which ports
- which applications
- Split the rule:
- explicit services (e.g. TCP 443, 22)
- or Application Control instead of ports
- Use Policy Optimizer for automatic suggestions (Tufin, AlgoSec or similar)
- Monitor after changes, then remove the Any rule
and now to something completely different - CCVS, CCAS, CCTE, CCCS, CCSM elite