I currently have event triggers working on the FortiGate to ban IP's
when the event handler on the FortiAnalyzer sees a matching event from
the FortiGate. I also have an alert working within FortiAnalyzer for
FortiMail when the event handler sees a m...
Here is the latest from support:..."Looks like this ZSTD is implemented
in FortiOS for other uses, but not for inspection. This means that the
inspection profiles applied to a policy that is supposed to allow the
zstd-encypted sites will fail and the...
Adding exemptions is a workaround. The issue appears to be related to
Meta and specifically Zstandard (ZSTD -
https://facebook.github.io/zstd/). I'm not sure if FortiOS supports ZSTD
yet and I am waiting to hear back from TAC on what they think the i...
We're seeing the same behaviour, our internet browsing policy is
blocking some sites (e.g. Instagram, Facebook) when users are in Chrome,
but not while using Edge. The sites should be allowed as they are not
blocked. This is on a FortiGate 600E with ...
It's possible you have the source IP defined on the FortiGate. You can
view it in the CLI using the following: FG-600E # config log
fortianalyzer settingFG-600E (setting) # showconfig log fortianalyzer
settingset status enableset server "192.168.1.10...
Without making any changes to the automation stich, I was able to get
this working by adding the FortiMail as a downstream device in the
FortiGate Security Fabric.
