- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
03-16-2022 03:42 AM
First of all, I have a per TB license, so today I integrated the data of the fortigate firewall, forwarded it to the broker through the log, and opened the syslog applet on the broker. Configured according to the admin guide, the firewall is given to the broker in cef format. Now the xdr cloud data ingestion Dashboard can see the Fortinet log, but the Fortinet log cannot be seen in the dataset, why is this? Will there be a delay?
03-17-2022 05:51 AM - edited 03-17-2022 06:04 AM
hi
Could you verify that you selected product=fortinet, vendor=fortinet in brokerVM syslog configuration.
Also could you check tcpdump output from BrokerVM cli. For connecting BrokerVM, you can upload your ssh keys to Bvm via web console of BrokerVM or XDR management console. Another option is to use Live Terminal to BrokerVM.
This is just for verification whether you are receiving logs from Fortinet firewall. Because, if syslog enabled and Vendor and product set correctly in syslog configuration, You should have logs on xdr management console.
03-16-2022 06:44 AM
Hi @Grady
Yes, There might be kind of buffering. I didnt test this with BrokerVM but i know there is a buffering with XDR Collector. If your fortinet firewall is not super active firewall which is creating so much syslog data, you may see kind of latency.
Btw, My recommendation is verifying logs from the Query Builder. with that way, you can see latest logs and can able compare with current data/time.
03-16-2022 06:51 AM
Hi Etugriceri
I understand looking at raw log data, so which dataset filter should I choose in XQL? xdr_data? Because the dataset of fortinet is empty
03-16-2022 07:02 AM
Hi
No, xdr_data dataset is just including xdr agent telemetry datas. could you check log_log_raw or unknown_unkown_raw data sets?
When you activate syslog on BrokerVM, You are configuring "New Syslog Data Source" and You should select, Vendor and Product information with this two information XDR is understanding log type. If you've choosed Auto/Auto. maybe due to version of Fortinet, XDR cannot able to parse very well and keep logs in unknown_unknown_raw. otherwise, should be in fortinet dataset.
So just check it out.
03-16-2022 07:55 AM
Hi Etugriceri
I checked unknown_unknown_raw in xql, and I didn't find the data of the tower, this seems to be a confusing problem
03-17-2022 05:51 AM - edited 03-17-2022 06:04 AM
hi
Could you verify that you selected product=fortinet, vendor=fortinet in brokerVM syslog configuration.
Also could you check tcpdump output from BrokerVM cli. For connecting BrokerVM, you can upload your ssh keys to Bvm via web console of BrokerVM or XDR management console. Another option is to use Live Terminal to BrokerVM.
This is just for verification whether you are receiving logs from Fortinet firewall. Because, if syslog enabled and Vendor and product set correctly in syslog configuration, You should have logs on xdr management console.
03-17-2022 07:15 AM
Thank you for your reply, the Fortis dataset has data today, I think it should be caused by the Broker cache
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!