← GDPR · Accountability

Art.37 — Designation of a data protection officer

medium dporoles-responsibilities

Requirement

A controller or processor must designate a DPO if it is a public authority, or if its core activities involve large-scale regular and systematic monitoring of individuals or large-scale processing of special-category or criminal data; the DPO's contact details must be published and communicated to the supervisory authority. Others should record why no DPO is required.

What the engine looks for

Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.

Required element 1 — any one of

data protection officerdpoprivacy officer

Required element 2 — any one of

designat…appointappointedpublishedcontact detailsnot requiredregistered with

Supporting terms — specificity signals

article 37large scalecore activitiessystematic monitoringsupervisory authorityassessment of whether requiredexpert knowledge

Equivalent controls elsewhere

Matched on shared topics. Satisfying this control usually moves these too.

Framework	Control	Title	Shared topics
NDPA 2023	s.32	Designation of a Data Protection Officer	dpo roles-responsibilities
SOC 2	CC1.3	Organisational structure and reporting lines	roles-responsibilities
SOC 2	CC1.5	Accountability for control responsibilities	roles-responsibilities
ISO 27001	A.5.2	Information security roles and responsibilities	roles-responsibilities
HIPAA	164.308(a)(2)	Assigned security responsibility (R)	roles-responsibilities
GLBA	314.4(a)	Qualified Individual oversees the information security program	roles-responsibilities
NIST CSF 2.0	GV.RR-02	Roles, responsibilities and authorities are established	roles-responsibilities