We have started using these as a front line of defense before all other inbound policies. My understanding is these are MORE explicit. So if you say DENY inbound from WAN from ALL to ALL for port 3389 it will be more inclusive as it relates to the attack surface of the device than creating a normal policy with the same constraints? In other words, using a normal policy might leave some of the mgmt ports exposed to probing on that port? The only downside is that there appears to be no logging so we lose the ability to monitor volume of the drops other than the packet count shown in the GUI.
Am I using this properly? How are others using the IPv4 ACL feature if at all?
Docs say how, would be good to know "when and why."
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.
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 |
---|---|
1660 | |
1072 | |
751 | |
443 | |
220 |
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.