Skip to content

GDPR compliance and Article 32 security

The General Data Protection Regulation, Regulation (EU) 2016/679, requires technical and organizational measures appropriate to the risk and a process for testing them regularly (Article 32). Security failures sit behind many of the largest GDPR fines. We implement and test the measures and produce the evidence, while legal advice stays with your counsel and DPO.

Type
Regulation (EU) 2016/679
Applies since
25 May 2018
Security duty
Article 32
Breach notification
Within 72 hours

Who it applies to. Any organization that processes personal data, as a controller or a processor, regardless of size.

  • Controllers

    Companies and institutions that decide why and how personal data is processed, from retail and health to finance and telecoms.

  • Processors

    IT, cloud and other providers that process data for clients. Supervisory authorities fine processors too when their security falls short.

  • Teams that must prove security

    To customers, a data protection officer or the supervisory authority, when they ask for evidence that the measures work.

What it requires of you

What the regulation asks of your security, in four parts.

  • Security of processing (Article 32)

    Technical and organizational measures appropriate to the risk, including encryption, resilience and regular testing.

  • Data protection by design and by default (Article 25)

    Security and data minimization built into systems from the start, not added afterwards.

  • Breach notification (Articles 33 and 34)

    Notify the supervisory authority within 72 hours, and inform data subjects when the risk to them is high.

  • Accountability (Article 5(2))

    Evidence that the measures exist, operate as described and are reviewed regularly.

From requirement to evidence in four steps

We deliver and validate the technical and organizational security measures (Article 32). We do not provide legal advice or act as your data protection officer. We work alongside your DPO and legal counsel.

  1. Security of processing assessment

    We assess the systems that process personal data against Article 32 and the risk, and give you a prioritized remediation plan.

  2. Testing of systems with personal data

    Penetration testing of web applications, APIs, cloud and networks delivers the regular testing Article 32(1)(d) asks for.

  3. Breach readiness

    We set breach criteria, a notification procedure and a report template, rehearse them with your team and help when a real breach happens.

  4. Evidence

    We assemble the reports, policies and records you can show your DPO, customers and the supervisory authority.

GDPR Article 32: security requirements and how we test them

Article 32 lists four groups of measures and asks you to choose them according to the risk.

RequirementWhat it means in practiceHow we verify it
32(1)(a): pseudonymization and encryptionEncryption of databases, disks, backups and data in transit; separating identifiers from the dataReview of encryption and key management in an IT security audit
32(1)(b): confidentiality, integrity, availability and resilienceAccess control, multi-factor authentication, segmentation, patching and monitoringNetwork penetration testing and web application testing
32(1)(c): timely restoration after an incidentBackups kept off the network and a tested recovery procedureA restore test from backups and an incident exercise
32(1)(d): regular testing and evaluationA testing plan and tracking of findings until they are fixedPenetration testing and vulnerability assessment with a retest
32(2): risk assessmentMeasures proportionate to the risk of destruction, loss, alteration, disclosure or accessCyber risk assessment for the systems that process personal data
32(4): processing only on instructionsAccess on a need-to-know basis, instructions and staff trainingAccess review and security awareness training
Requirements of Article 32 GDPR

GDPR technical and organisational measures

GDPR gives no fixed list. These are the measures we most often find missing.

Technical measuresOrganisational measures
Multi-factor authentication for email, VPN and administrationNeed-to-know access and regular review of user accounts
Encryption of devices, databases and backupsRules for handling personal data and removable media
Regular patching and vulnerability assessmentStaff training and phishing simulations
Network segmentation and restricted access to systems with dataContracts with processors under Article 28
Logging and monitoring of access to personal dataA breach procedure with named owners
Backups kept off the network, with tested recoveryA risk assessment and a plan for testing the measures
Examples of technical and organisational measures

The same measures are required by NIS2 and ISO 27001, so it pays to run them as one program with one set of evidence.

GDPR breach notification: the 72-hour rule

Not every security incident is a personal data breach, but every one needs a prompt assessment.

