Google

Thursday, 3 October 2013

Building Big Data or Big Risks?

Big Data or Big Risks
The world was shocked a few months back when media reports revealed that US National Security Agency  was gathering personal data of all citizens and storing it in a large data warehouse. Everyone was outraged at this invasion of privacy by their own country's national guards. But wait a minute! Marketing companies, product and service providers have been collecting our info since time immemorial. Why is it that we think our details with them are not being misused, and the one with NSA is? At least NSA is well equipped to keep it safe and secure.  

Companies that are building Big data don't realize that unintentionally they are putting it under big risk too. They may inadvertently share consumer's personal information such as address, date of birth, contact number and even annual income. The most prevalent example is the logistics chain that uses customer personal info to deliver goods. Such information moves from retailer to wholesaler and manufacturer, and then to logistics companies before reaching the customer. Although this process may support stakeholders to efficiently deliver the product, but this information is also vulnerable for misuse. The onus lies with companies to make sure that personal information is being used sensibly.

IntroducingBig Data, Hadoop, and No SQL Databases Training will help you understand the fundamentals of this concept and also make you avoid the mistakes outlined above using NoSQL and Hadoop databases. The biggest strength of Big data is also is biggest weakness. That is, its ability to combine data from multiple sources. In such cases, individuals can be identified by simply merging multiple data sets into one. While companies may take measures and classify information as non sensitive, but they don't realize the repercussions when non sensitive information becomes sensitive when combined.


Koenig Solutions offers this course for users who wish to build secure big data and leverage it for best possible use.

No comments:

Post a Comment