Optimizing CheckPoint firewall performance

1.) General ways that firewall performance can be improved to overcome problems such as high CPU utilization, low throughput, and slow applications.

2.) Tips and best practices that can help you to optimize your firewall infrastructure.

Check Point

  1. Use networks instead of address ranges in NAT.
  2. Avoid rules with Ident.
  3. Replace nested groups by flat groups.
  4. Be aware of configurations that SecureXL templates (fastpath) cannot handle, for example, security server, or syndefender.
  5. Note that SecureXL templates can be disabled from a certain rule onwards due to certain configurations such as client auth, time objects, etc.
  6. Be aware of configurations that SecureXL cannot handle, for example:
    • FloodGate-1 (automatically disables SecureXL)
    • Rules with user authentication
    • Services with a port number range (disables connection-rate acceleration)
    • Time object associated with the rule (disables connection-rate acceleration)
  7. Be aware of SmartDefense configurations that may impact performance:
    • Network Security–>Fingerprint scrambling–>ISN spoofing
    • Network Security–>Fingerprint scrambling –>TTL

Best practices for optimizing firewall performance

Is your firewall overloaded? Symptoms include high CPU, low throughput and slow applications.  Before upgrading your hardware, it is worth checking whether the firewall configuration can be optimized.

Optimization techniques can be divided into two groups – general best practices, and vendor-specific, model-specific configurations. This column focuses on best practices. Next time, we will look at vendor-specific tips, so if you have any to share, we would like to hear from you.

Optimizing firewalls for better performance and throughput:

  1. Remove bad traffic and clean up the network.  Notify server administrators about servers hitting the firewall directly with outbound denied DNS/NTP/SMTP/HTTP(S) requests as well as dropped/rejected internal devices. The administrators should then reconfigure the servers not to send this type of unauthorized outbound traffic, thereby taking load off the firewall.
  2. Filtering unwanted traffic can be spread among firewalls and routers to balance the performance and effectiveness of the security policy.
    1. Identify the top inbound dropped requests that are candidates to move upstream to the router as ACL filters. This can be time consuming, but it is a good method for moving blocks upstream to the router and saving firewall CPU and memory.
    2. If you have an internal choke router inside your firewall, also consider moving common outbound traffic blocks to your choke routers, freeing more processing on your firewall.
  3. Remove unused rules and objects from the rule bases.
  4. Reduce rule base complexity – rule overlapping should be minimized.
  5. Create a rule to handle broadcast traffic (bootp, NBT, etc.) with no logging.
  6. Place the heavily used rules near the top of the rule base. Note that some firewalls (such as Cisco Pix, ASA version 7.0 and above, FWSM 4.0 and certain Juniper Networks models) don’t depend on rule order for performance since they use optimized algorithms to match packets.
  7. Avoid DNS objects requiring DNS lookup on all traffic.
  8. Your firewall interfaces should match your switch and/or router interfaces.  If your router is half duplex your firewall should be half duplex.  If your switch is 100 Mbit your firewall interface should be hard-set to match your switch; both should most likely be hard-set to 100 Mbit full duplex. Your switch and firewall should both report the same speed and duplex mode. If your switch is gigabit, your switch and firewall should both be set to auto-negotiate both speed and duplex.  If your gigabit interfaces do not match between your firewall and switch, you should try replacing the cables and patch panel ports. Gigabit interfaces that are not linking at 1000 Mbit full duplex are almost always a sign of other issues.
  9. Separate firewalls from VPNs to offload VPN traffic and processing.
  10. Offload UTM features from the firewall: AV, AntiSpam, IPS, URL scanning.
  11. Upgrade to the latest software version. As a rule of thumb, newer versions contain performance enhancements but also add new capabilities, so a performance gain is not guaranteed.

If you use Tufin SecureTrack, you can automate a number of these tasks.

Here are a few ways that SecureTrack can help:

  1. Identify unused rules and objects with the Rule and Object Usage Report, and consider removing them. The longer the reporting period, the more reliable the rule usage status will be. Remember that certain rules, like the ones allowing disaster recovery services, are only used rarely. You can also identify and cleanup unused group members.
  2. Analyze rule shadowing with Policy Analysis. Run Policy Analysis with “Any;Any;Any;Any” to identify completely shadowed rules. These rules are redundant and should be deleted. You can re-validate the redundancy with an unused rules report.
  3. Identify the most-used rules with the Rule and Object Usage Report and move them up in the rule base hierarchy. To find the top-most location for placing a rule without affecting connectivity, run an “Any;Any;Any;Any” policy analysis query, then, for each most-used rule:
    1. If it is not shadowed, move it to any higher location.
    2. If it is shadowed, find the lowest-ranked shadowing rule with a contradictory action and place the most-used rule below that one.
  4. Other things to keep in mind when re-ordering rules:
    1. You’ll probably want to preserve the rule base structure, for example, rule grouping by service or application, source or destination, projects etc.
    2. Be careful with policies containing rules with special actions such as authentication or encryption – shadowing becomes more tricky in this case.
  5. You may also use the Best Practices Rule Order Optimization test to quickly identify candidates for relocation.
  6. Use the Automatic Policy Generator (APG) to identify and remove unwanted traffic from the firewall. Read more about APG here.
  7. Use the “Software Version Compliance Report” to control your firewall software versions.

Last but not least, remember that optimization can have a price, too – beyond the time you’ve invested. If you are not careful, you can wind up with a rule base which is too hard to maintain.  If you have the budget, there are times when upgrading the hardware is the easiest alternative.

This entry was posted in CheckPoint and tagged , , , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s