GDPR Compliance Guide: Requirements, Checklist, and More

Tags:
  • Compliance & Regulations

The General Data Protection Regulation (GDPR) is a pivotal framework that governs data protection and privacy for individuals within the European Union (EU). Its implications are far-reaching, affecting organizations worldwide that handle EU citizens' data. Understanding and achieving GDPR compliance is essential to avoid substantial penalties and to maintain trust with customers.

General Data Protection Regulation (GDPR) compliance

GDPR compliance entails adhering to the regulations set forth by the law, which aim to protect personal data and uphold the privacy rights of individuals. Personal data is defined as any information which is related to an identified or identifiable natural person. For other definitions, read our breakdown of key GDPR terms.

Organizations must implement appropriate technical and organizational measures to ensure data security, transparency, and accountability in their data processing activities.

Who is subject to GPDR?

Entities that either control or process personal data should be GDPR compliant.

A data controller is any natural or legal person, public authority, agency, or other body that determines the purposes and means of the processing of personal data. In essence, they decide the "why" and "how" data is processed. For example, a healthcare provider that collects patient data on a certain system of their choosing.

A data processor is any natural or legal person, public authority, agency, or other body which processes personal data on behalf of the controller; this means they don’t make decisions about how that data is handled. For example, a payroll company that processes employee salary and tax information for a company (the data controller) based on their instructions.

Although processors operate under the instructions of controllers, they must still comply with GDPR requirements when handling personal data. Read more about how controllers can manage cyber risk from their data processors.

Keys to achieving GDPR compliance requirements

The GDPR establishes stringent principles around lawfulness, fairness, and transparency that organizations must follow, including:

  • Lawful Processing: Data must be processed lawfully, fairly, and transparently.
  • Data Minimization: Only data necessary for the specified purpose should be collected.
  • Accuracy: Data must be accurate and kept up to date.
  • Storage Limitation: Data should be retained only as long as necessary.
  • Integrity and Confidentiality: Data must be processed securely to prevent unauthorized access.

GDPR compliance checklist

Achieving and maintaining GDPR compliance requires a systematic approach to managing personal data, protecting individual rights, and addressing security risks. The checklist below organizes 11 essential compliance activities into four categories: Data governance, organizational accountability, security and third-party risk, and ongoing compliance monitoring. Use the checkboxes to track progress against each requirement.

Data governance and processing

DoneAction itemGDPR reference
Map and document personal data collection, processing, storage, and deletion activitiesArticles 5, 30
Identify and document the lawful basis for each personal data processing activityArticle 6
Develop transparent privacy notices, consent mechanisms where applicable, and data protection policiesArticles 7, 12–14
Implement mechanisms that allow individuals to exercise their GDPR rights, including access, rectification, erasure, and objection to processing. Establish procedures to receive, verify, track, and respond to requests within required timeframes.Articles 12–21

Organizational accountability

DoneAction itemGDPR reference
Provide employees with regular GDPR and data protection trainingArticles 24, 39; best practice
Appoint a Data Protection Officer (DPO) if required and document their responsibilitiesArticles 37–39
Conduct Data Protection Impact Assessments (DPIAs) for processing likely to result in high riskArticle 35

Security and third-party risk

DoneAction itemGDPR reference
Implement appropriate technical and organizational safeguards, including encryption, access controls, and security assessmentsArticle 32
Identify third-party processors, establish appropriate data processing agreements, and review their security practices. Continuously monitor your vendors to assure ongoing compliance.Articles 28, 32

Ongoing monitoring and incident response

DoneAction itemGDPR reference
Conduct regular compliance reviews and audits, document gaps, and track corrective actionsArticles 24, 32; best practice
Establish and test data breach response procedures, including documentation and notification processesArticles 33–34

The GDPR references identify relevant legal provisions. Training, audits, and continuous third-party monitoring are practical compliance measures; their frequency and implementation depend on the organization's processing activities and risks. Completing the checklist alone does not establish GDPR compliance.

GDPR compliance across the globe

While GDPR is an EU regulation, its reach extends globally. Any organization, regardless of location, that processes the personal data of EU residents must comply with GDPR. This extraterritorial scope means that businesses worldwide need to be aware of and adhere to GDPR requirements.

