What security requirements does the GDPR have?

A
admin

Oct 28, 2022

  • 3 min Read
  • Shares
What security requirements does the GDPR have?
This article is part of our GDPR compliance certification hub page, where we explain how GDPR supports stronger data protection and privacy compliance. This blog focuses on the security requirements under GDPR, including the need for appropriate technical and organizational measures to protect personal data from unauthorized access, accidental loss, misuse, or data breaches.

Personal data must be “processed in a manner that ensures appropriate security of the personal data, including protection against unauthorized or unlawful processing and against accidental loss, destruction, or damage, using appropriate technical or organisational measures,” according to Article 5.1(f) of the GDPR. In essence, this is the security premise of the Regulation. The security of processing is governed by Article 32. Examples of suitable organisational and technical measures include:

  • encryption and pseudonymization of personal data
  • the capacity to maintain processing systems’ and services’ continued confidentiality, integrity, availability, and resilience
  • the capability of recovering data accessibility and availability in the case of a physical or technological mishap
  • a procedure for routinely examining, evaluating, and testing the efficacy of organisational and technical security measures.
Data controllers and processors must consider the risks associated with processing when deciding which security measures to put in place. A risk assessment or DPIA (data protection impact assessment) will help you choose the right security measures. Even when the risk is originally viewed as low, doing DPIAs is a useful practise because your evaluation may disclose risks you had not thought of. 
The GDPR includes six data processing principles as opposed to the eight data protection principles of the Data Protection Act of 1998. Personal information must be:
  1. “Lawfulness, fairness, and transparency” refers to how data is processed in regard to the data subject.
  2. Collected for specific, clear, and legal purposes and not further processed in a way that is inconsistent with those purposes pursuant to Article 89(1), further processing for public interest archiving, scientific or historical research, or statistical purposes shall not be deemed to be inconsistent with the initial purposes (the “purpose limitation”)
  3. Adequate, pertinent, and strictly limited to what is required in light of the processing’s goals (data minimization)
  4. Accurate and, where necessary, kept current every effort must be made to ensure that personal data that is incorrect, taking into account the purposes for which it is processed, is immediately deleted or corrected
  5. Personal data may be stored for longer periods if they are processed solely for archiving in the public interest, scientific or historical research purposes, or statistical purposes in accordance with Article 89(1), subject to implementation of the necessary technical and organisational measures. Personal data must be kept in a form that makes it possible to identify data subjects for no longer than is necessary for the purposes for which they are processed.
  6. Processed in a way that guarantees adequate security of the personal data, including protection against unauthorized or unlawful processing and against unintentional loss, destruction, or damage (referred to as “integrity and confidentiality”), using appropriate technical or organisational methods.

Other Blogs

Previous
Next
ISO/IEC 27701:2025 Transition: What Organizations Need to Know Blog

ISO/IEC 27701:2025 Transition: What Organizations Need to Know

ISO/IEC 27701 has entered a new phase. Published on 14 October 2025, ISO/IEC 27701:2025 replaces…

Read More
PCI KMO Standard v1.0: What It Means for Payment Security Blog

PCI KMO Standard v1.0: What It Means for Payment Security

Learn what PCI KMO Standard v1.0 covers, who it affects, how it supports PIN and…

Read More
Firewall Ruleset Review: What Your Rules Are Really Allowing Blog

Firewall Ruleset Review: What Your Rules Are Really Allowing

Every firewall does exactly what its rules tell it to do - nothing more. A…

Read More
CEA Cyber Security Regulations 2026: Compliance Guide Blog

CEA Cyber Security Regulations 2026: Compliance Guide

The Central Electricity Authority (Cyber Security in Power Sector) Regulations, 2026 create an auditable cyber…

Read More
Incident Response Planning for Regulated Entities in India Blog

Incident Response Planning for Regulated Entities in India

Every regulated entity has an incident response plan. It sits in a policy document, usually…

Read More
AI Governance and Compliance in Indian Financial Services Blog

AI Governance and Compliance in Indian Financial Services

Indian banks, NBFCs, and insurance companies are deploying AI across credit scoring, fraud detection, customer…

Read More
FAQ: Cloud Compliance Questions From Fintech CTOs Blog

FAQ: Cloud Compliance Questions From Fintech CTOs

Any cloud provider with data center regions in India - AWS (Mumbai and Hyderabad), Azure…

Read More
RBI Cybersecurity Directions 2026: A Complete Compliance Guide Blog

RBI Cybersecurity Directions 2026: A Complete Compliance Guide

RBI's approach to cybersecurity regulation has evolved from advisory circulars to mandatory directions. The regulatory…

Read More

Ready to become compliant?

Talk to QRC to understand your scope, close gaps, and move confidently
toward validation readiness.