Skip to content

Menu

LexBlog, Inc. logo
NetworkSub-MenuBrowse by SubjectBrowse by PublisherJoin the NetworkGet StartedSubscribeSupportContact
Search
Close

GDPR Guidance: Data Controllers Are Responsible for Processors’ Competency

By Odia Kagan on December 14, 2018
Email this postTweet this postLike this postShare this post on LinkedIn

The UK Information Commissioner’s Office (ICO) has issued a new guidance on the liabilities of Controllers and Processors, advising that the Controller is responsible for assessing that its Processor is competent to process personal data in line with GDPR’s requirements.

  • The assessment by Controller should take into account the nature of the processing and the risks to data subjects.
  • Some considerations:
    1. the extent to which the Processor complies with industry standards, if applicable
    2. whether the Processor has sufficient technical expertise to assist the Controller, e.g. in carrying out obligations under Articles 32-36 of the GDPR (technical measures, breach notifications and DPIAs)
    3. providing Controller with relevant documentation, e.g. privacy, record management and information security policies
    4. adherence to an approved code of conduct (when available)
  • Controllers should continue to monitor a Processor’s compliance, with frequency and methods used to audit compliance depending on the circumstances of the processing.

Read the full guidance.

  • Posted in:
    Privacy and Cybersecurity
  • Blog:
    Privacy Compliance & Data Security
  • Organization:
    Fox Rothschild LLP
  • Article: View Original Source

Call us at 1-800-913-0988 or email sales@lexblog.com.

Facebook LinkedIn Twitter RSS
The Library at LexBlog
  • About LexBlog
  • The Field We Built
  • Library at LexBlog
  • Our Beliefs
  • Our Team
  • Contact LexBlog
  • Disclaimer
  • Editorial Policy
  • Terms of Service
  • Get Started
  • Publishing Solutions
  • Compass
  • Submit a Request
  • Support Center
  • System Status
Copyright © 2026, LexBlog, Inc. All Rights Reserved.
Law blog design & platform by LexBlog LexBlog Logo