U.S. companies that handle EU citizens' data are subject to GDPR too. This includes e-commerce sites, service providers, and any business offering goods or services to EU residents. Non-compliance can result in significant fines and legal challenges.

Cookies that collect personal data are subject to GDPR. Organizations must obtain explicit consent from users before placing such cookies on their devices. This involves providing clear information about the cookies' purposes and ensuring users can opt in or out easily. Regular reviews of cookie practices are essential to maintain compliance.

GDPR and CCPA compliance

The California Consumer Privacy Act (CCPA) shares similarities with GDPR, but has distinct requirements. Organizations operating in both jurisdictions must navigate these differences to ensure compliance with both laws. This may involve implementing separate processes for data access requests and understanding the specific definitions and rights under each regulation.

Risk of non-compliance with GDPR

Intentional infringement, a failure to take measures to mitigate damage, or lack of collaboration with authorities can be the cause for penalties. For especially severe violations, listed in Art. 83(5), the fine framework can be up to €20 million, or in the case of an undertaking, up to 4% of the company’s total global turnover of the preceding fiscal year, whichever is higher. Beyond financial repercussions, organizations may suffer reputational damage, loss of customer trust, and legal actions. Therefore, adhering to GDPR is not only a legal obligation but also a critical component of responsible business practice.

GDPR compliance is a comprehensive and ongoing process that requires diligence, transparency, and a commitment to data protection principles. By following the guidelines outlined above, organizations can navigate the complexities of GDPR and build a robust framework for data privacy and security.

cisos guide to reporting to the board cta learn

Security is under the spotlight—and CISOs are expected to perform. This guide helps you report with precision, connect metrics to risk and resilience, and give executives what they need to lead with confidence.

GDPR compliance guide FAQs

Is double opt-in required for GDPR?

No, double opt-in is not explicitly required under the General Data Protection Regulation (GDPR). However, it can be a recommended practice to help demonstrate valid, informed consent—especially in email marketing. GDPR requires that consent be freely given, specific, informed, and unambiguous. While a single opt-in process can meet these criteria, double opt-in provides an added layer of verification that helps organizations document and prove that consent was obtained properly.

What is a requirement for controllers under the GDPR?

Under the GDPR, data controllers are required to implement appropriate technical and organizational measures to ensure and demonstrate that data processing is compliant with the regulation. This includes maintaining records of processing activities, ensuring transparency with data subjects, enabling rights like access and erasure, and working with processors that offer sufficient guarantees of GDPR compliance. Controllers must also notify supervisory authorities of data breaches within 72 hours, where feasible.

What level of encryption is required for GDPR?

The GDPR does not mandate a specific encryption algorithm or level, but it does require that organizations implement "appropriate technical and organizational measures" to protect personal data. Encryption is explicitly mentioned as a recommended safeguard. The chosen level of encryption should reflect the sensitivity of the data, potential risks, and the state of the art in data protection. Common standards include AES-256 for data at rest and TLS 1.2 or higher for data in transit.

Is SSL required for GDPR?

SSL (Secure Sockets Layer) is outdated and has been replaced by TLS (Transport Layer Security), which is the industry standard for encrypting data in transit. While the GDPR doesn’t explicitly require SSL or TLS by name, it does require appropriate security measures for protecting personal data during transmission. Using TLS is considered a best practice and is often necessary to meet GDPR's expectations for safeguarding data in transit over networks.

Does GDPR require consent for third-party cookies?

Yes, under the GDPR—particularly when interpreted alongside the ePrivacy Directive—organizations must obtain explicit, informed consent before placing or accessing most third-party cookies on a user's device. This includes cookies used for advertising, tracking, or analytics. Consent must be given before the cookies are set, and users should have a clear, easy way to refuse or withdraw consent at any time.

What are the reporting requirements for data breaches under GDPR?

Under the GDPR, organizations must report personal data breaches to the relevant supervisory authority within 72 hours of becoming aware of the breach—unless the breach is unlikely to result in a risk to the rights and freedoms of individuals. If the risk is high, affected individuals must also be informed without undue delay. The report should include details such as the nature of the breach, the categories and number of data subjects affected, likely consequences, and measures taken or proposed to address the breach.