The March 15, 2008 SploitCast podcast was recorded at SchmooCon and consisted of a panel discussion including some notables in the InfoSec space: Johnny Long, Rodney Thayer, Simple Nomad, Landon Lewis, Squidly, and Matt Hillman.
Though the entire cast is a must-hear, with an extensive discussion SCADA and critical infrastructure security, the conversation turned toward practical security in a space where the boundary of the ‘network perimeter’ is rapidly vanishing.
Simple Nomad made the observation that end users don’t, and won’t, care about security. Paraphrasing, it’s not that they are dumb, or stupid, but that they have different areas of expertise, and security may not be it.
The group agreed that security awareness is important, but it can’t be ‘the fix’. Users will not become security experts. Users can, however, be taught basics, such as not clicking on untrusted links in email.
At this point, Johnny Long stepped in.
He stated that awareness is good, and perhaps policy as well, but that when we really boil this security thing down, it reduces to three basic principles:
- A server should not be a client
- A client should not be a server
- Peers should only connect in certain ways
He noted that when a computer changes roles, that’s when we know there’s a problem.
For example, when a laptop gets infected with bot malware and begins phoning home, it starts acting like a server, and that’s the behavior we should be looking for.
Important points, and I subscribe to this view of the network.
It doesn’t matter if the device is completely controlled by our IT team, or an iPhone connected inside our network… If it’s a client, it should be acting like a client…
Imagine the simplicity of this view.
Suppose we had the simple tools necessary to determine if our machines are abiding by their designated role, then what will we need to ensure about the device.
Do we have to ensure that the box is 100% patched?
Do we have to pay lots of cash for anti-virus, anti-phishing, anti-this and anti-that?
Do we have to make sure that the user has a 100% crack-resistant password?
Do we have to spend countless hours configuring our network to prevent unauthorized hosts?
Perhaps not.
One simple reason, it takes much less time to re-ghost a PC than it does to keep it ’secure’.
In my organization, for example, we could let the desktops and laptops run free on the Internet.
As long as we know what clients are allowed to do on the network, and what they are not allowed to do, then we are far better off.
Imagine this… Say you have all the latest updates, and anti-virus scanners and whatnot. Well, do you know you are safe, or do you believe you are safe?
If you believe you are safe, then I’ll be happy to show you how you are wrong. And if you know you are safe, then I’ll call you ignorant.
Why? Because security degrades over time. Even the most secure system on earth is only secure until an attacker finds out a new way into the system.
For example, social engineering always works… Plain and simple, it doesn’t matter how secure the system, if I convince you to reveal the appropriate information, I will own you.
Perhaps I need to ponder this a little more, but it seems logical that we can dramatically simplify our IT infrastructure if we focus on separation of duties in the hardware/software space, and then focused our security dollars on making sure that those roles were being followed.
The old conceptions of the network no longer apply in a space where the network perimeter is porous, or non-existent. We need to change our thinking to match reality.
Bill