I am struggling with Algosec regarding the ability to forward syslog data with the right format.
Traffic is hitting the Algosec server but is is not parsing any PA Traffic log data.
Because the format and content in the traffic log is customisable I wonder if I am using the correct format here..
Any tip is highly appreciated
I know this post is old, but did you ever get syslog from PA to AlgoSec to work?
I am struggling with the same issue; the AlgoSec is getting traffic from PA but it is not parsed.
Anyone else got AlgoSec to work with Palo Alto?
The syslog implementation guide should be a great reference to construct your own syslog strings.
Remember however that syslog in total is limited to 1024 bytes per msg. Dunno how custom format in PA handles this.
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!