4 security measures that strengthen big data governance

4 security measures that strengthen big data governance

4 security measures that strengthen big data governance

As companies continue to redefine IT processes to cope with the semi-structured and unstructured data that characterize big data, they are also recognizing that standard data security practices that grew up with fixed-record, transactional data no longer address every big data security concern.

For starters, there are few controls on the mountains of big data that flow into companies on a daily basis. Big data can come from anywhere and in every form.

While companies can put controls in place to regulate the in-flow of this seemingly limitless data pipeline, there are very acute security concerns that emerge once the data is in enterprise data repositories where it can be accessed or shared. Who should be authorized to see the data in its entirety, and who within the organization needs to know some of the data, but not all of it?

"We are seeing major transitions in the big data market now," said Venkat Subramanian, CTO at Dataguise, a data protection and compliance vendor. "Companies are moving from traditional data services to the big data market, and they are beginning to move more of their standard and big data applications from on-premises data centers to the cloud. Whether big data is stored on premises or in a cloud environment, appropriate governance measures for this data are needed."

Read Also:
Big Data and DevOps: The Case for Bringing Them Together

As part of big data governance, there are several security measures that companies can take.

On a semi-annual or annual basis, IT should sit down with corporate stakeholders who access data from data lakes and repositories, and review data access permissions for all authorized personnel. Access permissions can be adjusted upward or downward based upon employee/contractor work responsibilities. When employees/contractors are no longer employed with the company, they should be immediately removed from access.

In some cases, masking can be used to redact sensitive data elements (e.g., social security numbers, names) so this data isn't shared with others outside of the company. Masking should especially be considered if the company wants to sell big data to third parties.



Chief Analytics Officer Europe

25
Apr
2017
Chief Analytics Officer Europe

15% off with code 7WDCAO17

Read Also:
Water Management Analytics

Chief Analytics Officer Spring 2017

2
May
2017
Chief Analytics Officer Spring 2017

15% off with code MP15

Read Also:
Will We Soon No Longer Need Data Scientists?
Read Also:
Google Cloud Databases Reach General Availability

Big Data and Analytics for Healthcare Philadelphia

17
May
2017
Big Data and Analytics for Healthcare Philadelphia

$200 off with code DATA200

Read Also:
The next big thing in space may be really, REALLY small satellites

SMX London

23
May
2017
SMX London

10% off with code 7WDATASMX

Read Also:
Will We Soon No Longer Need Data Scientists?

Data Science Congress 2017

5
Jun
2017
Data Science Congress 2017

20% off with code 7wdata_DSC2017

Read Also:
3 Ways Big Data and IoT Can Improve Our Health in 2016

Leave a Reply

Your email address will not be published. Required fields are marked *