Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


09:00 AM
Brad Shimmin
Brad Shimmin
Connect Directly
E-Mail vvv

Why Companies Should Care about Data Privacy Day

Marking yesterday's 14th anniversary of Europe's first data protection day reminds us how far we still have to go.

Enterprisewide leverage of company data is now a near-universal objective for the modern organization, but this must be balanced with the needs of data protection and privacy compliance. The frequency with which breaches of personally identifiable information (PII) hit the headlines makes it clear that too many organizations are failing in their data privacy obligations. Maintaining data privacy is no easy matter; the footprint of information within and beyond an organization's boundaries makes it difficult to get a handle on what data is where. Yet control of the information footprint is essential to provide the appropriate protection.

From an enterprise perspective, there are steps that can be taken to improve data privacy. The overarching recommendation to the enterprise is to work to increase the granular architectural control of data so that it is managed as a cohesive enterprise corpus. This requires a focus on all three elements of the cultural triad: people, process, and technology. Investment in strong IT leadership roles, establishment of processes that incorporate intradepartmental stakeholders, and systematic improvement of architecture via modernization of legacy architecture and careful selection of new technology are all important.

Irrespective of location, any company working with data, most especially those working with customer data, must take action. Organizations operating outside of the European Union cannot afford the luxury of watching data privacy legislation play out from afar, with bodies of legislation continuing to ripple across the entire technology landscape, demanding immediate action regardless of geography or vertical markets. Furthermore, governments do not always wait for legislation, as shown by the $5 billion fine the US Federal Trade Commission (FTC) handed to Facebook in summer 2019 for failing to protect customer data from third parties.

The real risks posed by waiting to implement the measures defined in GDPR, CCPA, and other data privacy legislation begin and end with the customer. Companies must strive to understand and adhere to the spirit of these laws, regardless of potential financial penalties. They must build trust with their customers and partners through constant, tangible efforts such as disclosure of major privacy failings. They must also equip users with knowledge and ownership, namely transparency into process changes that may affect privacy and the means by which users can take control over their own data.

Success will require a lot more than executive approval and adequate assistance from IT culminating in a formal compliance program with well-documented KPIs. Rather, it will require full company participation, support, and most importantly belief in the importance of protecting both company and customer data. Tangibly, this will entail the creation of a publicly visible code of conduct to which all employees pledge adherence. Built on top of a solid compliance program, this statement of intent will serve as a statement of record, a socially binding contract of trust between a company and its customers.

At Ovum, we have created a series of best practices for people, process, and technology to support data privacy and protection.

For people:

  • Fully interview all data stakeholders and any employee working directly on corporate data, building a fully transparent, 360-degree view of that data as it flows into and out of the company.
  • Communicate impactful changes to privacy laws, standards, and regulations in a timely manner, and follow up with specific instructions on any IT-led responses to those changes.
  • Regularly interview the external providers and internal data stakeholders/contributors to ensure that their workflows evolve in accordance with the organization's compliance program.

For process: 

  • Establish a track and trace program for corporate data as it flows throughout internal business software workflows, documenting points of access, modification, and distribution. 
  • Using this track and trace program, seek to operationalize compliance for these potential points of attack or establish firm policies surrounding the establishment of any external partnership (technology providers, contractors, channel partners, suppliers, etc.) that incorporates any data access or exposure.

For technology: 

  • Invest in a data cataloging tool capable of identifying and describing all corporate data assets to drive the creation of the formal data privacy and protection compliance program built on a thorough metadata view of all data resources. 
  • Incorporate data discovery and classification tools alongside data cataloging solutions as a means of automating tasks such as data tagging (necessary for data lineage and traceability), segmentation, and even destruction.
  • Establish control of the data perimeter, preventing the exposure of PII and other controlled information, using solutions emerging from the well-established firewall market.

Each of these suggestions will translate into positive outcomes for enterprise practitioners new to the task of protecting their company's data, the privacy of their users, and the good name of the company itself.

Related Content:

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "7 Steps to IoT Security in 2020."

Distinguished Analyst, Brad Shimmin has more than 25 years of experience in IT technology, helping enterprises and high-tech companies work effectively across a number of market areas including enterprise data and analytics management, artificial intelligence, digital ... View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
User Rank: Ninja
1/30/2020 | 3:34:01 PM
systematic improvement of architecture via modernization of legacy architecture and careful selection of new technology are all important. I think legacy is one of the struggles enterprises have. May not be in compliance with privacy regulations.
User Rank: Ninja
1/30/2020 | 3:31:51 PM
The frequency with which breaches of personally identifiable information (PII) hit the headlines makes it clear that too many organizations are failing in their data privacy obligations. We should expect this would be changing in Europe and US quote soon based on the new laws implemented.
User Rank: Apprentice
1/30/2020 | 1:50:48 AM
Thanks for sharing


<<   <   Page 2 / 2
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
The Problem with Artificial Intelligence in Security
Dr. Leila Powell, Lead Security Data Scientist, Panaseer,  5/26/2020
10 iOS Security Tips to Lock Down Your iPhone
Kelly Sheridan, Staff Editor, Dark Reading,  5/22/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-05-28
An access bypass vulnerability exists when the experimental Workspaces module in Drupal 8 core is enabled. This can be mitigated by disabling the Workspaces module. It does not affect any release other than Drupal 8.7.4.
PUBLISHED: 2020-05-28
In Kaminari before 1.2.1, there is a vulnerability that would allow an attacker to inject arbitrary code into pages with pagination links. This has been fixed in 1.2.1.
PUBLISHED: 2020-05-28
Dell Dock Firmware Update Utilities for Dell Client Consumer and Commercial docking stations contain an Arbitrary File Overwrite vulnerability. The vulnerability is limited to the Dell Dock Firmware Update Utilities during the time window while being executed by an administrator. During this time wi...
PUBLISHED: 2020-05-28
CMS Made Simple through 2.2.14 allows XSS via a crafted File Picker profile name.
PUBLISHED: 2020-05-28
node-dns-sync (npm module dns-sync) through 0.2.0 allows execution of arbitrary commands . This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. This has been fixed in 0.2.1.