Skip to main content
GDPR · EU data protection

GDPR compliance with Sumrite that you can prove when regulators ask.

Fines of up to 4% of turnover and a 72-hour breach clock put GDPR on the board agenda. Sumrite tests the systems that hold personal data and documents fixes so you can evidence Article 32 measures.

7
data protection principles in Article 5
6
lawful bases for processing personal data
72 h
to notify the regulator of a notifiable personal data breach, where feasible
4%
of worldwide turnover or €20M, the higher maximum tier of fines
The detail

What the GDPR actually is

The General Data Protection Regulation is a European Union law that sets rules for collecting, using and storing personal data. It applies when you operate in the EU, or when you offer goods or services to people in the EU or monitor their behaviour, even if your company is elsewhere.

It is built on seven principles: lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality; and accountability. Every processing activity needs one of six lawful bases, such as consent, contract or legitimate interests.

Security is an explicit duty. Article 32 requires “appropriate technical and organisational measures” and names, among other things, a process for regularly testing and evaluating their effectiveness. Penetration testing is one common way to show that.

Key terms in plain English

Controller
The organisation that decides why and how personal data is processed.
Processor
A company that processes personal data on a controller’s behalf, bound by a data processing agreement.
Data subject
The person the personal data is about.
DPIA
Data Protection Impact Assessment: a structured review required when processing is likely to be high risk.
Requirements

The duties that matter most

The regulation is long. These are the areas where security and engineering teams are asked to show evidence most often.

Art. 5

Article 5: the seven principles

Everything else hangs from the principles. Collect only what you need, keep it accurate, delete it when you no longer need it, and keep it secure. Accountability means you must be able to show you comply, not just claim it.

What it looks like in practice

  • A record of why each data set is collected
  • Retention periods that are actually enforced
  • Evidence of security controls and testing
Art. 6

Article 6: pick and document a lawful basis

Consent, contract, legal obligation, vital interests, public task and legitimate interests are the six bases. Choose the one that really fits and record it. Consent must be freely given, specific, informed and withdrawable.

What it looks like in practice

  • A processing register naming the basis per activity
  • Consent logs where consent is used
  • A legitimate interests assessment where relied on
Art. 12–22

Articles 12 to 22: rights of individuals

People can ask for access, correction, deletion, restriction, portability and objection. You normally have one month to respond. Systems need to find and export or delete one person’s data reliably.

What it looks like in practice

  • A request intake and tracking process
  • Ability to locate data across systems and backups
  • Identity checks that do not leak data to impostors
Art. 25–32

Articles 25 and 32: privacy by design and security of processing

Build protection in from the start and keep it effective. Article 32 lists measures such as pseudonymisation, encryption, resilience, restoring availability and regularly testing effectiveness.

What it looks like in practice

  • Encryption in transit and at rest
  • Access control with least privilege
  • Regular penetration tests and fixes tracked to closure
Art. 33–34

Articles 33 and 34: breach notification

If a breach is likely to put people’s rights at risk, notify the supervisory authority within 72 hours of becoming aware, where feasible. If the risk is high, tell the affected individuals as well. Keep an internal record of every breach.

What it looks like in practice

  • An incident response plan with a clock
  • A breach register, including non-notified incidents
  • Pre-agreed roles for legal, security and communications
Fit

Who needs to think about GDPR

SaaS and online services

If EU residents use your product, you almost certainly process their personal data.

HR, recruiting and employers

Employee and candidate data is personal data and carries strict handling duties.

Marketing and analytics teams

Tracking, profiling and email marketing rely on a clear lawful basis and honest notices.

Processors and vendors

If you handle data for EU customers, contracts and security evidence are expected.

Board and leadership view

Why GDPR matters to your board

The work is technical. The consequences of getting GDPR wrong show up in revenue, liability and reputation, which is why we report on it in the language of the boardroom first.

EU revenue and contracts

EU customers expect proof that personal data is protected. Weak evidence slows enterprise sales and renewals.

Fines and liability

Fines reach 4% of worldwide turnover or EUR 20M, and leaders are expected to show appropriate measures.

Reputation after a breach

Notification to authorities and individuals is public. Tested safeguards lower the chance of that event.

The 72-hour clock

Decisions on notification must be quick. Pre-agreed owners and tested systems prevent improvisation.

How it works

A practical GDPR readiness path

