Security. It’s an interesting topic when it comes to networking within Enterprise IT. There are those that are truly focused on an end to end view of security or just freakishly enjoy security and then those that are usually okay with just implementing a perimeter FW and maybe an IDS/IPS. So, when it comes to your “typical” Enterprise LAN, all hosts are inherently trusted so communication between clients and servers, clients and clients, and servers and servers, is unprotected. I will say, in 2011, I've seen this starting to change and infrastructure security is becoming even more critical for the average “mid-market” customer for various reasons, but heavily attributed to the wide adoption smart phones, tablets, and the whole “Bring Your Own Device” (BYOD) mantra being driven by the consumer.
Anyway, what does this have to do with OpenFlow/SDN? Nothing…yet, but the question that came to me while I was in a meeting with a NYC based financial firm last week was, “How will security be perceived with running a *real* virtualized network with control plane separation happening at a controller?”
Before I go any further, here is some background…
Anyway, what does this have to do with OpenFlow/SDN? Nothing…yet, but the question that came to me while I was in a meeting with a NYC based financial firm last week was, “How will security be perceived with running a *real* virtualized network with control plane separation happening at a controller?”
Before I go any further, here is some background…
1 Comment
RSS Feed
