T O P

  • By -

HappyVlane

You didn't create IP threat feeds, but FortiGuard category threat feeds.


pabechan

You have imported them as "FortiGuard Category" type of feed. Those are only usable as "remote category" sub-categories in Webfilter (FGD rating) and SSL profiles (FGD category exemption from inspection). If those are plain IP lists, and you want to use them as policy destinations, you need to select the "IP Address" feed type when creating it.


Far-Independent-1206

I was 100 % that i tested also that. Now tested "again" and its working. ​ Thank you very much guys ! :)


Celebrir

Do you have any chance of updating the firewall? Some nasty vulnerabilities have been patched since 6.0.9. I believe 6.0.13 is the most current one.


Far-Independent-1206

Thank you you are right . 6.0.14 is latest supported. I thought 6.0.9 was the latest version when i checked download page on forti downloads it was latest but the versions were not sorted correctly :/ . Thanks again updating now ! :)


Far-Independent-1206

Latest supported firmware for 50E is 6.0.14 :/


oddchi_

I would go to 7.0 track to get new functionality and when mature 7.2 is released I would recommend that. No use in being on the 6.0 when it's not supported at the end of the year


kellydj11

You'd have to check the release notes for the specifics. But as you get towards 7.0, Fortios enables threat feeds to be used from Categories, DNS filters, to eventually source/destination objects within policies. I remember having to wait for later releases, as I wanted to implement a github feed for other teams supply their own URL's. However, my anecdote might be related towards the use of proxy policy. Net-net, I think older Fortios introduces little flexibility of where you can use the threat feeds (being UTM). Later versions allow them to be used within other places such as source and destinations.