Skip to content
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

Check Point module - Review the docs/template on how to switch between UDP/TCP #36043

Open
lucabelluccini opened this issue Jul 11, 2023 · 3 comments
Labels
Stalled Team:Security-Deployment and Devices Deployment and Devices Team in Security Solution

Comments

@lucabelluccini
Copy link
Contributor

The Filebeat Check Point module uses this file as "template": https://github.com/elastic/beats/blob/v8.8.2/x-pack/filebeat/module/checkpoint/firewall/config/firewall.yml

It seems that the template file is switching between tcp and udp based on the ssl settings presence, which is weird.

{{ if .ssl }}

type: tcp
host: "{{.syslog_host}}:{{.syslog_port}}"
ssl: {{ .ssl | tojson }}

{{ else if eq .input "syslog" }}
...

Meaning that if we use:

- module: checkpoint
  firewall:
    var.syslog_host: 0.0.0.0
    var.syslog_port: 9001
    var.ssl.enabled: false

We can switch to tcp.
Proof:

{"log.level":"info","@timestamp":"2023-07-11T18:30:32.159+0200","log.logger":"input.tcp","log.origin":{"file.name":"tcp/input.go","file.line":105},"message":"Starting TCP input","service.name":"filebeat","address":"0.0.0.0:9001","ecs.version":"1.6.0"}

It's weird though we have such template. Wouldn't it be better to explicitly call out the protocol to be used?

By the way, it is also tricky now to switch to a "good" behavior as users might have already started using the module...

Also, a general suggestion would be to prefix the ssl settings with var in the examples of the doc.

FYI @P1llus

(On integrations side https://github.com/elastic/integrations/blob/main/packages/checkpoint/data_stream/firewall/manifest.yml#L4 it seems explicitly set as input: tcp / udp / logfile - so all good).

@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@ebeahan ebeahan added Team:Security-Deployment and Devices Deployment and Devices Team in Security Solution and removed Team:Security-External Integrations labels Jan 31, 2024
@elasticmachine
Copy link
Collaborator

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

@botelastic
Copy link

botelastic bot commented Jan 30, 2025

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!

@botelastic botelastic bot added the Stalled label Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stalled Team:Security-Deployment and Devices Deployment and Devices Team in Security Solution
Projects
None yet
Development

No branches or pull requests

3 participants