cancel
Showing results for 
Search instead for 
Did you mean: 
Post a Question

The flow time of the logs seems different

Hello all, 

I have Checkpoint MGMT R80.20 Smart Console and ClusterGateway R.80.20 . I looking logs with Smart Console.

 

Why the time of the logs is different. The time of the mgmt time and the gateways are the same. ntp server is in use. they all appear the same time?this image logs.

6 Replies
Jerry
Gold

Re: The flow time of the logs seems different. flow of logs when the problem

check

fw monitor -e "host(x.y.z.w) and host(a.b.c.d), accept;"

are the time-stamps in a proper time frames to the MGMT/GW ?

also check the fw log and cpview - ntp must be not entirely in SYNC with NTP servers or you've got some routing issues mate

Jerry
Admin
Admin

Re: The flow time of the logs seems different. flow of logs when the problem

What you might be seeing is consolidated logs and the time shown is the "start" of the the consolidated session.

You might drill into a few of those just to confirm that suspicion. 

Re:  The flow time of the logs seems different. flow of logs when the problem

Actually if you drill down on it it will (literally) sort itself out.

If you log both connections and sessions you will see the connection as soon as the SYN packet is received.

The session will only show in the log when it is finished.

This is something people really need to get used to with R80.

A sound understanding of Connections, Sessions and how the Acess Control is different from the Threat Prevention takes a bit of playing around with in order to full get a grasp on it.

Re: The flow time of the logs seems different. flow of logs when the problem

When I look log out put , I see the session logs time is creation time .so the real time seeming wrong . is this normal? how can ı see last update time in logs.. ?? 

Re:  The flow time of the logs seems different. flow of logs when the problem

Actually. The log is correct.

The session starts at 10:58 so that information is shown in the overview.

The session can only be listed once it's done so that happens at 11:30

So you will see it among other entries around 11:30 when you follow the log in real-time.

This is exactly the point I am trying to make.

It takes getting used to the way how sessions and connections can be logged completely differently.

Each timestamp is for the start of the log event. Not the end time.

I don't see why you want to see the end times in the overview. I would say the start of events is the most relevant information.

0 Kudos

Re: The flow time of the logs seems different. flow of logs when the problem

Session Logging is new in R80+ management, while Log Suppression was around earlier than that and sometimes gets confused with Session Logging.  Here is an excerpt from some content I recently developed explaining the difference with screenshots:

Module 6 – IPS Logging
Session Logging

  • Although not directly related to IPS logging, R80.10+ management by default will attempt to consolidate individual connection logs into a session log. This feature is commonly confused with Log Suppression which is quite relevant to IPS logging and covered next.
  • A connection log typically only contains very basic information such as Layer 3 and Layer 4 information, while a session log is a collection (or superset) of individual connections.
  • A session is a period that starts when a user first accesses an application or site. During a session, the gateway records one log for each application or site that a user accesses. All activity that the user performs within the session is included in the single session log.

  • Note the multiple tabs (such as “Matched Rules”) in this single log entry, don’t miss these as they contain valuable information!
  • For more information about session logging see the CheckMates article “Infinity R80.10 "Cool Feature of the Day" – Session logging” (from which the above screenshot was taken) by Moti Sagey at: https://community.checkpoint.com/message/6279
  • To determine the actual number of individual connections made during a session, see the Suppressed Logs field of the log (not shown above).

  • When a ThreatCloud IPS Protection is matched and Track is set to Log, a log entry is generated. Within a period of two minutes, if the same IPS Protection is matched again with all the same connection attributes (IP addresses, ports, etc) a second log entry is not generated. The Suppressed Logs counter of the original log entry is simply incremented. Note that Log Suppression does not occur for logs generated by Core Activations or Inspection Settings.
  • After two minutes measured from the first detection of this attack, if the same attack is still ongoing a new log entry is created and its Suppressed Logs counter is incremented.
  • Note that when viewing an IPS Log Entry, numerous actions are available including:

◦ Viewing the attack attributes at the Check Point ThreatWiki website
◦ Creating an Exception (covered later in this module)
◦ Viewing Remediation Options

--
Second Edition of my "Max Power" Firewall Book
Now Available at http://www.maxpowerfirewalls.com

"IPS Immersion Training" Self-paced Video Class
Now Available at http://www.maxpowerfirewalls.com