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 //

Compliance

// // //
2/9/2018
08:05 AM
Dawn Kawamoto
Dawn Kawamoto
News Analysis-Security Now

GDPR Readiness Goes Beyond Security Controls

IT security and privacy professionals face challenges in designing a comprehensive compliance program to meet the upcoming GDPR regulations that the EU is implementing, a Forrester Research report finds.

Psst… stop staring into the tool bag and look around you.

IT security and privacy pros who are tasked with helping their companies come into compliance with the European Union's General Data Protection Regulation (GDPR) would be better served rounding up a cross-section of co-workers and executives than throwing all efforts toward buying more IT products, a recent Forrester Research report found.

Although security controls, such as encryption, tokenization and the use of network security tools, are a top priority for a number of organizations seeking to achieve GDPR compliance, Forrester finds these strategies rely too heavily on IT for answers.

For many InfoSec pros, however, that is their comfort zone and may contribute to the challenges they may face in GDPR compliance.

"We know that GDPR investments usually come from IT budgets … but encryption is really the only security control that is called out specifically in the GDPR," Enza Iannopollo, an analyst on Forrester's Security & Risk team and co-author of the report, told Security Now.

(Source: Pixabay)
(Source: Pixabay)

Because of these heavy IT investments, as well as an approach by security and privacy pros to tackle GDPR requirements individually, companies are missing out on developing a meaningful comprehensive compliance program, she notes.

"They need to approach this as privacy-by-design," Iannopollo said. "You need to bring people together from across the organization to collaborate on ways to protect the information."

This means adopting processes and procedures to allow the continuous collaboration from DevOps teams to business units, from data scientists to security and privacy peers, the report notes.

Without a privacy-by-design process, problems in meeting and maintaining GDPR compliance may result, Iannopollo warns.

Problems without processes in place
"The roadblock that I come across the most is the ability of companies to identify and manage risk," Iannopollo said, pointing to a lack of executive ownership in the GDPR compliance process and the vacuum it creates in tackling the problem.

Customer notification after a breach is another problem area that may arise without a process in place.

Although a majority of organizations feel prepared to notify the data protection authorities within 72 hours after a breach, as required under the GDPR, companies are neglecting to train and test their ability to notify customers within the same timeframe as required by the GDPR, Forrester cites in its report.

Security and privacy pros also need to shift their mindset from satisfying individual GDPR requirements to developing a process of creating, executing and documenting a comprehensive GDPR compliance strategy, according to Forrester.

This is imperative given GDPR regulators have the ability to potentially audit firms on a continuous basis, which means a comprehensive and continuous GDPR compliance strategy is needed, Iannopollo notes.

Is your company GDPR ready?
The report found nearly 30% of the 3,752 survey respondents from around the globe believed their organization was fully GDPR compliant.

However, Forrester notes that based on its own research, most companies are taking a "piecemeal" approach and meeting only specific compliance requirements, such as encryption or data breach notification, and considering themselves in full compliance.

(Source: Forrester)
(Source: Forrester)

The survey also found some industries are further along in GDPR compliance than others. Highly regulated fields, such as the financial services industry, tend to have established teams of compliance and data protection workers, as well as data protection officers (DPO) on board.

The retail and media industries, meanwhile, are just now beginning to ramp up their GDPR compliance efforts, Forrester reports, despite both sectors possessing a treasure trove of customers' personal data.

Creating a comprehensive GDPR compliance framework
The report points to three areas that companies should consider when developing their compliance framework:

  • Execute GDPR programs across systems, processes, people and governance.
  • Involve all appropriate teams from day one.
  • Invest in compliance management solutions to support continuous GDPR compliance.

"GDPR is a cross-functional effort," Iannopollo said.

Related posts:

— Dawn Kawamoto is an award-winning technology and business journalist, whose work has appeared in CNET's News.com, Dark Reading, TheStreet.com, AOL's DailyFinance and The Motley Fool.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
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
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
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
Video
Cartoon
Current Issue
Everything You Need to Know About DNS Attacks
It's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask. Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted. Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-33196
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
CVE-2023-33185
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
CVE-2023-33187
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `ty...
CVE-2023-33194
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn’t fix it when clicking save. This issue was...
CVE-2023-2879
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file