Who it applies to
The Regulation applies to the processing of personal data wholly or partly by automated means, and to non-automated processing of personal data that form part of, or are intended to form part of, a filing system (Article 2(1)). Under Article 3(1) it applies to processing in the context of the activities of an establishment of a controller or processor in the Union, wherever the processing takes place. Article 3(2) extends it to controllers and processors outside the Union in defined cases, including offering goods or services to people in the Union (Article 3(2)(a)).
The Regulation separates controllers, which determine the purposes and means of processing (Article 4(7)), from processors, which process personal data on their behalf (Article 4(8)). A security firm can hold either role, depending on who decides what the processing is for. This page is written for organisations commissioning a test and for providers that may access personal data while testing.
Sources: Regulation (EU) 2016/679, Articles 2 and 3 (Official Journal); Regulation (EU) 2016/679, Article 4 (Official Journal)
Key dates
| Date | What happens | Source |
|---|---|---|
| Applies from (Article 99(2)) | Regulation (EU) 2016/679, Article 99 (Official Journal) |
What does GDPR Article 32 require for security testing?
Article 32 applies to controllers and processors, and asks for a level of security appropriate to the risk. Its examples are pseudonymisation and encryption of personal data (Article 32(1)(a)); “the ongoing confidentiality, integrity, availability and resilience” of processing systems and services (Article 32(1)(b)); restoring access “in a timely manner” after an incident (Article 32(1)(c)); and “a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing” (Article 32(1)(d)).
Three phrases in Article 32(1)(d) do the work. “Regularly” means the process repeats; the article sets no frequency. “Effectiveness” means checking that a measure works, not only that it exists. “A process” means findings must feed back into fixes. Penetration testing is not named, and no particular test is mandatory. It is a common way to evidence this element, especially when the test is scoped in writing, findings are tracked to remediation and fixes are checked.
Article 32(2) requires that, in assessing the appropriate level of security, account is taken in particular of the risks presented by processing, such as unauthorised disclosure of, or access to, personal data.
What is the GDPR 72-hour breach rule?
Article 33(1) requires notification to the supervisory authority “without undue delay and, where feasible, not later than 72 hours after having become aware of it”, unless the breach is “unlikely to result in a risk to the rights and freedoms of natural persons”. A late notice must give reasons for the delay.
A processor must notify the controller “without undue delay after becoming aware of a personal data breach” (Article 33(2)). Article 33(3) sets the content of the notice, and Article 33(5) requires every breach to be documented, with its facts, effects and remedial action.
Article 34(1) requires the controller to tell affected people “without undue delay” where a breach is likely to result in a high risk to them. Article 34(3) lists exceptions: where protection measures applied to the affected data render it unintelligible to anyone not authorised to access it, such as encryption; where later measures ensure the high risk is no longer likely to materialise; and where individual notice would involve disproportionate effort, in which case a public communication or similar measure must inform people in an equally effective manner.
Whether an event is a breach, and whether it is notifiable, is the controller’s judgement, and a penetration test does not make it. If a test shows personal data being read by someone who should not read it, tell the controller quickly and record the facts. The EDPB’s Guidelines 9/2022 (version 2.0) address how these terms apply; they are guidance, not law. Infringements of the obligations in Articles 32 to 34 fall under Article 83(4)(a): administrative fines up to EUR 10 000 000 or, in the case of an undertaking, up to 2% of the total worldwide annual turnover of the preceding financial year, whichever is higher.
How do Articles 5, 24, 25 and 30 apply to a security team?
Article 5(1)(f) requires appropriate security against unauthorised or unlawful processing and against accidental loss, destruction or damage. Article 5(2) makes the controller responsible for compliance with Article 5(1) and able to demonstrate it. Test reports are one part of that evidence.
Article 24(1) asks for measures to ensure, and to demonstrate, compliance. Article 25(1) asks for measures “designed to implement data-protection principles, such as data minimisation”, and Article 25(2) requires that, by default, only personal data necessary for each specific purpose are processed. Decisions on test data, staging copies and log retention are design decisions, and they are best written down before a test starts. The EDPB’s Guidelines 4/2019 (version 2.0) explain Article 25 further; they are guidance, not law.
Article 30(1) requires controllers to keep a record of processing activities, and Article 30(2) requires processors to record the categories of processing they carry out on behalf of each controller. Infringements of the basic principles in Article 5 fall under Article 83(5)(a): administrative fines up to EUR 20 000 000 or, in the case of an undertaking, up to 4% of the total worldwide annual turnover of the preceding financial year, whichever is higher.
Do processors and penetration testers need a DPA and a DPIA?
Article 4(7) defines the controller as the body that “determines the purposes and means of the processing of personal data”. Article 4(8) defines a processor as a body that “processes personal data on behalf of the controller”. A provider that processes your personal data on your behalf, to run a test you ordered, falls within that definition for that data. Check that the contract matches the facts.
Article 28(3) requires processing by a processor to be governed by a contract or other legal act setting out the subject-matter, duration, nature and purpose, the types of personal data and categories of data subjects, and the controller’s rights and obligations. The processor must take the Article 32 measures (Article 28(3)(c)), assist with Articles 32 to 36 (Article 28(3)(f)), and make available the information needed to demonstrate compliance and allow audits, including inspections (Article 28(3)(h)). AssurePort acts as processor for customer scan data under its Data Processing Addendum; read the current version there. Customer data is stored in the EU; AI analysis is performed by Anthropic in the United States, a sub-processor listed in the DPA.
Article 35(1) requires an assessment of the impact of processing before it begins, where the processing is “likely to result in a high risk to the rights and freedoms of natural persons”. Article 35(3) names three cases where a DPIA is specifically required, and security testing is not among them. Whether a DPIA is needed for a test is the controller’s assessment.
How to run a penetration test when the target holds personal data
Settle the roles and the lawful basis first. The controller decides why a test happens and chooses the lawful basis under Article 6(1). Legitimate interests is one basis a controller may consider. Article 6(1)(f) applies only where processing is “necessary for the purposes of the legitimate interests pursued by the controller or by a third party”, except where those interests are “overridden by the interests or fundamental rights and freedoms of the data subject”.
Confirm authority. AssurePort starts a scan only for a domain-verified asset, or after you give an explicit legal-authority attestation that you own the target or have written permission to test it. Your written scope should name the hosts, accounts and data the tester may use, and say what happens if personal data outside that scope turns up.
Minimise what the test touches. Article 5(1)(c) limits personal data to what is “necessary in relation to the purposes for which they are processed”. A proof needs to show a flaw, not collect a dataset: a count, a masked value or one non-sensitive record can often show an injection or access-control flaw. In practice:
- use test accounts and synthetic records where the application allows;
- stop each proof at the least personal data that shows the flaw;
- agree in writing where evidence is stored, who can see it and when it is deleted.
Where production data cannot be protected, use a staging copy; production testing carries availability risk, which Article 32(1)(b) asks you to consider.
Know the engine’s limits. On the read-only engines, the runner checks each command against a list of known write and destructive operations before it runs. On Web and API, stopping at proof of concept is an agent instruction, not a hard technical block, so test against a target you can restore.
Treat the report as personal data (Articles 5(1)(c) and 32). Redact personal data from requests, responses and screenshots unless the finding needs it, and keep the request that reproduces a flaw rather than copies of the records it returned. The Trust Center states that AssurePort redacts secrets such as API keys and passwords from saved findings and masks email addresses harvested by the OSINT engine; other personal data is not removed automatically, so read the report before you share it.
Plan for the unexpected. If a test exposes personal data you did not expect, the controller decides promptly whether it is a personal data breach under Article 33; if it is, Article 33(5) requires it to be documented. Agree the route to the controller before testing starts. Retention for account and scan data is set out in the privacy policy.
Three free checks are not a test: the Security Headers Grader, the cookie flags check and the email authentication checker read public responses and DNS records in a single passive look. They can flag configuration points before you commission a test. For how AssurePort’s own scans work, see the penetration testing page.
Obligations and where testing can contribute evidence
| Reference | What the text requires | Where a penetration test can contribute evidence |
|---|---|---|
| Art. 5(1)(c) | Data minimisation Personal data must be adequate, relevant and limited to what is necessary for the purposes for which it is processed. In testing, this governs how much personal data a proof touches. Source: Regulation (EU) 2016/679, Article 5 (Official Journal) | A report can show which data a finding required the tester to touch, which supports minimisation during testing; it cannot show that the controller’s processing as a whole is minimised. |
| Art. 5(1)(f) | Integrity and confidentiality Personal data must be processed with appropriate security, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage. Source: Regulation (EU) 2016/679, Article 5 (Official Journal) | A test can show whether an external attacker can reach or change personal data through a specific weakness; it does not show that the wider protection is appropriate. |
| Art. 5(2) | Accountability The controller is responsible for complying with Article 5(1) and must be able to demonstrate that it does. Source: Regulation (EU) 2016/679, Article 5 (Official Journal) | Outside what a test can evidence. |
| Art. 24(1) | Controller responsibility Taking account of the risks, the controller must implement appropriate measures to ensure, and to be able to demonstrate, that processing is performed in accordance with the Regulation. Source: Regulation (EU) 2016/679, Article 24 (Official Journal) | Outside what a test can evidence. |
| Art. 25(1)–(2) | Data protection by design and by default Controllers must build data-protection principles such as minimisation into processing, at the design stage and during use. By default, only personal data necessary for each specific purpose may be processed (Art. 25(2)). Source: Regulation (EU) 2016/679, Article 25 (Official Journal) | A test can show that a deployed control fails in a specific case; it cannot show that the design process was followed. |
| Art. 28(3) | Contract between controller and processor Processing by a processor must be governed by a contract or other legal act setting out the subject-matter and duration, the nature and purpose, the types of personal data and categories of data subjects, and the obligations and rights of the controller. Source: Regulation (EU) 2016/679, Article 28 (Official Journal) | Outside what a test can evidence. |
| Art. 28(3)(c) | Security measures in the contract The processor must take all measures required under Article 32. Source: Regulation (EU) 2016/679, Article 28 (Official Journal) | Outside what a test can evidence. |
| Art. 28(3)(f) | Assistance with Articles 32 to 36 The processor assists the controller in ensuring compliance with its duties under Articles 32 to 36, taking into account the nature of the processing and the information available to the processor. Source: Regulation (EU) 2016/679, Article 28 (Official Journal) | Outside what a test can evidence. |
| Art. 28(3)(h) | Information and audits The processor makes available the information needed to demonstrate compliance with the obligations in Article 28, and allows for and contributes to audits, including inspections, by the controller or another auditor mandated by the controller. Source: Regulation (EU) 2016/679, Article 28 (Official Journal) | A test report and its method can be part of the information a processor provides; a report does not replace the audit right. |
| Art. 30(1)–(2) | Records of processing activities Controllers keep a record of processing activities under their responsibility. Processors keep a record of the categories of processing carried out on behalf of each controller (Art. 30(2)). Source: Regulation (EU) 2016/679, Article 30 (Official Journal) | Outside what a test can evidence. |
| Art. 32(1)(a) | Pseudonymisation and encryption Among the measures the article lists: pseudonymisation and encryption of personal data. Source: Regulation (EU) 2016/679, Article 32 (Official Journal) | A test can check whether personal data is sent in clear text or over weak transport encryption, and whether the encryption in place matches what is documented. |
| Art. 32(1)(b) | Confidentiality, integrity, availability and resilience The ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services. Source: Regulation (EU) 2016/679, Article 32 (Official Journal) | A test can show that an access control failed in a specific case, or that a flaw could disrupt a service; it cannot establish resilience in general. |
| Art. 32(1)(c) | Restoring availability and access The ability to restore availability of, and access to, personal data in a timely manner after a physical or technical incident. Source: Regulation (EU) 2016/679, Article 32 (Official Journal) | Outside what a test can evidence. |
| Art. 32(1)(d) | Regular testing, assessment and evaluation A process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing. The article sets no frequency and does not name penetration testing. Source: Regulation (EU) 2016/679, Article 32 (Official Journal) | A penetration test is one common way to produce evidence for this element when it is repeated, scoped in writing, and followed by remediation and a check that the fixes hold. |
| Art. 32(2) | Risk-based level of security In assessing the appropriate level of security, account must be taken in particular of the risks of accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to personal data. Source: Regulation (EU) 2016/679, Article 32 (Official Journal) | Test findings can feed the risk assessment; they do not replace it. |
| Art. 33(1) | Notification to the supervisory authority The controller notifies the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware of a personal data breach, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. A notice not made within 72 hours must give reasons for the delay. Source: Regulation (EU) 2016/679, Article 33 (Official Journal) | Outside what a test can evidence. |
| Art. 33(2) | Processor notifies the controller A processor must notify the controller without undue delay after becoming aware of a personal data breach. Source: Regulation (EU) 2016/679, Article 33 (Official Journal) | A test that exposes personal data needs a defined route to the controller; whether the exposure is a breach is the controller’s assessment. |
| Art. 33(3) | Content of the notification The notice describes the nature of the breach, including where possible the categories and approximate numbers of people and records affected; gives a contact point; and describes the likely consequences and the measures taken or proposed. Source: Regulation (EU) 2016/679, Article 33 (Official Journal) | Outside what a test can evidence. |
| Art. 33(5) | Breach documentation The controller documents every personal data breach, including its facts, effects and remedial action, so that the supervisory authority can verify compliance with Article 33. Source: Regulation (EU) 2016/679, Article 33 (Official Journal) | Outside what a test can evidence. |
| Art. 34(1) | Communication to data subjects Where a breach is likely to result in a high risk to the rights and freedoms of natural persons, the controller tells the affected individuals without undue delay, in clear and plain language (Art. 34(2)). Source: Regulation (EU) 2016/679, Article 34 (Official Journal) | Outside what a test can evidence. |
| Art. 34(3) | Exceptions to individual notice Individual notice is not required where protection measures applied to the affected data render it unintelligible to anyone not authorised to access it (for example encryption), where later measures ensure the high risk is no longer likely to materialise, or where it would involve disproportionate effort; in that last case a public communication or similar measure must inform people in an equally effective manner. Source: Regulation (EU) 2016/679, Article 34 (Official Journal) | Outside what a test can evidence. |
| Art. 35(1) | Data protection impact assessment Before processing that is likely to result in a high risk to the rights and freedoms of natural persons, the controller assesses the impact of the processing on the protection of personal data. Article 35(3) names three cases where a DPIA is specifically required; security testing is not one of them. Source: Regulation (EU) 2016/679, Article 35 (Official Journal) | A test can supply technical input to a DPIA about system risk; it does not replace the DPIA. |
Reporting deadlines
| Deadline | What must be reported | To | Reference |
|---|---|---|---|
| Without undue delay and, where feasible, not later than 72 hours after having become aware of the breach | Notification of a personal data breach, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons | Supervisory authority | Art. 33(1) |
| Without undue delay after becoming aware of the breach | Processor notifies the controller of a personal data breach | Controller | Art. 33(2) |
| Without undue delay | Communication to affected individuals, where the breach is likely to result in a high risk to them | Data subjects | Art. 34(1) |
| No fixed period; every personal data breach must be documented | Facts of the breach, its effects and the remedial action taken | Controller (internal breach record) | Art. 33(5) |
Frequently asked questions
Does GDPR require penetration testing?
No. GDPR does not name penetration testing. Article 32(1)(d) asks controllers and processors for a process for regularly testing, assessing and evaluating the effectiveness of their security measures. A well-scoped penetration test is one common way to produce evidence for that element, and other methods can also contribute.
Is a penetration testing provider a data processor?
It can be, when it processes personal data on your behalf. Article 4(8) defines a processor as a body that processes personal data on behalf of the controller. If the provider is a processor, Article 28(3) requires a contract covering the matters the article lists, and the test scope should say what personal data the tester may access.
What is the 72-hour rule?
Article 33(1) requires the controller to notify the supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware of a personal data breach. The notice is not needed where the breach is unlikely to result in a risk to the rights and freedoms of natural persons, and a notice not made within 72 hours must give reasons for the delay. A processor must notify the controller without undue delay under Article 33(2).
Can a penetration test report contain personal data?
It can, and it should contain no more than a finding needs. Article 5(1)(c) limits personal data to what is necessary in relation to the purposes for which they are processed, so redact personal data from requests, responses and screenshots where you can, and keep the request that reproduces a flaw rather than copies of records. Set access and deletion rules for the report before the test starts.
Do I need a DPIA before a penetration test?
Article 35(1) requires an impact assessment before processing that is likely to result in a high risk to the rights and freedoms of natural persons. Article 35(3) names three cases where a DPIA is specifically required, and security testing is not among them. Whether a DPIA is needed is the controller’s assessment, and a test can supply technical input to it.
Related
Start an authorised scan from $399
Web Pentest and API Pentest are $399 per scan, Network / Host Pentest is $579, Email Security is $869 and Cloud Pentest is $2,299. Scans need a verified domain or a legal-authority attestation.
Sources
- Regulation (EU) 2016/679 of the European Parliament and of the Council (General Data Protection Regulation), OJ L 119, 4.5.2016, Articles 2 to 6, 24, 25, 28, 30, 32 to 35, 83 and 99 (Official Journal)
- EDPB Guidelines 9/2022 on personal data breach notification, version 2.0 (EDPB page; guidance, not law)
- EDPB Guidelines 4/2019 on Article 25, version 2.0 (EDPB page; guidance, not law)