GDPR·Article Article 58·low·Component: Chapter VI: Supervisory Authorities

What this control requires

Supervisory authorities have investigative powers to access data, conduct audits, and notify infringements; corrective powers to issue warnings, reprimands, and orders for compliance, data erasure, or processing bans; and advisory powers to guide controllers, approve codes, certifications, and clauses. They enforce GDPR with safeguards, judicial remedies, and may initiate legal proceedings. This control addresses Supervisory Authorities.
— GDPR, Article Article 58

In plain English

Supervisory authorities have investigative powers to access data, conduct audits, and notify infringements; corrective powers to issue warnings, reprimands, and orders for compliance, data erasure, or processing bans; and advisory powers to guide controllers, approve codes, certifications, and clauses. In practice, this means you can prove you data controllers-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 VI: Supervisory Authorities, the assessor will trace your implementation back to the catalogue reference (Article Article 58) 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.

Operational checklist

  • Data. Document the trigger, the owner and the cadence.
  • Codes. Document the trigger, the owner and the cadence.
  • Supervisory. Document the trigger, the owner and the cadence.
  • Powers. Document the trigger, the owner and the cadence.
  • Safeguards. Document the trigger, the owner and the cadence.
  • Scope: controllers, conduct, certifications, proceedings.

Evidence to collect

  • Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Powers.

Common pitfalls

  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

Related controls in GDPR

References

Topics: governance riskpolicy management