Check Point has multi-part logs that update with more information as time goes by. These can result in multiple log messages at the SIEM for the same event.
There is a pretty good recent thread discussing it here: https://community.checkpoint.com/t5/Management/Aggregate-log-updates-before-export-Log-Exporter-opti...
You want to set your read-mode to semi-unified in your cp_log_export config or turn on "Aggregate log updates before export" if you are using a Log Exporter/SIEM object in the GUI.
I like this description from r81.10 log exporter docs: https://sc1.checkpoint.com/documents/R81.10/WebAdminGuides/EN/CP_R81.10_LoggingAndMonitoring_AdminGu...
field:loguid
Log Unification ID.
Some Check Point logs are updated over time.
Updated logs have the same Log UID value.
Check Point SmartLog client correlates those updates into a single unified log.
When the update logs are sent to 3rd party servers, they arrive as distinct logs.
Administrators can use the "loguid" field to correlate updated logs and get the full eventClosed chain.
Note - Log Exporter's new semi-unified mode correlates all previous logs into one, so the latest log always shows the complete data.
Examples of updated logs:
-The total amount of bytes sent and received over time.
-The severity field which is updated over time as more information becomes available.