<\/p>\n\n\n\n
The obligation of diligence and verification that the processor maintains secure systems is the responsibility of the data controller as can be seen in a recent Resolution of the AEPD that establishes a Penalty of<\/strong> \ud835\udfee\ud835\udfec\ud835\udfec\ud835\udfec\ud835\udfec\ud835\udfec to a hospital center for security deficiencies in its hospital management system<\/strong>.<\/p>\n\n\n\n The case exposes specific flaws in the legal relationship between the hospital (data controller) and the company providing and managing the software (processor), in accordance with the provisions of Article 28 of the GDPR:<\/p>\n\n\n\n – Data Processor Contract:<\/strong> The GDPR establishes that the data controller must only contract with data processors that offer sufficient guarantees to implement the necessary security measures. The AEPD Resolution considered that the contract with the technology company did not adequately detail the required data protection measures, and the hospital did not carry out a thorough verification of the company’s ability to comply with the GDPR rules.<\/p>\n\n\n\n – Oversight of the Supervisor<\/strong>: The AEPD also found that the hospital did not adequately monitor the supervisor’s compliance with the security measures. This included periodic audits and security reviews to ensure that security policies and measures were effectively implemented. The lack of oversight facilitated an environment where deficiencies went unnoticed, resulting in significant vulnerabilities to patient data.<\/p>\n\n\n\n – Shared Risk Assessment and Management<\/strong>: Although the processor is responsible for implementing the necessary security measures, the AEPD recalls in its Resolution that the controller must verify and require that such measures are effective and sufficient. In this case, the hospital did not coordinate adequately with the technology company to assess and manage the risks associated with the processing of personal data. No security audits were conducted, nor was there coordination to mitigate the identified risks.<\/p>\n\n\n\n – Liability<\/strong>: In the event of non-compliance, both the controller and the processor may be liable for breaches, in accordance with the provisions of the GDPR. The sanction imposed on the hospital illustrates that both the controller and the processor have obligations to ensure data security, and that liability is not limited to the processor alone.<\/p>\n\n\n\n This sanctioning resolution of the AEPD illustrates the importance of proper implementation of security measures and rigorous compliance with the obligations of data controllers and processors in data protection. The GDPR emphasizes that both must act diligently to protect the rights of data subjects, in this case patients, and ensure that the processing of their data is carried out in a secure and compliant environment.<\/p>\n<\/div><\/div>\n<\/div><\/div>\n\n\n\n <\/p>\n","protected":false},"featured_media":12039,"template":"novedad-corporativa-single-post.php","categories":[],"tags":[214,212],"novedades_corporativa":[],"class_list":["post-35379","noticias","type-noticias","status-publish","has-post-thumbnail","tag-gdpr","tag-news","entry"],"acf":[],"yoast_head":"\nArticle 28 of the GDPR:<\/strong> Relationship between Controller and Processor<\/h2>\n\n\n\n
Conclusion<\/h3>\n\n\n\n