2.24.2013

Federal Sequester - Who's fooling Whom?

$85B - Annual impact of 'Sequester' on US Government Spending.
$85B - Monthly 'purchase' of US Treasury Bonds ($40B) and Mortgage backed securities ($45)

The sequester doesn't touch 80% of US Federal Government deficit spending this year or any year to follow.

And how does the government 'pay' for that deficit? The Federal Government simply issues IOU's in the form of US Treasury Bonds, Bills, and Notes. Because of the eroding confidence in the US Treasury's ability or desire honor those debts - the Federal Reserve Bank buys what the market won't with 'money' ingeniously and simply created on it's own balance sheet.

Sequester? Killing the economy? If a less than 20% cut in the unfunded or deficit spending trigger's a new recession, it's not sequestration that caused it. We need look no further than the chickens of massive Federal Reserve money creation machine coming home to roost, coupled with profligate Federal spending.

Let's get real. Who's fooling whom?

2.18.2013

Data breach, are you prepared?


I witnessed an exchange between a senior level corporate executive charged with his company’s data security, and a security practitioner who asked him as a briefing opener, “What are your company’s plans for addressing a data breach?” The executive replied “Working at my local gas station.” The speaker dutifully chuckled and then said “No, really - what is your corporate breach procedure?” The executive responded “That’s not an option. I have a friend who owns a gas station not far from my house, and should my company be breached, I’ll be working for him the following day.”

You may be thinking (as did I at the time) that our hapless security officer was just trying to lighten the mood. And like me, you'd be wrong. I won’t elaborate as did this executive, but suffice it to say he appeared completely serious providing entirely too much information about his exit strategy, should it come to that. Since then I’ve thought long and hard about the issue.

Those in our business who’s job it is to identify the signs of breach and provide technology to mitigate it know that breach is not necessarily (and usually is not) catastrophic. But ignoring the skull and cross-bones on the bottle won’t make the poison any less deadly. Pretending breach can’t happen is likely only to exacerbate it’s effects.

To protect our businesses and systems against breach with human and technical measures is table stakes. To prepare to respond to data breach is the same as any other contingency or business continuity planning - is simply best practice. It's unfortunate the lack of the latter remains 'the unthinkable' to so many - evidenced by the following ground-hog's day scenario:

  • Week 1 (Company Spokesman) “The system compromised was an ancillary system containing no personally identifiable information."  
  • Week 4 (Company Spokesman) “We've determined that a small number of email addresses were leaked and we've notified the affected individuals. There is no evidence of further compromise."
  • Week 8 (Company Spokesman) "Our authentication system was apparently compromised and we've reset the affected accounts and notified account holders. Our systems are now secure." 
  • Week 10 (New spokesman) "Acme Inc. deplores the illegal and criminal theft of user accounts and business data, and is recommending it's customers and business partners reset their passwords and contact our hotline should they notice any unusual account activity."  
  • Week 12 (a Business Journal) "Acme Inc. shares continue to fall on further reports revealing the scope of last quarter's data breach and it's management's apparent inability to address the fallout in an open, timely, and forthright manner.

The bottom line is aptly articulated by Brian Lapidus, COO of the Cybersecurity & Information Assurance practice of Kroll:

“Establish a comprehensive breach preparedness plan that will enable decisive action and prevent operational paralysis when a data breach occurs.”

Not quite the head-in-the-sand approach of our executive friend.


That data breaches occur is unsurprising. The trend indicates they will increase in both frequency and magnitude. Does your disaster recovery plan include a defined procedure to classify and deal with data breach? Has it been tested? Do you perform at least annual 'dry-runs?' If so, thank you. If not, why not?

Here is but a sampling of practice guidelines to help you get started:
http://www.krollcybersecurity.com/resources/data-security-resources/data-breach-prevention-tips.aspx
http://www.diskagent.com/resources/Data_Breach_Incident_Response_Workbook_by_Debix.pdf
http://usa.visa.com/download/merchants/cisp_responding_to_a_data_breach.pdf
http://www.experian.com/assets/data-breach/brochures/response-guide.pdf
http://www.americanbar.org/content/dam/aba/administrative/litigation/materials/sac_2012/22-15_intro_to_data_security_breach_preparedness.authcheckdam.pdf
http://www.justice.gov/opcl/breach-procedures.pdf
http://www.ibm.com/developerworks/library/cl-hipaa/index.html

~r