SaaS and online services
If EU residents use your product, you almost certainly process their personal data.
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.
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.
The regulation is long. These are the areas where security and engineering teams are asked to show evidence most often.
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.
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.
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.
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.
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.
If EU residents use your product, you almost certainly process their personal data.
Employee and candidate data is personal data and carries strict handling duties.
Tracking, profiling and email marketing rely on a clear lawful basis and honest notices.
If you handle data for EU customers, contracts and security evidence are expected.
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 customers expect proof that personal data is protected. Weak evidence slows enterprise sales and renewals.
Fines reach 4% of worldwide turnover or EUR 20M, and leaders are expected to show appropriate measures.
Notification to authorities and individuals is public. Tested safeguards lower the chance of that event.
Decisions on notification must be quick. Pre-agreed owners and tested systems prevent improvisation.
Timelines are typical ranges, not promises. Yours depends on scope, team size and how much is already in place.
List what personal data you hold, where it flows, who receives it and why. This becomes your record of processing.
Choose and document a basis for each activity and make privacy notices match reality.
Create a process and tooling to respond to access and deletion requests within one month.
Apply Article 32 measures and run a penetration test on systems that hold personal data.
Sign data processing agreements and review each vendor’s security evidence.
Run a tabletop exercise so the 72-hour decision is not made for the first time in a real incident.
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.
Documents that you test technical measures and act on the results. Retest reports show findings were fixed.
Testing shows whether access control and data protections actually hold against a determined attacker.
Testing new features before release helps catch privacy-impacting weaknesses early.
Customers reviewing you as a processor will often ask for recent independent test summaries.
Consent is only one of six. Using it where it is not freely given can make processing unlawful.
The 72-hour window leaves little time to improvise. Decide roles and thresholds ahead of time.
You remain accountable for vendors you use. Keep contracts and security evidence up to date.
Without enforced retention, old data becomes a liability the moment you are breached.
GDPR is a team effort between your people, your auditor and your customers. We take the weight off all three.
From the first question about GDPR to the final report, you deal with one accountable team and one timeline.
We have taken more than 250 clients through SOC 2 and similar audits, so we know what reviewers ask for and what they accept.
We explain what GDPR means for your business, your roadmap and your customers before any technical work starts.
Everything we produce is organised so your auditor, customer or regulator can follow it quickly.
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.
Technical and organisational measures compared with Articles 25 and 32 for systems holding personal data.
Expert-led testing of applications, APIs and infrastructure that process personal data.
Checks that access control, encryption and logging work as described in your records.
Dated test reports and fix records you can show a regulator or a processor review.
Fix guidance for engineers, then a retest confirming closure.
Personal data risk and progress in language leadership can act on.
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.
Where personal data is exposed and what to fix first.
Dated reports and retest letters supporting regular testing.
Every finding with an owner, severity and status.
Test summaries suited to processor reviews and security questionnaires.
The same Sumrite team stays with you through customer and audit questions.
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.
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.
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.
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.
Only in certain cases, such as public bodies or large-scale regular monitoring or sensitive data processing. It depends on your activities and scale.
Browse all 23 security and compliance frameworks or see our penetration testing services.
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 →