A personal data breach is a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data (Article 4(12)). Typical examples are ransomware, data sent to the wrong recipient, a lost or stolen laptop and unauthorised access to a database.

  1. Establish whether it is a breach

    Check whether personal data was destroyed, lost, altered, disclosed or accessed. Forensics shows which data and systems were affected.

  2. Assess the risk to people

    The type and sensitivity of the data, the number of people, the likely consequences and whether children or other vulnerable groups are involved.

  3. Notify the authority within 72 hours

    Describe the breach, the categories and approximate number of people and records, the likely consequences, the measures taken and a contact point (Article 33(3)). Send what you know and add the rest later.

  4. Inform data subjects if the risk is high

    Without undue delay, in clear language (Article 34).

  5. Document every breach

    The facts, effects, remedial action and the reasoning behind your decision, including breaches you did not notify (Article 33(5)).

Detecting a breach in time is what makes 72 hours possible. Our 24/7 monitoring covers detection, and our incident response team establishes what happened and which data was affected.

Security failures behind GDPR fines

An example from Croatia, based on the fines list published by the supervisory authority AZOP on 16 November 2026.

105

administrative fines published by AZOP since 2020

AZOP

EUR 19.0M

total of all published fines

AZOP

51%

of that amount comes from fines that include an Article 32 breach

Raptoric analysis

7 of 10

largest fines include Article 32, security of processing

Raptoric analysis

The largest Article 32 fines went to a debt collection agency (EUR 5.47 million), another debt collector (EUR 2.27 million), a gambling operator, a district heating company, a telecom operator and a private healthcare provider. AZOP also fined processors, including an IT services company, for missing technical security measures. GDPR allows fines of up to EUR 20 million or 4% of worldwide annual turnover.

Related services

Three services that cover preparation for GDPR.

Frequently asked questions

If your question is not here, ask it on the initial call.

What is GDPR?

GDPR is the General Data Protection Regulation, Regulation (EU) 2016/679, which has applied since 25 May 2018. It sets out how organizations may process personal data and how they must protect it. It applies directly in every member state, supported by national laws and enforced by national supervisory authorities.

Does GDPR apply to my company?

Yes, if you process personal data as a controller or a processor. GDPR has no size threshold, so it covers small companies too. The obligations follow the data rather than the company's location, so they also reach companies outside the EU that offer services to people in the Union.

What are the GDPR security requirements?

Article 32 requires measures appropriate to the risk: pseudonymization and encryption, ongoing confidentiality, integrity, availability and resilience of systems, timely restoration after an incident, and a process for regularly testing and evaluating the measures. People with access to the data may only process it on instructions.

What are technical and organisational measures?

Technical measures include multi-factor authentication, encryption, network segmentation, patching, logging and backups. Organisational measures include access management, policies, staff training, contracts with processors and a breach procedure. GDPR gives no fixed list; it asks for measures proportionate to the risk.

Does GDPR require encryption?

Not in every case. Article 32 names encryption as an example of an appropriate measure, chosen according to the risk. It also pays off after a breach: under Article 34(3)(a), you may not need to inform data subjects if the affected data was unintelligible to unauthorised people, for example because it was encrypted.

Is penetration testing required under GDPR?

GDPR does not name penetration testing, but Article 32(1)(d) requires a process for regularly testing, assessing and evaluating the effectiveness of security measures. A penetration test of systems holding personal data is the most direct way to show that, and the report with a retest becomes accountability evidence.

How do you report a personal data breach within 72 hours?

Notify the supervisory authority without undue delay and within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to people. If you do not have every detail, send what you know and complete it later. If you miss 72 hours, the notification must give the reasons for the delay.

How high are GDPR fines?

GDPR allows fines of up to EUR 20 million or 4% of worldwide annual turnover, whichever is higher. In Croatia, the supervisory authority AZOP has published 105 fines totalling about EUR 19 million since 2020, and fines that include an Article 32 security breach make up about half of that amount.

Do you help with a DPIA?

A data protection impact assessment is required when processing is likely to result in a high risk to people's rights and freedoms (Article 35). We deliver its technical part: threats, vulnerabilities and security measures of the systems. The controller runs the assessment as a whole with advice from the data protection officer.

Do you provide legal or DPO services?

No. We deliver the security side of GDPR: the technical and organizational measures, testing, breach response and the evidence that the measures work. Legal interpretation, records of processing and privacy notices stay with your legal counsel and data protection officer, and we work alongside them.

All articles

Need to prove security of processing?

Tell us what you need to protect. We reply within one business day.

What happens next

  1. Message

    You tell us what you need. We reply within one business day.

  2. Call

    30 minutes about your systems and needs.

  3. Proposal

    Scope, timeline and price within 48 hours.