Thanks so very much for watching and taking the time to comment!

This is one of the best network Lay man explanations. This is the view I have ever seen

Thank you for saying so!

Thanks so much @CubensisEnjoyer! I’m really glad to hear that you are enjoying the series and that it is hitting the mark for you. It’s always a challenge to try to hit that sweet spot of have substantive content without being overly technical. Good to know that we’re getting there for you!

I am preparing for a job interview and this series is a very good refresher for my entry level CC certificate from ISC2 but with sufficient practical information to keep me on the edge. Thank you very much for your time and effort Jeff. If and when your time allows, could you please do a video on the ETC part? I want to hear you speak on that one as well. Thank you sir.

I love hearing this! Glad it helped

Thanks so much for all the great feedback! This is what makes the effort all worthwhile!

You are far too kind!

I love ginni rometty

I’m so glad you are enjoying the series! I do a deeper version of this in the course I teach at NC State University but it’s only available in the classroom, unfortunately, so I came up with this reduced format version for the channel to at least get out some of the basics

So glad you liked it!

Glad you liked it!

You are very kind to say so! Comments like yours make it all worthwhile!

Thanks so much for saying so!

Thanks so much!

Thank you for watching!

My pleasure! Thanks for watching!

I’m so glad to hear that you liked it! Thanks for saying so!

Thanks for the feedback! Those topics may be a bit deep for this channel but I’ll see what I can do going forward

Thanks so much for saying so! Glad you liked it!

Thank you for all the kind words! That saying you quoted is very true. I have found I had to dig deeper and improve my own understanding in order to develop this material

Glad you liked it!

Thanks for saying so!

You’re most welcome!

Thanks @kent_calvin! Very nice of you to say so!

Thanks for saying so!

Can you guide me how to complete the course in Coursera.I am interested to do.

Awesome! Best of luck with your learning journey!

I’m glad you liked it. Unfortunately, the “guards, guns and gates” of physical security are areas where I would be out of my depth since all of my work has been in infosec

Thank you!

same here

Good point. So often I’ve found these two combined at the product level that the lines get blurred so I went with the usage that I thought people are likely to run into

Exactly my thought. He conflates stateful filtering and deep packet inspection. Also, describing SSH as a VPN is a great example of where the OSI model fails to reflect the real world. A more important point, I think, and also something that beginners often don't realize, is that VPN does not necessarily always include encryption, e.g. MPLS. But, this is not a networking tutorial,so that may be too out of bounds.

Actually, a less detailed and less convoluted explanation of SASE is probably more appropriate for this series. SASE is really about extending the security perimeter from the edge of the corporate network to the remote endpoint ( think user with their laptop at home or in the coffee shop ). The details of how that is accomplished vary by vendor because SASE is only defined at a high level, and has a hardware component ( SD-WAN ) that also varies widely by vendor.

Typically, the firewalling functions operate at wire speed so there really is no noticeable lag

I really combined both in my description of SPI in the interest of time but technically SPI is about considering state/order of the packets whereas deep PI is about digging deeper past the header into the details of the payload/data

A more detailed answer to the question. First, consider the packet filtering firewall. It operates on the 5-tuple ( protocol, source and destination IP address, source and destination port ) in only one direction. Thus, two rules are required to allow bi-directional traffic. Generally, the packet filtering firewall is in the form of an Access Control List (ACL) on a physical device, and is not a physical device on its own. The stateful firewall eliminates the single direction limitation by implementing a connection table that tracks traffic in one direction and automatically implements policy to allow the traffic to return. Only one rule is required to allow bi-directional traffic. This type of firewall is commonly a physical device, but can take the form of a type of ACL or software on a host ( i.e. Windows Firewall ). Deep packet inspection is not directly related to either of the two firewall types, although it is most commonly found in stateful firewalls. DPI simply refers to the fact that the firewall can look beyond the packet headers and into the payload, as part of the decision to allow or drop the traffic. The effectiveness of DPI is limited by encryption. The firewall cannot protect against what it cannot see. This limitation is commonly overcome through the use of decryption of inbound traffic and re-encryption as the traffic leaves the firewall, which comes at a cost of higher CPU usage and added latency.

Sorry about that. I have a limited amount of time on the channel to cover a lot so some parts get squished, I’m afraid

@@jeffcrume I would really want to be one of your students some day.What a good tutor,i hope i can be able to explain concepts like these easily to my juniors

Sorry to disappoint …😂😂

😂