Breaking

Tuesday, February 10, 2015

What the cloud will learn from the data-breach epidemic

Anthem joins the likes of Sony and residential Depot within the data-center hack parade, however cloud fans should not get too content

 

Last week, the second-largest U.S. health insurance firm, Anthem, declared that as several as eighty million customers had their account data purloined. Not abundant is understood regarding that systems were hijacked, however Anthem aforementioned all of its businesses were affected, thus it is easy to work that the attack was extensive.

"'The names, addresses, birth dates, and Social Security numbers purloined from the Indianapolis-based insurance big area unit gold for criminals,' aforementioned James P. Nehf, a academic of law at the Indiana University Henry Martyn Robert H. McKinney faculty of Law in state capital," USA these days reportable.

Once again, there is a major data breach on internal servers.

Those who promote cloud computing can get a bit arrogant about outages and breaches, which are few and far between on the cloud. However, considering that only 1 percent of our data and applications are in the cloud, it's clear that cloud systems have yet to be truly tested. Their day will come.

The common pattern around the recent data breaches is that hackers simply exploited vulnerabilities in traditional systems that the companies did not take steps to address. I suspect thousands of systems out there have the same kinds of vulnerabilities, so more data breaches are coming.

Those who deploy cloud systems can learn a lesson from these breaches: Security needs to be systemic. Security can't be a bolt-on at the end of the build process. Instead, it must be continually updated during the life of the system. The effectiveness of security depends wholly on the planning and technology applied to the problem, for both cloud and traditional systems.
Let's get a clue and provide better security from the start, no matter where your systems are hosted.

Read More Updates :- Techies | Update

No comments:

Post a Comment