You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I have implemented the Barracuda CloudGen Firewall solution in 2 environments which both got a new Barracuda F18B installed.
These firewalls have both been set up to forward their logs to a separate Linux machine, which then forwards the logs over syslog to Sentinel.
The logs are visible in Sentinel, however they are not structured properly and the Dataconnector for Barracuda doesnt pick this datastream up.
Barracuda logs in Sentinel through syslog:
As visible in the screenshot above in my case there is no processname bound to the log messages (probably since its being forwarded) and the structure of the data is not the same as how the current parser expects it. I have tried to attempt to edit the parser to filter on the box_Firewall_Activity keywords instead of the processname, however this still does not parse as expected.
Current parser query:
I have attempted to save this query in one of the environments to the function code for the current parser, this doesnt seem to get picked up though however by the data connector (as its still showing as disconnected), I think there needs to be an update performed from the content hub to adjust this change.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
@thom2804, Could you please share the sample logs with us on below mail ID, so we can check the supported parsing format for it - v-sudkharat@microsoft.com
Thanks!
Hi @thom2804, since we have not received a response in the last 5 days, we are closing your issue as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation.
Recently I have implemented the Barracuda CloudGen Firewall solution in 2 environments which both got a new Barracuda F18B installed.
These firewalls have both been set up to forward their logs to a separate Linux machine, which then forwards the logs over syslog to Sentinel.
The logs are visible in Sentinel, however they are not structured properly and the Dataconnector for Barracuda doesnt pick this datastream up.
Barracuda logs in Sentinel through syslog:
As visible in the screenshot above in my case there is no processname bound to the log messages (probably since its being forwarded) and the structure of the data is not the same as how the current parser expects it. I have tried to attempt to edit the parser to filter on the box_Firewall_Activity keywords instead of the processname, however this still does not parse as expected.
Current parser query:
Therefore I created a new query which is able to parse my logs as expected:
I have attempted to save this query in one of the environments to the function code for the current parser, this doesnt seem to get picked up though however by the data connector (as its still showing as disconnected), I think there needs to be an update performed from the content hub to adjust this change.
Thanks in advance!
The text was updated successfully, but these errors were encountered: