# GDPR Article 97 — Commission reports - Source: https://support.icompaas.com/compliance/gdpr/article-97-commission-reports - Section: [Compliance](https://support.icompaas.com/compliance) › [GDPR (Regulation (EU) 2016/679)](https://support.icompaas.com/compliance/gdpr) › Articles 91–100 - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **GDPR**·Article `Article 97`·low·Component: **Chapter XI: Final Provisions** ## What this control requires > This control mandates that the Commission submit a report every four years, starting from 25 May 2020, on the evaluation and review of GDPR. The report will focus on the application of specific chapters related to data transfers and cooperation, and may lead to proposals for amendments based on technological developments and feedback from relevant bodies. This control addresses Final Provisions. > > — GDPR, Article Article 97 ### In plain English This control mandates that the Commission submit a report every four years, starting from 25 May 2020, on the evaluation and review of GDPR. In practice, this means you can prove you data transfers-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. ## 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 XI: Final Provisions**, the assessor will trace your implementation back to the catalogue reference (Article Article 97) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Secure Development **Pipeline.** Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline. **Branch protection.** Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence. #### Code Review Testing **Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this. ### Operational checklist - **Data.** Document the trigger, the owner and the cadence. - **Cooperation.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Transfers.** Document the trigger, the owner and the cadence. - **Reports.** Document the trigger, the owner and the cadence. - **Scope:** transfers, reports, commission. ## Evidence to collect - **Code Repo Scan.** Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports. Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Commission reports. ## Common pitfalls - CI security checks set to warn-only; the merge button is faster than the security feedback. ## 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. - [**CIS Controls v8 16.3** — Perform Root Cause Analysis on Security Vulnerabilities](https://support.icompaas.com/compliance/cis-controls-v8/16-3-perform-root-cause-analysis-on-security-vulnerabilities) - [**ISO/IEC 27001:2022 A.8.28** — Secure coding](https://support.icompaas.com/compliance/iso-27001-2022/a-8-28-secure-coding) - [**SOC 2 (2017 TSC) P5.2** — Correction and Amendment of Personal Information](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/p5-2-correction-and-amendment-of-personal-information) - [**BSI C5:2020 PSS-02** — Identification of Vulnerabilities of the Cloud Service](https://support.icompaas.com/compliance/bsi-c5-2020/pss-02-identification-of-vulnerabilities-of-the-cloud-service) - [**ISO/IEC 42001:2023 A.6.2.8** — Development of AI system](https://support.icompaas.com/compliance/iso-42001-2023/a-6-2-8-development-of-ai-system) ## Related controls in GDPR - [**Article Article 46** — Transfers subject to appropriate safeguards](https://support.icompaas.com/compliance/gdpr/article-46-transfers-subject-to-appropriate-safeguards) ## References - [European Union — GDPR](https://eur-lex.europa.eu/eli/reg/2016/679/oj) - Catalogue identifier: `Article Article 97` Topics: application securitysecure developmentcode review testingdevsecops ## 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.