Do we need a Hans Brinker for Office 365 Security or is the flood unstoppable?

News Upcoming Webinars Trade Shows and Events Press Releases Newsletters Blog

Do we need a Hans Brinker for Office 365 Security or is the flood unstoppable?

As a matter of fact, the story of the little boy who stopped a leaking dyke and saved the town from a flood, wasn’t really named Hans Brinker. The poor little guy was never given a name in the story, and readers got confused and called him Hans Brinker (of the silver skate’s fame). After almost freezing to death as no one ever came to find him until the next day, he did end up saving the town.

And, you may ask, what does this have to do with cloud security? In mid-February, Microsoft made available to the masses multi-factor authentication for Office 365, including security enhancements for those using Yammer in SharePoint. Any vendor that adds additional security precautions gets a plus in my book. Unfortunately, cloud security, or even enterprise security still needs to evolve.

I think the security marketplace should being to turn towards security at the content asset level, as we do. We no longer need analysts to tell us of the burgeoning growth of unstructured content. We know it, most of us encounter it every day (which is why I can no longer find the files that I need). The issue is not in the security architecture or strategy, it is the inability to identify potential sensitive information exposures that are unknown. Sensitive information exists in documents, scanned items, faxed items, emails, and could be in any unstructured or semi-structured content. Many security applications provide the ability to recognize industry standard descriptors such as a social security number or credit card number, other sensitive and confidential information can exist that contains information the organization does not wish to share.

Most exposures are caused either intentionally or unintentionally by the organization’s own staff. They can prove costly, damage brand, and increase organizational risk.
Similar to our poor little nameless boy, the problem was miniscule as all he needed was an eight year old finger to avoid a devastating flood. The same with unstructured and semi-structured content, a small hole can also bring down an organization.

Search Webinar