Next-Generation Firewall Service - What are the necessary pieces here?

role of next-generation firewall in tomorrow's borderless networks

Current Job Listings

Well, the reality is that view that we have of anything as next-generation is a moving target. our view for that entity changes over time, largely fueled by innovation (and in some ways the service packaging). In this blog entry, I'd like to focus on next generation firewall. Quickly, firewall started to be stateless, then became stateful. Over the period of time, we saw full L4-L7 awareness to protocol headers and payload via what we called ALGs (Application Layer Gateway). Well, that served us for a good chunk of time, before we entered into an era where HTTP/HTTPs became practically the new transport protocol (over TCP). This gave birth to another problem of application visibility, which essentially required sort of HTTP in depth analysis along with a lot of other innovation that has happened lately. Gartner, recently, published a report on what they think is the Next-Generation Firewall, point to Reference section for more details. Here are some details, to get your started, and get your creative juiced flowing in order to have a productive conversation here. #1: Application Awareness and Full Stack Visibility #2: Integrated Rather Than Co-Located IPS #3: Extra-Firewall Intelligence #4: Standard First-Generation Firewall Capabilities #5: Support “bump in the wire” Deployments Last but no least (hey, it wouldn't be complete without a contrarian perspective): #6 Things That a Next-Generation Firewall Isn’t Now, I'm looking for your feedback here, please share your thoughts, comments, questions, experiences and above all, your Vision of what Next-Gen Firewall are supposed to be! Reference:

Join the Network World communities on Facebook and LinkedIn to comment on topics that are top of mind.
Now read: Getting grounded in IoT