Syslog to Elastic Integration - 2.4.x #11649
Replies: 5 comments
-
Did you follow this? https://docs.securityonion.net/en/2.4/syslog.html?highlight=syslog#syslog |
Beta Was this translation helpful? Give feedback.
-
yes I have, How can I check the external firewall from within my Onion box as NMAP from the bastion is seeing a port but with a status of closed. |
Beta Was this translation helpful? Give feedback.
-
I am having the same problem. I am trying to get syslog forwarding from my pfsense box to the so box. [root@securityonion ~]# iptables -L Chain FORWARD (policy DROP) Chain OUTPUT (policy ACCEPT) Chain DOCKER (1 references) Chain DOCKER-ISOLATION-STAGE-1 (1 references) Chain DOCKER-ISOLATION-STAGE-2 (1 references) Chain DOCKER-USER (1 references) Chain LOGGING (2 references) Chain FORWARD (policy DROP) Chain OUTPUT (policy ACCEPT) Chain DOCKER (1 references) Chain DOCKER-ISOLATION-STAGE-1 (1 references) Chain DOCKER-ISOLATION-STAGE-2 (1 references) Chain DOCKER-USER (1 references) Chain LOGGING (2 references) I did see a diff when I did a so-firewall apply
|
Beta Was this translation helpful? Give feedback.
-
Interesting. ACCEPT udp -- anywhere udp dpt:syslog so for me, the SOC firewall only added upd messages. I changed the rsyslog configuration to send UDP messages and things are now working and I am seeing parsed messages. BUT |
Beta Was this translation helpful? Give feedback.
-
I ran the command via so-firewall, kind of miss so-allow |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to get syslog integration working between a Raspberry Pi and SO. The PI is working as a bastion and network traffic is covered by Zeek. I am trying to add syslog via the Elastic ingestor.
When I connect rsyslog between the machines the logs sync correctly but this is not what I want as the log messages get merged in SO.
I have added the Raspberry PI IP address to the syslog firewall rules in the SOC.
When I disable the listening port on SO rsyslog.conf the Raspberry PI complains it cannot see a listener on 514. Running NMAP from the PI shows the port is closed.
I have read the documentation for 2.3 and 2.4 to see what I am missing and I thought I had done everything.
Beta Was this translation helpful? Give feedback.
All reactions