We’ve been hearing about ‘computer glitch’ for a while. That’s what the talking heads on the news always cite when something goes awry with a computer system. Perhaps ‘malfunction’ is the new scapegoat? That’s the route GoDaddy is taking. They say it was a ‘malfunction’, not hacking, that took them and presumably hundreds of thousands (millions?) of other systems offline for hours yesterday.
I’m sure it had nothing to do with poor planning…or people making bad choices. That’d be too simple…and too responsible. It’s easier to blame computer problems on the obscure – something that can’t be understood – much less proven – by the general population, even forensics analysts.
Calling a network outage a ‘malfunction’ is similar to how legal counsel encourage executives to refer to security breaches as ‘events’. In the end, a business continuity problem is a business continuity problem. It’s your responsibility.
Stuff’s going to happen. You just have to ask yourself what needs to be done to minimize the impact to your business. Don’t wait until the you know what hits the fan to try to figure it out. Here’s some material I’ve written that can help you get started down this path.
“A business associate referred our company to Principle Logic when we were seeking a resource to perform vulnerability /penetration testing for our external and internal networks. We found Kevin Beaver to be professional, well informed, and easy to work with. His testing did not disrupt our networks, and his progress updates were timely.
His final report was very thorough and included security recommendations for our network environment. The executive leadership was so impressed with Kevin’s security expertise, they have extended their agreement to continue to perform periodic testing. We highly recommend Kevin Beaver and Principle Logic as a resource for network security testing.”