<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Firewall state table optimization in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Firewall-state-table-optimization/m-p/13127#M17418</link>
    <description>&lt;P&gt;How can we achieve below requirement in Checkpoint firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE width="720"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="36"&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="684" style="border-left: none;"&gt;State Table&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD style="border-top: none;"&gt;1.1&lt;/TD&gt;
&lt;TD width="684" style="border-top: none; border-left: none;"&gt;The solution should be a stateful firewall and must allow granular control of the state table&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD style="border-top: none;"&gt;1.2&lt;/TD&gt;
&lt;TD width="684" style="border-top: none; border-left: none;"&gt;On a per-rule basis:&lt;BR /&gt;a. Limit simultaneous client connections&lt;BR /&gt;b. Limit states per host&lt;BR /&gt;c. Limit new connections per second&lt;BR /&gt;d. Define state timeout&lt;BR /&gt;e. Define state type&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD style="border-top: none;"&gt;1.3&lt;/TD&gt;
&lt;TD width="684" style="border-top: none; border-left: none;"&gt;State types - the solution shall offer multiple options for state handling:&lt;BR /&gt;&amp;nbsp;a. Keep state - Works with all protocols. Default for all rules.&lt;BR /&gt;b. Sloppy state – shall work with all protocols. Less strict state tracking to support asymmetric routing.&lt;BR /&gt;c. Synproxy state - Proxies incoming TCP connections to protect servers from spoofed TCP SYN floods. Must include the option to keep state and modulate state combined.&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD style="border-top: none;"&gt;1.4&lt;/TD&gt;
&lt;TD width="684" style="border-top: none; border-left: none;"&gt;State table optimization options – at minimum table optimization shall have the options to:&lt;BR /&gt;a. Normal - the default algorithm&lt;BR /&gt;b. High latency - Useful for high latency links, such as satellite connections. Expires idle connections later than normal.&lt;BR /&gt;c. Aggressive - Expires idle connections more quickly. More efficient use of hardware resources, but can drop legitimate connections.&lt;BR /&gt;d. Conservative - Tries to avoid dropping legitimate connections at the expense of increased memory usage and CPU utilization&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
    <pubDate>Tue, 22 Jun 2021 20:58:56 GMT</pubDate>
    <dc:creator>Nikhil_Patil</dc:creator>
    <dc:date>2021-06-22T20:58:56Z</dc:date>
    <item>
      <title>Firewall state table optimization</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Firewall-state-table-optimization/m-p/13127#M17418</link>
      <description>&lt;P&gt;How can we achieve below requirement in Checkpoint firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE width="720"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="36"&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="684" style="border-left: none;"&gt;State Table&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD style="border-top: none;"&gt;1.1&lt;/TD&gt;
&lt;TD width="684" style="border-top: none; border-left: none;"&gt;The solution should be a stateful firewall and must allow granular control of the state table&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD style="border-top: none;"&gt;1.2&lt;/TD&gt;
&lt;TD width="684" style="border-top: none; border-left: none;"&gt;On a per-rule basis:&lt;BR /&gt;a. Limit simultaneous client connections&lt;BR /&gt;b. Limit states per host&lt;BR /&gt;c. Limit new connections per second&lt;BR /&gt;d. Define state timeout&lt;BR /&gt;e. Define state type&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD style="border-top: none;"&gt;1.3&lt;/TD&gt;
&lt;TD width="684" style="border-top: none; border-left: none;"&gt;State types - the solution shall offer multiple options for state handling:&lt;BR /&gt;&amp;nbsp;a. Keep state - Works with all protocols. Default for all rules.&lt;BR /&gt;b. Sloppy state – shall work with all protocols. Less strict state tracking to support asymmetric routing.&lt;BR /&gt;c. Synproxy state - Proxies incoming TCP connections to protect servers from spoofed TCP SYN floods. Must include the option to keep state and modulate state combined.&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD style="border-top: none;"&gt;1.4&lt;/TD&gt;
&lt;TD width="684" style="border-top: none; border-left: none;"&gt;State table optimization options – at minimum table optimization shall have the options to:&lt;BR /&gt;a. Normal - the default algorithm&lt;BR /&gt;b. High latency - Useful for high latency links, such as satellite connections. Expires idle connections later than normal.&lt;BR /&gt;c. Aggressive - Expires idle connections more quickly. More efficient use of hardware resources, but can drop legitimate connections.&lt;BR /&gt;d. Conservative - Tries to avoid dropping legitimate connections at the expense of increased memory usage and CPU utilization&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
      <pubDate>Tue, 22 Jun 2021 20:58:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Firewall-state-table-optimization/m-p/13127#M17418</guid>
      <dc:creator>Nikhil_Patil</dc:creator>
      <dc:date>2021-06-22T20:58:56Z</dc:date>
    </item>
  </channel>
</rss>