Timelines are typical ranges, not promises. Yours depends on scope, team size and how much is already in place.

  1. 1

    Map your data

    Weeks 1 to 3

    List what personal data you hold, where it flows, who receives it and why. This becomes your record of processing.

  2. 2

    Set lawful bases and notices

    Weeks 3 to 5

    Choose and document a basis for each activity and make privacy notices match reality.

  3. 3

    Handle rights requests

    Weeks 4 to 8

    Create a process and tooling to respond to access and deletion requests within one month.

  4. 4

    Secure and test

    Months 2 to 3

    Apply Article 32 measures and run a penetration test on systems that hold personal data.

  5. 5

    Contract with processors

    Months 2 to 4

    Sign data processing agreements and review each vendor’s security evidence.

  6. 6

    Rehearse a breach

    Month 4

    Run a tabletop exercise so the 72-hour decision is not made for the first time in a real incident.

VAPT

Where VAPT comes in under GDPR

GDPR never says “penetration test” but Article 32(1)(d) calls for a process for regularly testing, assessing and evaluating the effectiveness of security measures. A scoped, expert-led test is one of the clearest ways to evidence it.

Art. 32(1)(d)

Regular testing and evaluation

Documents that you test technical measures and act on the results. Retest reports show findings were fixed.

Art. 32(1)(b)

Confidentiality and integrity

Testing shows whether access control and data protections actually hold against a determined attacker.

Art. 25

Data protection by design

Testing new features before release helps catch privacy-impacting weaknesses early.

Art. 28

Processor assurance

Customers reviewing you as a processor will often ask for recent independent test summaries.

Avoid these

Common GDPR mistakes, and how to avoid them

!

Treating consent as the only basis

Consent is only one of six. Using it where it is not freely given can make processing unlawful.

!

No tested breach plan

The 72-hour window leaves little time to improvise. Decide roles and thresholds ahead of time.

!

Unmanaged processors

You remain accountable for vendors you use. Keep contracts and security evidence up to date.

!

Keeping data forever

Without enforced retention, old data becomes a liability the moment you are breached.

Why Sumrite

Why teams choose Sumrite for GDPR

GDPR is a team effort between your people, your auditor and your customers. We take the weight off all three.

One team, start to finish

From the first question about GDPR to the final report, you deal with one accountable team and one timeline.

250+ clients cleared through audits

We have taken more than 250 clients through SOC 2 and similar audits, so we know what reviewers ask for and what they accept.

Plain English, not jargon

We explain what GDPR means for your business, your roadmap and your customers before any technical work starts.

Evidence that stands up

Everything we produce is organised so your auditor, customer or regulator can follow it quickly.

Scope of work

What Sumrite delivers for GDPR

One accountable team takes you from scoping to retest. The people who test your systems are the people who explain the findings to your leadership.

Gap analysis

Technical and organisational measures compared with Articles 25 and 32 for systems holding personal data.

Penetration testing

Expert-led testing of applications, APIs and infrastructure that process personal data.

Control validation

Checks that access control, encryption and logging work as described in your records.

Evidence pack

Dated test reports and fix records you can show a regulator or a processor review.

Remediation support and retest

Fix guidance for engineers, then a retest confirming closure.

Board-ready report

Personal data risk and progress in language leadership can act on.

Fixed scope, one team, no hand-offsYou get a named lead, a clear scope document before work starts and a report your leadership, customers and reviewers can read without a translator. We stay with you through your review to answer questions about what we tested and found.
Deliverables

What your leadership team receives

Every engagement ends with material written for two audiences: a plain-language view for executives and the board, and full technical detail for the engineers who fix things.

  • An executive summary

    Where personal data is exposed and what to fix first.

  • Article 32 testing evidence

    Dated reports and retest letters supporting regular testing.

  • A remediation tracker

    Every finding with an owner, severity and status.

  • Customer-ready summaries

    Test summaries suited to processor reviews and security questionnaires.

  • Support through reviews

    The same Sumrite team stays with you through customer and audit questions.

FAQ

GDPR questions, answered

Does GDPR apply to companies outside the EU?

Yes, when you offer goods or services to people in the EU or monitor their behaviour in the EU, even if you have no office there.

Is a penetration test required by GDPR?

Not by name. Article 32 requires appropriate security and a process for regularly testing it. Penetration testing is a widely accepted way to meet that expectation.

What counts as a notifiable breach?

A personal data breach that is likely to result in a risk to people’s rights and freedoms. Regulators expect you to assess and record every incident, even ones you do not report.

What are the maximum GDPR fines?

Up to €20 million or 4% of worldwide annual turnover for the most serious infringements, and up to €10 million or 2% for others. Actual fines depend on the case.

Do we need a Data Protection Officer?

Only in certain cases, such as public bodies or large-scale regular monitoring or sensitive data processing. It depends on your activities and scale.

See all FAQs →

Ready to get GDPR sorted?

Tell us your scope, your deadline and who is asking. You get a fixed-scope quote and a named lead from day one.

Get a Quote →