GDPR Article 12 — Transparent information, communication and modalities for the exercise of the rights of the data subject

What this control requires

The controller must provide clear, concise, and accessible information per Articles 13-14, and facilitate data subject rights under Articles 15-22, 34. Information must be free, timely (within one month), and in plain language, with extensions justified. Non-action requires reasoning and complaint options. Excessive requests may incur fees or refusal. This control addresses Data Subject Rights.

In plain English

The controller must provide clear, concise, and accessible information per Articles 13-14, and facilitate data subject rights under Articles 15-22, 34. In practice, this means you can prove you transparent 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 III: Rights of the Data Subject, the assessor will trace your implementation back to the catalogue reference (Article Article 12) and look for objective evidence on the latest two assessment cycles.

How to implement

1. Write a short policy stating intent, scope and named owner.
2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

• Transparent. Document the trigger, the owner and the cadence.
• Information. Document the trigger, the owner and the cadence.
• Data. Document the trigger, the owner and the cadence.
• Communication. Document the trigger, the owner and the cadence.
• Exercise. Document the trigger, the owner and the cadence.
• Scope: controller, rights, information.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Transparent information, communication and modalities for the exercise of the rights of the data subject.

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.

• ISO/IEC 27001:2022 A.5.18 — Access rights
• SOC 2 (2017 TSC) CC1.5 — Accountability for Internal Control Responsibilities
• NIST SP 800-171 Rev. 3 3.13.4 — Information in Shared System Resources
• ISO/IEC 27701:2025 A.3.9 — Access rights
• CIS Controls v8 9.2 — Use DNS Filtering Services

Related controls in GDPR

• Article Article 13 — Information to be provided where personal data are collected from the data subject
• Article Article 26 — Joint controllers
• Article Article 45 — Transfers on the basis of an adequacy decision
• Article Article 59 — Activity reports
• Article Article 92 — Exercise of the delegation

References

• European Union — GDPR
• Catalogue identifier: Article Article 12

Topics: identity accessidentity managementaccess reviewprivileged access