Get the real story via our monthly newsletter

Search

    2
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > The reality of content security

TrendWatch Blog

The reality of content security

24-Jan-2008

My colleague Jarrod forwarded a link to a news story of how one person deliberately destroyed 7 years worth of corporate content/data with ease. Meanwhile, I had another tab open, regarding the White House's inability/refusal to archive emails, and had just finished reading about the loss of a laptop containing the personal details of 600,000 people -- quite a busy day for data destruction.

Fact is, few days pass now without news about another major breach of data privacy, illegal destruction of data, or the inability to find historic data. It's a stream of data points that will doubtless boost the revenues of Records Management, eDiscovery, ECM, Search and Archiving vendors across the globe. It will happen like this: These stories (along with many others) will become part and parcel of the vendors' sales pitch in 2008 and 2009 - a steady stream of ever more disturbing and frightening cases of data nightmares. After these vendor presentations you may feel a desperate need for those vendors' products, and that only with their help can you avoid certain disaster.

But the truth is, these stories (and nearly all the others I read) point to a problem for which no software vendor or consultant can truly offer a solution: employees and bosses can be incompetent, stupid, and dishonest. At the end of the day almost all major security breaches relating to content and data are due to such poor behavior, rather than the result of artful hackers working from secret government locations in China (or for that matter the bedrooms of teenage geeks in Ohio).

Yes, in all the three cases above, better governance and compliancy related software might have helped. The White House really should have an email archiving system in place (and I recommend our President to read my November blog entry on Backup vs Archive), laptop data containing such incredibly sensitive data should have remote locks and controls, and if the architectural firm had proper archiving, the data would have been much easier to recover. So maybe the lesson then is that you should expect people to behave incompetently, dishonestly and be downright stupid on occasions, and you should plan to have safety nets in place for when this happens. But that no software can prevent it from happening in the first place.

- Submitted by: Alan Pelz-Sharpe, Analyst

All ECM Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us



Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.




What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

18113 Town Center Drive, Ste 217

Olney, MD USA 20832

1 800 325 6190 (N. America only)

+1 617 763 5336 (customer service)

+1 301 585 7004 (editorial)

Fax: +1 214 242 3048