GDPR Controls: Regulation (EU) 2016/679
57 controls (GDPR framework) organised in 7 categories | Reference: RGPD/GDPR
Legend: Legal/Organisational Technical Governance Updated on 2026-10-27: new section 8, with the mapping of controls to EterShield modules.
1. Legal Bases & Lawfulness of Processing
| Code | Title | Art. | Type | Priority |
|---|---|---|---|---|
| RGPD-6-1 | Identify and document the legal basis for each processing operation | Art. 6 | Legal/Organisational | CRITICAL |
| RGPD-7-1 | Collect explicit, specific, informed and withdrawable consent | Art. 7 | Legal/Organisational | HIGH |
| RGPD-7-2 | Keep a record of consents with date, channel and policy version | Art. 7 | Governance | HIGH |
| RGPD-9-1 | Identify special categories of data and ensure a reinforced legal basis | Art. 9 | Legal/Organisational | CRITICAL |
| RGPD-5b | Purpose limitation: data used only for the original purpose for which it was collected | Art. 5(1)(b) | Legal/Organisational | HIGH |
| RGPD-5c | Data minimisation: collect only what is strictly necessary | Art. 5(1)(c) | Legal/Organisational | HIGH |
2. Data Subject Rights
| Code | Title | Art. | Type | Deadline | Priority |
|---|---|---|---|---|---|
| RGPD-15 | Process for responding to access requests | Art. 15 | Legal/Organisational | 30 days | HIGH |
| RGPD-16 | Mechanism for rectification of incorrect or incomplete data | Art. 16 | Technical | 30 days | HIGH |
| RGPD-17 | Erasure process ("right to be forgotten") with validation of exceptions | Art. 17 | Technical | 30 days | HIGH |
| RGPD-18 | Restriction of processing when the accuracy of the data is contested | Art. 18 | Technical | N/A | MEDIUM |
| RGPD-20 | Data portability in a machine-readable format | Art. 20 | Technical | 30 days | MEDIUM |
| RGPD-21 | Process for objection to processing for direct marketing purposes | Art. 21 | Legal/Organisational | Immediate | HIGH |
| RGPD-22 | Decisions not taken solely by automated means without oversight | Art. 22 | Legal/Organisational | N/A | HIGH |
| RGPD-12-14 | Clear and transparent privacy notice at the time of collection | Art. 12-14 | Legal/Organisational | N/A | HIGH |
3. Technical and Organisational Security
| Code | Title | Art. | Type | Priority |
|---|---|---|---|---|
| RGPD-32-1 | Encryption of personal data at rest and in transit | Art. 32 | Technical | CRITICAL |
| RGPD-32-2 | Pseudonymisation where technically feasible | Art. 25, 32 | Technical | HIGH |
| RGPD-32-3 | Confidentiality, integrity and availability of processing systems | Art. 32(1)(b) | Technical | CRITICAL |
| RGPD-32-4 | Role-based access control (RBAC) and the principle of least privilege | Art. 32 | Technical | HIGH |
| RGPD-32-5 | Regular penetration tests and security assessments | Art. 32(1)(d) | Technical | HIGH |
| RGPD-25-1 | Privacy by Design and Privacy by Default in systems development | Art. 25 | Technical | HIGH |
| RGPD-32-6 | Audit logs for access to and modification of personal data | Art. 32 | Technical | HIGH |
| RGPD-32-7 | Management of security patches and vulnerabilities with a defined SLA | Art. 32 | Technical | HIGH |
4. Governance & Accountability
| Code | Title | Art. | Type | Priority |
|---|---|---|---|---|
| RGPD-30 | Up-to-date Record of Processing Activities (RoPA) | Art. 30 | Governance | HIGH |
| RGPD-37 | Appoint a Data Protection Officer (DPO) where mandatory | Art. 37 | Governance | MEDIUM |
| RGPD-24 | Documented internal data protection policies | Art. 24 | Governance | HIGH |
| RGPD-28 | Processor contracts (DPA) with all processors | Art. 28 | Legal/Organisational | CRITICAL |
| RGPD-24-2 | Periodic data protection training for all staff | Art. 24 | Governance | HIGH |
| RGPD-26 | Clear responsibilities defined between Controller and Processor | Art. 26, 28 | Governance | HIGH |
5. Data Breaches & Incident Management
| Code | Title | Art. | Type | Deadline | Priority |
|---|---|---|---|---|---|
| RGPD-33 | Process for detecting and notifying breaches to the CNPD | Art. 33 | Legal/Organisational | 72h | CRITICAL |
| RGPD-34 | Communication to data subjects in the event of a high-risk breach | Art. 34 | Legal/Organisational | Without undue delay | HIGH |
| RGPD-33-5 | Internal record of all data breaches | Art. 33(5) | Governance | N/A | HIGH |
| RGPD-32-IR | Incident response plan with defined roles and deadlines | Art. 32 | Governance | N/A | HIGH |
6. International Transfers
| Code | Title | Art. | Type | Priority |
|---|---|---|---|---|
| RGPD-44-MAP | Map all data transfers outside the EEA | Art. 44 | Governance | HIGH |
| RGPD-45-46 | Ensure a legal mechanism for transfers (adequacy, SCCs, BCRs) | Art. 45-46 | Legal/Organisational | CRITICAL |
| RGPD-46-REV | Regularly verify the validity of the transfer mechanisms | Art. 46 | Governance | HIGH |
| RGPD-46-TIA | Carry out a Transfer Impact Assessment (TIA) for transfers with a risk of surveillance by third-country authorities (Schrems II / EDPB Rec. 01/2020); document supplementary measures and residual risk | Art. 46 | Governance | CRITICAL |
EterShield module: Control RGPD-46-TIA is supported by the Transfer Impact Assessment module. DPF Watch automatically identifies Data Flows and DPAs without an approved TIA that are linked to DPF/adequacy transfers to the US, which is relevant since the collapse of the EU-US DPF on 29 June 2026.
7. Impact Assessment (DPIA)
| Code | Title | Art. | Type | Priority |
|---|---|---|---|---|
| RGPD-35 | Carry out a DPIA before high-risk processing | Art. 35 | Governance | HIGH |
| RGPD-36 | Consult the CNPD when the DPIA indicates high residual risk | Art. 36 | Legal/Organisational | HIGH |
| RGPD-35-REG | Register of DPIAs carried out, with results and mitigating measures | Art. 35 | Governance | HIGH |
8. Mapping of controls to EterShield
EterShield links each of the controls below to a platform module. When the checklist of a control is filled in (the "Fill with AI" button), the "have the record" lines are decided by rule and count, not by the AI: the same platform state always gives the same [x] or [ ], which makes the result reproducible in an audit. Each line indicates the module and the location of the record so the auditor can open it. The AI handles only the lines that depend on text (procedures, attached evidence). The state of the control derives from the final checklist: all lines [x] give compliant, some give partial, none give non-compliant; a control marked as not applicable is not changed.
There are 14 GDPR codes with a fixed rule:
| Code | Topic | Art. | EterShield module | Rule |
|---|---|---|---|---|
| RGPD-30 | Record of Processing Activities (RoPA) | Art. 30 | RoPA | at least 1 activity recorded |
| RGPD-28 | Processor contracts (DPA) | Art. 28 | Data processing agreements | at least 1 DPA signed or in force |
| RGPD-35 | DPIA | Art. 35, 36 | DPIA | at least 1 approved DPIA |
| RGPD-15, 16, 17, 18, 20, 21 | Data subject requests | Art. 12 to 22 | Data subject requests | it is enough for the module to be available (record with a 30-day deadline, status and history) |
| RGPD-13-14 | Privacy notice | Art. 13, 14 | Privacy notice | at least 1 (notice published to the data subject) |
| RGPD-33-5 | Breach record | Art. 33(5) | Breach notifications | it is enough for the module to be available |
| RGPD-7 | Consents | Art. 7 | Consents | at least 1 record |
| RGPD-5-5 | Retention periods | Art. 5(1)(e) | Retention periods | at least 1 rule defined |
| RGPD-44-MAP | International transfers | Art. 44 et seq. | Transfer Impact Assessments | at least 1 TIA |
If the query to a module fails, the rule does not decide that line, instead of assuming a value.
What each module does today
- RoPA (Art. 30). Record of processing activities. The DPIA column of the list distinguishes "missing", "in progress" and "approved". When the DPIA is approved, the activity's "DPIA required" notice closes by itself.
- DPA (Art. 28). Contracts with processors, with data scope per entity (lists, summaries, detail and DPF card).
- DPIA with four eyes and prior consultation (Art. 35 and 36). Cycle
DRAFT → IN_REVIEW → APPROVED | REJECTED, with reopening to draft; editing is only possible in draft. Approving and rejecting require permission to approve or reject DPIAs (SUPER_ADMIN and ADMIN) and segregation of duties is always mandatory, regardless of the tenant setting. With high or very high residual risk, approval only proceeds after the prior consultation of the supervisory authority and its response have been recorded (Art. 36). Through the API only the fields of a draft can be edited; the status is changed in the interface. - Data subject requests (Art. 12 to 22). Response templates in Portuguese and English for access, rectification, erasure, restriction, portability and objection (the automated decisions of Art. 22 have no template). The portability request (Art. 20) exports, in JSON or CSV, the map of the RoPA activities linked to the request (purpose, categories, legal basis, retention, processor, international transfer); the DPO adds the data subject's data. The export is recorded in the audit log.
- Public privacy notice (Art. 13 and 14). Public page
/privacidade/<slug>, without a session and not indexable, with an English version (?lang=en). The text is built from the active RoPA activities (purpose, legal basis, categories, period and transfers) and never includes security measures, processor names or internal notes. It is off by default; it is switched on and the contact is defined in Data Subject Requests (DSR) (requires permission to change the settings, recorded in the audit log). It is a template: legal validation remains with the organisation. - Data breaches (Art. 33 and 34). Each breach has the detection date (
detectedAt) and the date on which the organisation became aware (awareAt). The deadlines of 72 h to the CNPD and 24 h to the CNCS run fromawareAt, or fromdetectedAtif the former is not filled in, and are recalculated whenawareAtchanges. - Consents (Art. 7). Record of consents in Consents.
- Retention periods (Art. 5(1)(e)). Retention rules in Retention periods.
- TIA (Art. 44 et seq.). Impact assessment of transfers, linked to Data Flows and DPAs; the data scope per entity also applies here.
- LIA (Art. 6(1)(f)). Legitimate interest assessment. It has no fixed rule in the mapping; the GDPR package of the IT module creates a draft LIA.
- Annual GDPR review. Tenants with GDPR active receive a recurring annual review task (the next one on 31 December).
GDPR package of the IT module (#167)
On the equipment privacy page (requires permission to register devices and create policies), the "IT and Devices" module creates, in draft and without duplication, what the processing of employee data requires. The customer is the controller and EterShield is the processor.
| Item | Content |
|---|---|
| RoPA | 4 activities: equipment, access and JML, licences, IT requests |
| LIA | 1 assessment: legitimate interest in the security of systems (Art. 6(1)(f)) |
| DPIA | 1 assessment: remote surveillance means, MDM and telemetry (Labour Code, Arts. 20 and 21); approval requires permission to approve DPIAs |
| Retention | 4 rules: equipment assignment history 1 year after return; JML reports 5 years after the end; released licence seats 1 year; closed IT requests 2 years |
| Text | Notice to employees and the section "IT module: employee data" in the Eter DPA reference |
Measures described: inventory of hardware and network only (no software or usage history), no location, screen capture or activity logging, and removal of company data only on personal devices (BYOD).
Total: 57 controls.
Competent authority in Portugal: CNPD (Comissão Nacional de Proteção de Dados) | www.cnpd.pt
Source: Regulation (EU) 2016/679 (RGPD/GDPR)