GDPR in Romania: Article 32 is what draws the fines
The 2026 fines do not come from incomplete registers, they come from inadequate security. What Article 32 asks for, and what to do when a breach happens.
When a company takes on GDPR, it almost always starts with documents: the privacy notice, the register of processing activities, the processor agreements. All necessary. None of them the main reason fines are issued in Romania.
Of the penalties the Romanian supervisory authority made public between March and June 2026, fifteen in total and adding up to roughly 330,000 euro, eleven found a breach of Article 32, the obligation to take appropriate technical and organisational measures. The recorded causes are the least legal ones imaginable: vulnerable applications, weak passwords, lost documents, access granted to an unauthorised person, employee error.
In other words, in Romania GDPR is lost on security ground, not on documentary compliance ground.
What Article 32 requires
Measures appropriate to the risk, taking into account the state of the art and cost. The text gives examples too: pseudonymisation and encryption of data, ensuring confidentiality, integrity, availability and resilience of systems, the ability to restore access to data after an incident, and a process for regularly testing and evaluating the effectiveness of the measures.
The last point is the ignored one. Regularly means with a written trace. A measure nobody can show the last verification date for is, in the authority’s file, an unproven measure.
What counts as appropriate is not a fixed list, and that frightens people more than it should. In practice the authority compares what you did against what would have been reasonable for your risk. A reused password on an admin panel exposed to the internet fails that test anywhere.
What Law 190/2018 adds
The regulation leaves member states room, and Romania used it. Law 190/2018 covers the processing of national identification numbers, the employment context including the conditions under which employee monitoring is permitted, and procedure before the authority.
Workplace monitoring is the part that produces the most surprises, because the conditions are cumulative and include informing employees in advance and a limited retention period. A camera or tracking system switched on without them is a problem even where the purpose is legitimate.
The breach and the 72 hours
A personal data breach is notified to the authority within 72 hours of becoming aware, where it is likely to result in a risk to people’s rights. Where the risk is high, you also inform the data subjects, without undue delay.
If you do not have all the information within 72 hours, you notify with what you have and complete it later. A late notification because the investigation was still running is a separate infringement from the one that caused the breach.
And a breach below the notification threshold still has to be recorded internally. The authority can ask for the register, and an empty register at a company that has had incidents says what it says on its own.
Where it meets everything else
Nearly everything Article 32 asks for is already covered by ISO 27001 controls: access management, cryptography, logging, backups, vulnerability management. And the incident register you keep for NIS2 is the same register the notification to the data protection authority comes out of, with a different clock over it.
In Phalanx, Legal and GDPR groups legal requirements and data processing. Legal requirements link to the controls that cover them, and generated policies can include the relevant national references.