GDPR and managed cybersecurity: 10 technical controls to prove
Without documented technical measures, a data breach turns from an IT incident into a problem with the regulator. Ten controls in three blocks: know, protect and prove.
What does the law require of infrastructure, without the legalese?
Regulation (EU) 2016/679 does not impose brands or products. It asks for security proportionate to risk. Article 32(1) lists examples: pseudonymisation and encryption; ongoing confidentiality, integrity, availability and resilience; timely restoration of…
01GDPR Article 32 requires encryption, access control, data recovery and regular testing.
02A breach is normally notified to the authority within 72 hours; it is always documented.
03Your IT provider is usually a processor, and the contract must comply with Article 28.
04DataRoad implements and documents the technical controls; it does not give legal advice.
In this article
A personal data breach without documented technical measures turns an IT incident into a problem with the data protection authority, with clients and with the company's reputation. For infrastructure, GDPR translates into ten controls within reach of any organisation above 10 workstations, to implement and, above all, to demonstrate. Here, DataRoad - IT Services and Consulting organises them into three blocks (know, protect, prove) and explains the first 72 hours after a breach. The legal side (lawful bases, consent, data subjects' rights) is left out; it belongs to your lawyer or data protection officer.
GDPR and managed cybersecurity: what do you need to know now?
Article 32 Requires effective technical security: encryption, confidentiality, data recovery and regular evaluation.
72 hours The standard deadline for notifying the CNPD (the Portuguese data protection authority), counted from the moment the company becomes aware, using the dedicated form.
Record everything Every breach is documented, including those that are never notified.
Article 28 Whoever provides your IT services and accesses your data is, as a rule, a processor; the contract must comply with this article.
What does the law require of infrastructure, without the legalese?
Regulation (EU) 2016/679 does not impose brands or products. It asks for security proportionate to risk. Article 32(1) lists examples: pseudonymisation and encryption; ongoing confidentiality, integrity, availability and resilience; timely restoration of access to data after an incident; and regular testing of the effectiveness of the measures.
In management terms, four guarantees: access only for those who need it, controlled changes, recovery in good time and periodic verification. And personal data is anything that identifies a person: name, email, tax number, address, client file, payslip.
Block 1, Know where the data is and who touches it
Personal data inventory: go through the server, Microsoft 365, billing, external drives, HR software and old mailboxes. Result: a table with the type of data, the system and the owner.
Least privilege: permissions defined by role: sales does not see salaries, reception cannot access the management folder. Every change of role triggers a fresh review.
Contracts with those who process data for you: IT provider, cloud, payroll. Article 28 requires sufficient guarantees and a written contract setting out instructions, confidentiality, security, conditions for using sub-processors, cooperation in a breach and return or destruction of data at the end. See what to check in exit and data clauses in an IT contract.
Block 2, Protect against loss, theft and attack
Multi-factor authentication: a large share of intrusions start with a compromised password. The second factor, usually on a phone, must protect email, cloud and remote access.
Encryption: one of the two measures named in Article 32 itself: encrypted disks on laptops, managed and locked phones, encrypted backups.
Updates with a set deadline: unpatched systems are the most common way to lose integrity and resilience. Set installation deadlines and retire equipment the manufacturer no longer supports.
Backups that are actually restored: without a tested restore, a backup is just a hypothesis. We recommend at least one test per quarter: see the 30-minute restore test and our managed backup service.
Block 3, Prove due diligence when someone asks
Access logs: sign-ins, access to sensitive folders, permission changes. In an incident, these records are what let you tell the authority which data was affected.
A plan for the first 72 hours: who decides, who gathers the technical information, who completes the notification. All agreed before it is needed.
A written annual review: the most forgotten Article 32 requirement. One review a year, with fixes recorded, is the best proof that the company acted diligently.
What should you do in the 72 hours after a breach?
Article 33 and the CNPD's guidance set notification within 72 hours of becoming aware, unless the breach poses no risk to data subjects' rights. Where the risk is high, Article 34 also requires informing the data subjects themselves.
When
What
Who
Detection
Technical alert, complaint, ransom demand or missing laptop
Establish which data and how many data subjects are involved
IT and management
By day 3
Decide and, if required, submit the form to the CNPD
The company, as data controller
In every case
Record the breach, its consequences and the measures taken
The company
Two details catch many companies by surprise. Documenting is mandatory even when there is no notification. And the processor, IT provider included, must alert the client without undue delay. A lost laptop without encryption may constitute a breach; with an encrypted disk, the risk assessment is different.
Real example: continuity at a public body
Under a public contract with the União de Freguesias de Massamá e Monte Abraão, DataRoad installed and configured a new server, fitted a UPS (batteries that keep equipment running when the power fails), implemented local and cloud backups and migrated data and configurations. That is availability exactly as Article 32 describes it: data stored in more than one place and recoverable. Find out about the Massamá and Monte Abraão project.
How does DataRoad's managed cybersecurity help?
We implement and document the technical controls, access, encryption, backups, updates, logs, firewall. We do not give legal advice. In 11 years, DataRoad has never suffered a security incident.
Do we have to encrypt all data to comply with GDPR?
Encrypting everything is not mandatory, but encryption is expressly named as an appropriate measure. On backups, phones and laptops it is the simplest way to stop a loss becoming a serious breach.
Does a lost laptop have to be reported to the authority?
Only if there is a risk to the data subjects. If the disk is encrypted and wiped remotely, that risk falls sharply. The incident is always recorded, and the decision rests with the data controller, with legal support where needed.
Does our IT partner count as a processor?
Yes, in most cases, provided it accesses systems containing personal data. The contract must then comply with Article 28: instructions, confidentiality, security, cooperation in incidents and return or destruction of data.
What is the deadline for notifying a breach?
As a rule, 72 hours from when the company becomes aware, using the form provided by the CNPD. If that deadline is missed, the notification must explain the delay.
In 10 working days we assess the ten controls across your systems and leave you, in writing, the gaps and the order in which to close them. Request a no-commitment proposal.