Recently nobody asked me what I thought of the future of network security. So I’m writing you about it.
Also, nobody asked me how I’m doing, if they can sit with me, or if I want fries with that but I’ll save those for future articles.
This is the future of network security. This. Right now. What you see now is the future. Exciting, isn’t it?!
Let’s recap why it’s so. The first RFC on the Internet Protocol as well as TCP and ICMP came out in September 1981. That was the magical time of your parent’s youth when shirts showed belly, kids climbed over the seats while driving, and movie stars could be President. Anything and everything seemed possible then.
Fast forward to today. The world has become a completely different place where shorts show cheek, kids climb over the seats while flying, and television stars can be President. Meanwhile TCP/IP has not changed. Most RFCs regarding TCP or IPv4 focus on updates to how the protocols are being used today rather than documenting how they should be used. It’s like instead of policing society to be in compliance to the laws they’re updating the laws to match society! Which, actually, kind of makes more sense…. Never mind.
So that’s why we’re here now in the future of network security, because the network hasn’t really changed while the world has. Actually, that’s not completely true. There’s many more protocols and many more types of networks both wired and wireless and in between. Most run over IP. So never mind that. But it’s the basic transport protocol that’s in main use has not changed enough to require–
You know what. That’s crap. So much has changed in networking even if TCP/IP really hasn’t. I’m not going to try anymore (Read more...)
This is a Security Bloggers Network syndicated blog post authored by Pete Herzog. Read the original post at: Cylance Blog