hello@sterling-grc.com +1 201 263 4443 New York ISO & GRC consulting in 60+ countries
SterlingInternational Consulting Talk to a consultantTalk to us
← All videos

Two-minute brief

GDPR requirements explained: video brief

A two-minute brief on the GDPR obligations that shape a compliance programme, from the Article 5 principles to breach notification and transfers.

  • Two-minute brief
  • 2 min

Key takeaways

  • Article 5 accountability means being able to demonstrate compliance, not only to achieve it.
  • Every processing activity needs one of six lawful bases.
  • Data subject requests are answered within one month, free of charge in principle.
  • Notifiable breaches go to the supervisory authority within 72 hours.
  • Transfers outside the EU need a recognised transfer mechanism.

The obligations that shape a GDPR programme

The Regulation runs to 99 articles in eleven chapters, but the obligations that shape a programme sit in a handful of them. This short film brings them together. Article 5 sets the principles: personal data processed lawfully, fairly and transparently, for specified purposes, minimised, accurate, kept no longer than necessary and secure, with the controller able to demonstrate it. In practice that means a data inventory with purpose, retention and security per activity, and a file of the decisions behind each one.

Articles 6, 7 and 9 require one of the six lawful bases for every activity, proof of consent where consent is used, consent as easy to withdraw as to give, and an Article 9 condition before processing special-category data such as health or biometric data. Articles 12 to 22 cover transparency and the rights of access, rectification, erasure, restriction, portability and objection, with requests answered within one month and limits on solely automated decisions.

Accountability, breaches and transfers

The controller and processor duties require measures that prove processing follows the Regulation, processor contracts and records of processing activities. Personal data breaches must be managed, and notifiable breaches reported to the supervisory authority within 72 hours of becoming aware of them. Transfers of personal data outside the EU are restricted and need a recognised mechanism.

Scope depends on where you are established and whom you serve, not where your servers sit. In the United Kingdom, the UK GDPR applies alongside the Data Protection Act 2018. No certification exists for the GDPR as such: compliance is assessed by regulators and customers' auditors, and legal interpretation stays with your legal advisers.

A working programme therefore combines decisions, such as why each activity is lawful, documents such as records, notices and contracts, and controls that are actually in use, each with evidence an auditor can follow.

GDPR at a glance

Purpose
Data protection: personal data processed lawfully, transparently and securely, the rights of the people it concerns honoured, and the evidence to prove it
Relevant to
Any organisation established in the EU or EEA, and any organisation elsewhere that offers goods or services to people in the EU or monitors their behaviour, as controller or processor
Edition
Regulation (EU) 2016/679, in application since 25 May 2018; in the United Kingdom the UK GDPR applies alongside the Data Protection Act 2018, as amended by the Data (Use and Access) Act 2025
Certification
None exists for the GDPR as such. Compliance is assessed by regulators and your customers' auditors; voluntary Article 42 seals are few and never reduce your own responsibility
Sterling's role
Programme design and consulting with your team, Effivity, training, internal audit and review readiness, then Sustain™
Cost and timing
Total investment for a GDPR compliance programme depends on the current maturity of your processes, the scope, locations and number of employees. The process typically takes 3 to 8 months

GDPR: the complete guide →

GDPR: questions people ask

Is there such a thing as GDPR certification?

Not in the way ISO certification exists. Article 42 allows voluntary certification, issued by bodies accredited under Article 43 against criteria approved by a supervisory authority or the European Data Protection Board; the Board's register lists only a handful of approved mechanisms, Europrivacy among them, and Article 42(4) says certification does not reduce the controller's or processor's responsibility. A "GDPR certificate" from outside that register is a badge, not a certification.

Does ISO/IEC 27701 or ISO/IEC 27001 make us GDPR compliant?

No standard does. ISO/IEC 27701 is a certifiable privacy management system standard that maps closely to the GDPR's obligations, and ISO/IEC 27001 evidences the security Article 32 asks for; both are strong evidence of a managed programme. Neither is an Article 42 certification, and neither replaces the legal analysis of your lawful bases, notices, contracts and transfers.

We are outside the EU. Does the GDPR really apply to us?

If you offer goods or services to people in the EU, paid or free, or monitor their behaviour there, Article 3(2) applies wherever you are, and Article 27 usually requires a representative in the Union. If you process personal data for an EU client as a processor, your obligations arrive through the Regulation and the Article 28 contract the client must sign with you.

Do we need a data protection officer?

Article 37 requires one for public bodies, for organisations whose core activities involve regular and systematic monitoring of individuals on a large scale, and for those whose core activities involve large-scale processing of special-category or criminal-conviction data. Others appoint one voluntarily. Either way, document the decision; the DPO may be an employee or a contractor, acts independently and reports to top management.

What has to happen within 72 hours of a breach?

Article 33 requires the controller to notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a breach, unless it is unlikely to result in a risk to individuals; a late notification must explain the delay. Where the risk is high, Article 34 requires affected people to be told without undue delay. Processors notify their controllers, and every breach, reported or not, goes in the register.

More GDPR questions and answers →

Talk to a consultant

Plan your GDPR compliance with confidence.

Tell us your goals, locations and target date. We’ll help you define the scope, timeline and next steps.

hello@sterling-grc.com

+1 201 263 4443 (global headquarters) · your nearest office and its number are at the top of this page

What would you like to achieve?

Choose a starting point. The enquiry form takes about a minute.

Your goal
Book my free discovery call

Continue to the enquiry form to share your details. Please do not include passwords, sensitive personal information or confidential files. A Sterling consultant replies within one working day. Privacy notice