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/27/2018
09:35 AM
Dawn Kawamoto
Dawn Kawamoto
Dawn Kawamoto
50%
50%

4 Steps to Make Your Website GDPR Compliant

Three months remain to whip your website into shape before the May 25 GDPR compliance deadline. Here are several steps to help you get there.

Websites operated by mom-and-pop businesses to large corporate titans face a looming deadline to comply with the European Union's General Data Protection Regulation (GDPR) if they collect, store or distribute personally identifiable information of EU citizens.

While a number of US-based companies may believe the EU's GDPR requirement does not apply to them -- think again, and fast. The deadline to adhere to the regulation is May 25 and may come with steep fines for non-compliance.

And what is the purpose of the GDPR as it relates to websites?

"It's all about transparency of communication regarding how the website and company will use the data in question and making sure that they clearly state what the rights of the individual are relating to accessing, objecting, and ultimately, removing the data that has been collected by the organization," Rick Hemsley, managing director of Accenture Security, told Security Now.

Common missteps in GDPR website compliance
Although the GDPR compliance deadline has not hit, the Data Privacy Act of 1998 serves as a yardstick in terms of common missteps companies may encounter in trying to comply with the GDPR, Hemsley said.

(Source: iStock)
(Source: iStock)

"It is likely that most organizations will stumble on their ability to provide access to data and their ability to delete it either when legitimately asked to by the customer or when it falls out of retention," he explains.

Another challenging area for companies includes the way that they communicate clearly with customers regarding their privacy policies. Under the GDPR, the information is required to be clear and designed for the average lay person to understand, rather than written in "legalese," Hemsley added.

Companies will need to learn to strike a balance between clear and concise privacy policy language and legally protecting themselves.

GDPR website compliance steps
Under GDPR, there are several key steps website operators need to take to be compliant with the regulations, Enza Iannopollo, a security and risk analyst for Forrester, told Security Now.

Here are the four steps businesses should take:

  • First step: Review and identify all the personal customer information that you and your third-party partners collect and store on your website and distribute. For example, what information are you collecting and are you and your third-party partners asking permission to collect this information?
  • Second step: Understand what processes are needed to be built into the way your customer uses your website and the risks they may pose. Iannopollo strongly suggests website operators think about the "journey" customers take as they enter and move about and through the website. "Think about the customer and when does it make sense to ask them for their permissions, keeping in mind you need their permission before you collect the data you are seeking," Iannopollo says. And she noted that some websites are addressing the disclosure issue by providing links that allow a user to drill down into as much information as they are seeking about a company's privacy policy, rather than having pages upon pages of information for them to wade through on the site.
  • Third step:Talk to your attorneys to help identify the risks and ensure your processes comply with GDPR, as well as work with your tech team to build the needed safeguards to collect the data, evaluate it and remove it.
  • Fourth step: Remove personally identifiable information after its intended and customer-approved use. This step can be accomplished by either deleting the information or masking it, so it is anonymous but can still be used for aggregation purposes. "Data is not only an asset, but it is also a liability," Iannopollo said.

Hemsley agrees with Iannopollo on that assessment about data and further adds:

GDPR presents a real opportunity for organizations to drive data efficiencies throughout their organization. Organizations will be shedding data that they don't need, don't have a right to hold, and ultimately, costs them money to store. By removing unnecessary data, organizations not only increase operational and processing efficiency, but they save money, and, if they get it right, engender greater trust with their customer base which can be translated into more profitable and active customers.

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
Oldest First  |  Newest 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
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-33988
PUBLISHED: 2021-10-19
Cross Site Scripting (XSS). vulnerability exists in Microweber CMS 1.2.7 via the Login form, which could let a malicious user execute Javascript by Inserting code in the request form.
CVE-2020-12141
PUBLISHED: 2021-10-19
An out-of-bounds read in the SNMP stack in Contiki-NG 4.4 and earlier allows an attacker to cause a denial of service and potentially disclose information via crafted SNMP packets to snmp_ber_decode_string_len_buffer in os/net/app-layer/snmp/snmp-ber.c.
CVE-2021-29912
PUBLISHED: 2021-10-19
IBM Security Risk Manager on CP4S 1.7.0.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 207828.
CVE-2021-38911
PUBLISHED: 2021-10-19
IBM Security Risk Manager on CP4S 1.7.0.0 stores user credentials in plain clear text which can be read by a an authenticatedl privileged user. IBM X-Force ID: 209940.
CVE-2021-3746
PUBLISHED: 2021-10-19
A flaw was found in the libtpms code that may cause access beyond the boundary of internal buffers. The vulnerability is triggered by specially-crafted TPM2 command packets that then trigger the issue when the state of the TPM2's volatile state is written. The highest threat from this vulnerability ...