03-17-2021 07:33 PM
Hello All,
I've been using FortiGate for my firewall choice and would recently like to switch to cisco ASA.
one thing that I noticed from the FortiGate, is that it does not have ACLs, instead, it has something called Policy to filter the IPv4/IPv6 packets.
Now, ACLs are straight forward in terms of packet filtering. You specify the condition, bind it towards a certain direction of an interface. it's works like a filter.
But when digging deeper into understanding the difference between Fortigate Policy and Cisco ACLs (actually ACLs in general, I only see policy on Fortigate). There's a feature called session tracking which I found pretty useful.
In short, when applying an allow policy, not only does Fortigate allow the packet to pass from the source interface to destination interface (you have to specify 2 interfaces), it also tracks the session so that the reply packet in reverse direction gets allowed as well.
In user friendly terms, this becomes useful since I can simply put an allow policy from host A (connected to interface A) to host B (connected to interface B), so that host A can initiate network session talks such as SSH, ICMP, etc while host B cannot do the samething backwards.
Now that I'm trying to replace the Fortigate with Cisco ASA, is there a similar feature of which I can utilize and achieve the same effect?
Thank you
Solved! Go to Solution.
03-18-2021 12:54 AM
n user friendly terms, this becomes useful since I can simply put an allow policy from host A (connected to interface A) to host B (connected to interface B), so that host A can initiate network session talks such as SSH, ICMP, etc while host B cannot do the samething backwards.
if i understand correctly same thing works with ASA its stateful firewall, when you enable stateful inspection - it automatically tracks the connection from inside to destination and maintains a state table.(not other way around.)
for reference : (hope this what you looking ?)
03-18-2021 12:54 AM
n user friendly terms, this becomes useful since I can simply put an allow policy from host A (connected to interface A) to host B (connected to interface B), so that host A can initiate network session talks such as SSH, ICMP, etc while host B cannot do the samething backwards.
if i understand correctly same thing works with ASA its stateful firewall, when you enable stateful inspection - it automatically tracks the connection from inside to destination and maintains a state table.(not other way around.)
for reference : (hope this what you looking ?)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide