Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
FCNSP/WCSP
ORIGINAL: abc987 The docs sometimes have not all details. The relationship is between the " trusted hosts" and " administrative access" configured at the interface settings.Yes, that' s also my conclusion. However, it' s not only a matter of " details" , it' s totally misleading. They need to rectify their documentation.
ORIGINAL: Maik firmware you are mentioning is 4 MR2.Yes, my fortigate firmware is v4.0,build0346,120606 (MR2 Patch 12) Are you implying that this problem is solved in a newer version?
ORIGINAL: Maik see a ping to a fortigate as an administrative task. so only " admins" are allowed to do that.Well, maybe, but it' s a matter of viewpoint and interpretation, and therefore it' s not objective enough. And there' s a flaw in this reasoning of yours: the ping works with whatever admin (because you only need to put IP address in any trusted hosts of any admin account). But there' s no login associated to a ping, how can you be sure that only admins are allowed to do that?
But there' s no login associated to a ping, how can you be sure that only admins are allowed to do that?It' s only dependent to the trusted hosts. If you have 0.0.0.0/0 in there (default) and have admin access boxes checked everyone can " connect" via http, https, ssh, ping... Login as a admin is after connecting. So ping works for everyone. Be shure which admin accesses you check on WAN-Interface If you need remote-access at WAN be shure no admin has 0.0.0.0/0 (restrict all admins to remote IP or privat IP)
FCNSP/WCSP
ORIGINAL: abc987Of course I understood all the implications (and complications) once I found out the workaround. My time is limited so I' m not going to comment on this. So I' ll let you think about it and see by yourself how this setting is bad and useless.But there' s no login associated to a ping, how can you be sure that only admins are allowed to do that?It' s only dependent to the trusted hosts. If you have 0.0.0.0/0 in there (default) and have admin access boxes checked everyone can " connect" via http, https, ssh, ping... Login as a admin is after connecting. So ping works for everyone. Be shure which admin accesses you check on WAN-Interface If you need remote-access at WAN be shure no admin has 0.0.0.0/0 (restrict all admins to remote IP or privat IP)
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1647 | |
1070 | |
751 | |
443 | |
214 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.