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.

Operational Security //


// // //
09:35 AM
Paige Bartley
Paige Bartley
News Analysis-Security Now

GDPR Compliance: Enterprises Have Two Options to Consider

When it comes to preparing for GDPR, enterprises, as well as vendors, are relying on two different approaches. The first focuses on technology, while the second relies on internal processes and workflows.

A sizable proportion of organizations will not be fully compliant with the European Union's General Data Protection Regulation by the time the May 2018 deadline passes, and demand for compliance tools is growing.

Technology vendors, eager to carve out a piece of this burgeoning market, are offering a diverse swath of solutions that tackle various aspects of the broad regulation. However, two primary approaches are emerging in the solution market: those that depend more on technology and those that depend more on existing organizational processes and workflows.

The better approach is a matter of debate, but GDPR's framework suggests that technology in isolation -- without respect to underlying people and processes -- is unlikely to provide sustainable results. The most successful GDPR compliance solutions are likely those that are able to successfully combine aspects of both technology and human process, helping operationalize data control and compliance workflows within the organization. (See GDPR Non-Compliance: Will Your Enterprise Get Busted?)

GDPR's technology-agnostic framework underscores process
As a rule, GDPR is technology-agnostic. Aside from a few references to standard security measures such as encryption and high availability of systems, the regulation makes scant mention of specific technology.

(Source: iStock)
(Source: iStock)

There is good reason for this: Technology evolves much more quickly than regulatory and legal frameworks. If the regulation were to endorse or depend on the viability of specific technologies, it would quickly become obsolescent and unable to adequately fulfill its role of protecting the information and rights of data subjects.

Nevertheless, technology will be a critical component to fulfilling GDPR's requirements.

After all, the regulation pertains to the protection of data, and data is stored and processed in technology-based systems. Solutions that aim to fulfill the technical requirements of the regulation need to be based on technology and/or directly interface with existing IT systems.

However, GDPR itself is more concerned with the repeatable governance processes and frameworks that exist within organizations; for all the regulation's technical requirements, such as security of data, right to erasure, right to data portability and data protection by design and by default, there are many more articles of the regulation that focus on the human process. (See GDPR Blackmail Looms as a Double-Dip Cyber Attack Plan.)

Data protection impact assessments (DPIAs), prior consultation and communication of data breaches to data subjects and supervisory authorities are all examples of requirements that necessitate repeatable, documentable processes driven by established human roles and responsibilities.

Technology cannot replace that.

In reality, compliance with GDPR requires two major components: direct technical control of data assets and the existence and documentation of repeatable human processes.

Neither can exist in isolation. While this may seem like a distinction between "hard" and "soft" requirements, software solutions provide technical means for achieving both needs. The solutions' approaches, however, are often divergent.

Two camps emerge
Given this mix of needs, the landscape of vendors offering GDPR-related solutions is largely evolving into two camps: those that take a technology-based approach and those that take a process-based approach.

Both methodologies depend on software to typically provide a centralized interface for task management and human interaction with data, but they tend to differ in their objectives and execution.

While broad generalizations are not entirely useful, as some products use an overlapping approach, the general distinction is as follows:

    • A technology-based approach depends on technology-based mechanisms to meet specific technical requirements, such as the encryption of data. Automation of data handling and data manipulation is common. These solutions are likely to assign rigid roles to product users, and typically come with their own preconfigured workflows and templates. Direct technical control of data assets is often the primary objective.


  • A process-based approach largely relies on existing roles, workflows and processes within the enterprise, with technology as a facilitator rather than as the primary mechanism. Manual handling of data, such as assignment of policies to data, is often required. These solutions are likely to offer flexible, customizable workflows and are likely to adopt existing roles within the enterprise rather than imposing their own within the product. Documentation and recordkeeping of processes, instead of direct data control, is often the primary objective.


Neither approach is right nor wrong; a technology-based solution may excel at automatically applying policies -- such as masking -- to data that has been identified as personal, whereas a process-based solution would be far better suited to Article 35's requirements for repeatedly conducting DPIAs. (See GDPR Territorial Scope: Location, Location, Location?)

Given that the regulation is so broad and encompasses a mix of technical and process requirements, an organization would benefit from using a mix of solutions that are either technology-based or process-based, depending on which articles of the regulation are being addressed.

However, technology vendors take note: Process is overrepresented in the GDPR's framework. For any compliance solution to be successful in the enterprise, it needs to piggyback off of existing human processes and roles.

Otherwise, it is likely to become siloed and underused. A solution that is striving to help achieve compliance with the broadest possible number of articles from the regulation will take advantage of both technology and human processes, utilizing each for their respective strengths.

Technology excels at automation, scale and consistency. But processes have the benefit of adaptability, human adherence and the ability to become rooted in enterprise culture.

Next page: Utilizing an Enterprise's Strengths

1 of 2
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
The 10 Most Impactful Types of Vulnerabilities for Enterprises Today
Managing system vulnerabilities is one of the old est - and most frustrating - security challenges that enterprise defenders face. Every software application and hardware device ships with intrinsic flaws - flaws that, if critical enough, attackers can exploit from anywhere in the world. It's crucial that defenders take stock of what areas of the tech stack have the most emerging, and critical, vulnerabilities they must manage. It's not just zero day vulnerabilities. Consider that CISA's Known Exploited Vulnerabilities (KEV) catalog lists vulnerabilitlies in widely used applications that are "actively exploited," and most of them are flaws that were discovered several years ago and have been fixed. There are also emerging vulnerabilities in 5G networks, cloud infrastructure, Edge applications, and firmwares to consider.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2023-03-17
The Bookly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the full name value in versions up to, and including, 21.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that w...
PUBLISHED: 2023-03-17
The WP Express Checkout plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘pec_coupon[code]’ parameter in versions up to, and including, 2.2.8 due to insufficient input sanitization and output escaping. This makes it possible for authenti...
PUBLISHED: 2023-03-17
A vulnerability was found in SourceCodester Student Study Center Desk Management System 1.0. It has been rated as critical. This issue affects the function view_student of the file admin/?page=students/view_student. The manipulation of the argument id with the input 3' AND (SELECT 2100 FROM (SELECT(...
PUBLISHED: 2023-03-17
A vulnerability classified as critical has been found in SourceCodester Student Study Center Desk Management System 1.0. Affected is an unknown function of the file Master.php?f=delete_img of the component POST Parameter Handler. The manipulation of the argument path with the input C%3A%2Ffoo.txt le...
PUBLISHED: 2023-03-17
A vulnerability classified as critical was found in SourceCodester Student Study Center Desk Management System 1.0. Affected by this vulnerability is an unknown functionality of the file admin/?page=reports&date_from=2023-02-17&date_to=2023-03-17 of the component Report Handler. The manipula...