Everyone knows how tough the economy is these days.  People are having a tough time making ends meet, business is slow and generally people want a way to forget about it all sometimes.  I openly admit that I did not make up this list, but a Texas radio station web site recently published "You Know It's Been a Tough Year When..."

10.  The economy is so bad that i got a pre-declined credit card in the mail.

9. I ordered a burger at McDonald's and the kid behind the counter asked "Can you afford fries with that?"

In my first post on this subject, I talked about whether there truly is a need to have a DR/BC plan or process.  As much of a pain it is to think about this stuff and actually plan for it, I think we all know we need to get it done.  The big question really is "How"?  The information we'll talk about during this and the following two steps is something to get you started.  Most organizations will dive deeper into this I'm sure.

I'm sure many of you that are reading this post had high hopes that all of the work required to create, implement and test DR/BC plans wasn't needed!  I honestly wish I could say that were true.  Unfortunately, we all know that doing business eletronically means that we need to protect those valuable assets.

In response to the New York Times' article "Lost in the Cloud" by Jonathan Zittrain published July 19th, 2009:

This article simply drums up a very old discussion regarding security and privacy vs. accessibility that has been discussed for years.