-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Filebeat] Add module for Checkpoint Firewall #16041
Comments
Pinging @elastic/siem (Team:SIEM) |
@leehinman Since not yet supported by beats, how are you currently shipping SIEM events? |
This adds a new ingest pipeline and fields to populate from Check Point CEF logs. Closes elastic#16041
* Make CEF key name mapping case-insensitive There's some case inconsistency in CEF docs (i.e. C6a4Label). Better to ignore case when mapping keys to full names. * Add missing custom CEF extensions This adds: - `deviceCustomIPv6Address2(Label)`: Only 1, 3 and 4 were expected. - `flexNumber[12](Label)`: These two alternative custom numbers were dropped after V23 of the spec, but still used by some vendors. [Maybe unnecessary] changes: - Changed the case of `DeviceCustomNumber2` from uppercase as documented) to lowercase to align with the other fields. * CEF module: Support Check Point devices This adds a new ingest pipeline and fields to populate from Check Point CEF logs. Closes #16041
Thank you @adriansr ! |
* Make CEF key name mapping case-insensitive There's some case inconsistency in CEF docs (i.e. C6a4Label). Better to ignore case when mapping keys to full names. * Add missing custom CEF extensions This adds: - `deviceCustomIPv6Address2(Label)`: Only 1, 3 and 4 were expected. - `flexNumber[12](Label)`: These two alternative custom numbers were dropped after V23 of the spec, but still used by some vendors. [Maybe unnecessary] changes: - Changed the case of `DeviceCustomNumber2` from uppercase as documented) to lowercase to align with the other fields. * CEF module: Support Check Point devices This adds a new ingest pipeline and fields to populate from Check Point CEF logs. Closes elastic#16041 (cherry picked from commit f6fde2e)
…vices (#17111) * Make CEF key name mapping case-insensitive There's some case inconsistency in CEF docs (i.e. C6a4Label). Better to ignore case when mapping keys to full names. * Add missing custom CEF extensions This adds: - `deviceCustomIPv6Address2(Label)`: Only 1, 3 and 4 were expected. - `flexNumber[12](Label)`: These two alternative custom numbers were dropped after V23 of the spec, but still used by some vendors. [Maybe unnecessary] changes: - Changed the case of `DeviceCustomNumber2` from uppercase as documented) to lowercase to align with the other fields. * CEF module: Support Check Point devices This adds a new ingest pipeline and fields to populate from Check Point CEF logs. Closes #16041 (cherry picked from commit f6fde2e)
This was closed after merging CEF support for Check Point but shouldn't have been closed as this is just support for the CEF output but not for Check Point logs in general. |
@adriansr: what’s the difference here? |
Check Point can generate logs in CEF format, so we updated the cef module to understand the custom fields it adds. But also has it's own log format which is the default and provides more information than CEF. We'll add a new module to support those logs. |
Most likely using Checkpoint Log Exporter and CEF format
Checkpoint can export logs via CEF using their "Log Exporter". I found a list of mappings:
https://community.checkpoint.com/t5/Logging-and-Reporting/Log-Exporter-CEF-Field-Mappings/td-p/41060
Info on Log Exporter:
https://community.checkpoint.com/t5/Logging-and-Reporting/Log-Exporter-guide/td-p/9035
https://sc1.checkpoint.com/documents/R80.20.M2/WebAdminGuides/EN/CP_R80.20_M2_LoggingAndMonitoring_AdminGuide/html_frameset.htm?topic=documents/R80.20.M2/WebAdminGuides/EN/CP_R80.20_M2_LoggingAndMonitoring_AdminGuide/203039
The text was updated successfully, but these errors were encountered: