You found out that $FWDIR/Iog/fw.log is constantly growing in size at a Security Gateway, what is the reason?

Question

Options

• ATCP state logging is enabled
• BIts not a problem the gateways is logging connections and also sessions
• Cfw.log can grow when GW does not have space in logging directory
• DThe GW is logging locally

• A
  2% (1)
• B
  90% (45)
• C
  6% (3)
• D
  2% (1)

Explanation

Option B is correct because a Check Point Security Gateway's fw.log is designed to grow continuously - it records every connection and session passing through the gateway as part of its core logging function. A constantly growing fw.log is normal, healthy behavior indicating the gateway is working as intended.

Why the distractors are wrong:

• A is incorrect because "TCP state logging" is not a distinct feature that drives fw.log growth; all traffic types are logged by default, not just TCP state changes.
• C has the logic backwards - insufficient disk space would prevent the log from growing, not cause it to grow.
• D is partially true (local logging does write to fw.log) but frames a normal process as if it were an anomaly, and it's less complete than B's explanation.

Memory tip: Think of fw.log like a receipt printer that never stops printing as long as traffic flows - constantly growing means the gateway is alive and working, not broken. If it stopped growing, that would be the real problem.

No community discussion yet for this question.