How to Prepare for a Data Breach Under GDPR

The European Union’s General Data Protection Regulation (GDPR) came into effect last month with a mighty thud. This wide-ranging law requires businesses to protect the personal data and privacy of EU citizens for transactions that occur within the European Union.

GDPR applies to all companies operating in Europe and all companies with a website or app that captures and processes the data of EU citizens. The complexity of GDPR is breathtaking. It consists of 99 articles that detail the rights of individuals and the obligations of companies.

Corporate failure to comply with the law can result in substantial fines: up to €20 million or 4 percent of a company’s global revenue, whichever is higher. Two pain points stand out: a requirement to notify EU authorities within 72 hours of a breach, and another to prove the company’s security approach is state-of-the-art.

Most U.S. Companies are Not Ready

A slew of reports indicate that most U.S. companies are woefully unprepared for GDPR. A recent survey by Spiceworks reveals that only 25 percent of U.S. companies were compliant with the tough new law when it was enacted on May 25.

The findings also show that most U.S. companies are not concerned about potential GDPR penalties, and, as a result, many are failing to make compliance a priority. However, about 20 percent of U.S. respondents said the law will make it more difficult for their company to do business.

GDPR emphasizes transparency, security and accountability for data controllers. It introduces mandatory data protection impact assessments (DPIAs) for companies involved in high-risk processing. Examples of “high-risk” are companies that deploy new technologies, engage in activities involving significant profiling of individuals or do large-scale monitoring of a public area.

The law mandates that data processors:

  • Establish formalized incident response procedures.

  • Create an internal breach notification process.

  • Communicate a personal data breach to the data subject without delay.

  • Notify the supervisory authority within 72 hours of a breach.

  • Be compliant or face fines.

5 Steps to Take Now

To prepare for a data breach under GDPR companies should implement the following immediately.

Start with Compliance

This involves working the legal department and/or an external auditing firm to assess whether the company is compliant with GDPR. Both data “controllers,” who determine how and why personal data is processed, and data “processors,” who act on behalf of controllers, must comply with GDPR.

Establish GDPR Playbooks

To gather evidence about a data breach and document it, companies need a streamlined process. Incident response and case management playbooks provide a predefined set of procedures, processes and workflows in the event of a breach.

Create GDPR Workflows

Customized workflows are required to respond swiftly to various incident types. They can prioritize tasks, assign duties to specific stakeholders, and formalize, enforce and measure specific response steps. Centralizing these on a single platform for collaboration is recommended.

Establish Reporting Capabilities

To satisfy data breach reporting and notification within GDPR’s 72-hour the time frame, the ability to gather, anonymize and share data from various sources is essential. Put in place automated procedures for preparing detailed reports based on incident and forensic data—and set up mechanisms to quickly send breach notifications to affected customers.

Be Able to Meet the 72-hour Notification Mandate

This is arguably one of GDPR’s toughest requirement. It imposes a three-day deadline to detect and contain a breach and fully report on the details while following strict protocols, including documenting the events and making sure the proper incident response and case management procedures have been followed. Routine assessments should be conducted to ensure the necessary processes and procedures are in place and stakeholders are trained and understand their responsibilities.

Data breach detection and response is never easy, under any circumstances. GDPR has significantly raised the stakes by requiring more detailed documentation and an extremely short notification window. Preparation and planning today is the surest way to avoid the hefty fines and public scrutiny that’s in store for organizations that fail to comply with GDPR.

Featured eBook
Automating Open Source Security: A SANS Product Review of WhiteSource

Automating Open Source Security: A SANS Product Review of WhiteSource

Many sources indicate that 60–80 percent of code in applications today is based on open source components. This open source code often includes vulnerabilities that, if not managed properly, can expose organizations to potential breaches. This paper takes a close look at how WhiteSource can automate the process of open source component vulnerability detection, remediation, ... Read More
WhiteSource
John Moran

John Moran

John Moran is Senior Product Manager at DFLabs (https://dflabs.com) and an expert in security operations, incident response, digital forensics and investigations. He has served as a Senior Incident Response Analyst for NTT Security, Computer Forensic Analyst for the Maine State Police Computer Crimes Unit and Task Force Officer for the US Department of Homeland Security. John currently holds GCFA, CFCE, EnCE, CEH, and CHFI certifications as well as degrees in Digital Forensics and Information Security.

john-moran has 1 posts and counting.See all posts by john-moran