# GDPR Article 35 — Data protection impact assessment - Source: https://support.icompaas.com/compliance/gdpr/article-35-data-protection-impact-assessment - Section: [Compliance](https://support.icompaas.com/compliance) › [GDPR (Regulation (EU) 2016/679)](https://support.icompaas.com/compliance/gdpr) › Articles 31–40 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **GDPR**·Article `Article 35`·high·Component: **Chapter IV: Controller and Processor** ## What this control requires > Controllers must conduct a data protection impact assessment (DPIA) for high-risk processing, especially involving new technologies, profiling, special data categories, or large-scale monitoring, detailing operations, purposes, risks, and mitigation measures, consulting the DPO and, where appropriate, data subjects. This control addresses Data Protection Impact Assessment. > > — GDPR, Article Article 35 ### In plain English Controllers must conduct a data protection impact assessment (DPIA) for high-risk processing, especially involving new technologies, profiling, special data categories, or large-scale monitoring, detailing operations, purposes, risks, and mitigation measures, consulting the DPO and, where appropriate, data subjects. In practice, this means you can prove you data controller-level controls on a defined cadence. ## Why it matters GDPR administrative fines reach the greater of €20 million or 4% of global annual turnover. The European Data Protection Board (EDPB) coordinates supervisory-authority enforcement across the EU/EEA, and DPAs publish enforcement decisions citing specific Articles. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A DPA or privacy auditor expects: a Records of Processing Activities (RoPA) entry, a documented lawful basis, evidence the Article's data-subject right is operationalised end-to-end, a named DPO contact (where required), and Article 30 records that match what the front-end actually does. Within **Chapter IV: Controller and Processor**, the assessor will trace your implementation back to the catalogue reference (Article Article 35) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. #### Vulnerability Management **Scanners.** Pair an unauthenticated scanner (Nessus / Qualys / Tenable.io) for external surface with an authenticated agent for OS/library CVEs on every host. **SLA.** Document remediation SLAs by CVSS / EPSS: critical 7 days, high 30 days, medium 90 days; report monthly trend to leadership. **Containers.** Scan images in CI (Trivy / Grype / Snyk Container) AND at runtime; block deploys on critical findings without exception. ### Operational checklist - **Data.** Document the trigger, the owner and the cadence. - **Processor.** Document the trigger, the owner and the cadence. - **Scope:** controller, controllers, protection impact assessment, conduct, data subjects. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Data protection impact assessment. ## Common pitfalls - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. - Scans that hit only the perimeter; missing authenticated scans of OS, runtime libs and base images so most CVEs are invisible. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-171 Rev. 3 3.12.2** — Plan of Action and Milestones](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-12-2-plan-of-action-and-milestones) - [**India DPDP Act 2023 PD-001** — Data Protection Impact Assessment Programme](https://support.icompaas.com/compliance/india-dpdp-act-2023/pd-001-data-protection-impact-assessment-programme) - [**BSI C5:2020 OPS-22** — Testing and Documentation of known Vulnerabilities](https://support.icompaas.com/compliance/bsi-c5-2020/ops-22-testing-and-documentation-of-known-vulnerabilities) ## Related controls in GDPR - [**Article Article 37** — Designation of the data protection officer](https://support.icompaas.com/compliance/gdpr/article-37-designation-of-the-data-protection-officer) - [**Article Article 27** — Representatives of controllers or processors not established in the Union](https://support.icompaas.com/compliance/gdpr/article-27-representatives-of-controllers-or-processors-not-established-in-the-union) - [**Article Article 28** — Processor](https://support.icompaas.com/compliance/gdpr/article-28-processor) - [**Article Article 38** — Position of the data protection officer](https://support.icompaas.com/compliance/gdpr/article-38-position-of-the-data-protection-officer) - [**Article Article 24** — Responsibility of the controller](https://support.icompaas.com/compliance/gdpr/article-24-responsibility-of-the-controller) - [**Article Article 3** — Territorial Scope](https://support.icompaas.com/compliance/gdpr/article-3-territorial-scope) ## References - [European Union — GDPR](https://eur-lex.europa.eu/eli/reg/2016/679/oj) - Catalogue identifier: `Article Article 35` Topics: governance risklogging monitoringcontinuous monitoringpolicy managementvulnerability management ## Related compliance guidance - [GDPR compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/gdpr): Start with the full GDPR implementation guide — scope, roadmap, evidence and how the assessment runs. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): The security management system most EU procurement teams ask for alongside a DPA; its controls supply much of the Article 32 evidence. - [India's DPDP Act 2023: a practical compliance guide for cloud teams](https://support.icompaas.com/compliance/india-dpdp-act-2023): If engineering or support teams sit in India, the same data flows are also subject to India’s Digital Personal Data Protection Act.