Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
GDPR is the data protection law that governs how organisations collect, use, store, and secure personal data; in Britain it applies as the UK GDPR alongside the Data Protection Act 2018.

What Is GDPR?
The General Data Protection Regulation (GDPR) is the European law that sets out how personal data must be collected, used, shared, and protected. It has applied across the EU since 25 May 2018. After Brexit, the UK kept its substance in domestic law as the UK GDPR, which works alongside the Data Protection Act 2018 and is enforced by the Information Commissioner’s Office (ICO).
For security teams, GDPR matters because it turns information security into a legal duty. Article 32 requires “appropriate technical and organisational measures”, and a breach can lead to regulatory action, compensation claims, and lasting reputational harm.
The UK GDPR applies to any organisation that processes personal data of people in the UK, whether it is a large bank, a charity, or a small online shop. It also reaches organisations outside the UK that offer goods or services to people in the UK or monitor their behaviour. The EU GDPR works the same way for people in the EU, so many UK businesses must comply with both.
The law distinguishes between controllers, who decide why and how data is processed, and processors, who process data on a controller’s behalf. A cloud host or a managed SOC provider is typically a processor and must be bound by a contract that meets Article 28.
Article 5 sets out the principles that every processing activity must meet:
The sixth principle is where cybersecurity sits, but accountability is what auditors and the ICO will ask you to prove: records of processing, policies, data protection impact assessments, and evidence that controls actually work.
People have the right to be informed, to access their data (a subject access request, normally answered within one month), to rectification, to erasure, to restrict processing, to data portability, to object, and rights related to automated decision-making. Security teams often support these requests, because finding every copy of someone’s data across email, file shares, and SaaS platforms is as much a discovery problem as a legal one.
UK GDPR does not prescribe specific products. It expects measures proportionate to the risk, and names examples such as pseudonymisation, encryption, resilience, backup and restoration, and regular testing of security controls. The ICO also points to Cyber Essentials as a sensible baseline.
When a personal data breach occurs, the controller must:
Meeting the 72-hour window depends on preparation. Without logging, an incident response plan, and access to forensic expertise, many organisations cannot even tell within three days whether personal data left their network.
Under the UK GDPR, the higher maximum fine is £17.5 million or 4% of annual worldwide turnover, whichever is greater, with a lower tier of £8.7 million or 2%. In October 2020 the ICO fined British Airways £20 million over its 2018 breach, in which attackers skimmed payment card data from its website, and Marriott International £18.4 million over the compromise of the Starwood guest reservation database. In both cases the ICO criticised weaknesses in security measures rather than the attacks alone. Beyond fines, the ICO can issue reprimands and enforcement notices, including orders to stop processing.
The Data (Use and Access) Act 2025 amends the UK GDPR, the Data Protection Act 2018, and PECR, with changes such as recognised legitimate interests, revised rules on automated decision-making, and higher fines for PECR breaches. Its provisions are being brought into force in stages, so check the ICO’s current guidance before relying on a specific change.
A workable programme starts with a data map: what personal data you hold, where it lives, who can reach it, and which suppliers process it. From there, prioritise controls around the highest-risk data, test them regularly, and keep the evidence. Our regulation and compliance services help organisations turn GDPR security obligations into measurable controls.
They started as almost identical texts, and the core principles, rights, and security duties are the same. The UK version is enforced by the ICO, uses sterling fine limits, and is now diverging gradually through the Data (Use and Access) Act 2025. Organisations operating in both markets usually build one programme that meets the stricter requirement wherever the two differ.
No. You must report a personal data breach within 72 hours unless it is unlikely to result in a risk to people’s rights and freedoms. A misdirected email containing a single colleague’s name might not need reporting, whereas leaked customer records or health data almost certainly would. Every breach must still be documented internally, along with your reasoning.
GDPR does not name penetration testing, but Article 32 requires a process for regularly testing, assessing, and evaluating the effectiveness of security measures. Penetration tests and vulnerability scanning are the most common ways to meet that duty and produce evidence for accountability. The ICO’s security guidance explicitly lists regular testing among the measures it expects to see.
You must appoint one if you are a public authority, if your core activities involve large-scale regular and systematic monitoring of individuals, or if you process special category or criminal offence data on a large scale. Many other organisations appoint a DPO voluntarily or assign a privacy lead, because someone still needs to own compliance.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.