HI please recommend to me a firewall analyzer software that compatible with astaro UTM and generate live report except manageengin firewall analyzer thanks all
It fails to even find their test log, which is there.
Sorry I didn't notice your post earlier. I sent them a few entries from my Sophos log for an example, and these are the directions they sent back for my log:
1. In the Log profiles tab, create a new log profile 2. Browse to one of your log files. 3. As before, Firegen will probably fail to identify the log format 4. Verify if the log naming convention was identified correctly. If you just analyze logs that you saved then you don’t need to worry too much about the naming convention as you will analyze the logs on demand. 5. Click on New pattern 6. In the Log entry parsing syntax enter:
(\d{4}): (\d\d): (\d\d)-(\d\d:\d\d:\d\d) .*?(log).*?id="(\d+)" (.+) My note-I had to add spaces after each colon, this board was seeing the two characters : and ( together as a sad face [:(]
Note: Since the log sample that you sent us does not contain a field to identify the firewall itself, we have set the parsing syntax to use “log” as the firewall identifier (this appears in all the log entries).
7. In the Field mapping enter:
5,1,2,3,4,6,7
10. "Has year" checkbox should be checked 11. Set the Firewall type as Sophos UTM 12. Save 13. Click Test pattern to verify that the information is matched properly. ... There was some sample output and info I can send if needed.
They also updated the version on their web site for the 30-day trial to v3.35 which included changes they made for the Sophos logs.
It fails to even find their test log, which is there.
Sorry I didn't notice your post earlier. I sent them a few entries from my Sophos log for an example, and these are the directions they sent back for my log:
1. In the Log profiles tab, create a new log profile 2. Browse to one of your log files. 3. As before, Firegen will probably fail to identify the log format 4. Verify if the log naming convention was identified correctly. If you just analyze logs that you saved then you don’t need to worry too much about the naming convention as you will analyze the logs on demand. 5. Click on New pattern 6. In the Log entry parsing syntax enter:
(\d{4}): (\d\d): (\d\d)-(\d\d:\d\d:\d\d) .*?(log).*?id="(\d+)" (.+) My note-I had to add spaces after each colon, this board was seeing the two characters : and ( together as a sad face [:(]
Note: Since the log sample that you sent us does not contain a field to identify the firewall itself, we have set the parsing syntax to use “log” as the firewall identifier (this appears in all the log entries).
7. In the Field mapping enter:
5,1,2,3,4,6,7
10. "Has year" checkbox should be checked 11. Set the Firewall type as Sophos UTM 12. Save 13. Click Test pattern to verify that the information is matched properly. ... There was some sample output and info I can send if needed.
They also updated the version on their web site for the 30-day trial to v3.35 which included changes they made for the Sophos logs.
