Jump to content

General Data Protection Regulation: Difference between revisions

From ICANNWiki
← Older editNewer edit →
VisualWikitext
No edit summary
Dustin Loup (talk | contribs)
Bureaucrats, Interface administrators, lookupuser, staff, Administrators, translator
11,770 edits
m Reverted edits by Kiran Kumar (talk) to last revision by Jackie Treiber
Line 9: Line 9:
The GDPR directly impacts the domain name space, most notability the [[WHOIS]] service. Prior to the GDPR enforcement date, [[ICANN]]'s contracted parties ([[Registry|Registries]] and [[Registrar]]s) expressed concern about their about to comply with their contractual requirement and be GDPR compliant. In light of this concern and the uncertainty around the implications of GDPR on WHOIS, ICANN announced that it would defer action against registries and registrars for noncompliance related to registration data.<ref>[https://www.icann.org/resources/pages/contractual-compliance-statement-2017-11-02-en ICANN Contractual Compliance Statement] Accessed 2 February 2018</ref>
The GDPR directly impacts the domain name space, most notability the [[WHOIS]] service. Prior to the GDPR enforcement date, [[ICANN]]'s contracted parties ([[Registry|Registries]] and [[Registrar]]s) expressed concern about their about to comply with their contractual requirement and be GDPR compliant. In light of this concern and the uncertainty around the implications of GDPR on WHOIS, ICANN announced that it would defer action against registries and registrars for noncompliance related to registration data.<ref>[https://www.icann.org/resources/pages/contractual-compliance-statement-2017-11-02-en ICANN Contractual Compliance Statement] Accessed 2 February 2018</ref>


==Personnel Data==
Understanding why and where personal data is stored and how it is being accessed within your organization is an essential element of General Data Protection Regulation (GDPR) readiness and compliance. But when personal data is spread across hundreds of different systems and platforms, it can be a big challenge for your organization to manage this duty and risk in a consistent and efficient manner across the enterprise. Can machine learning and cognitive capabilities help you accelerate your journey starts with the below challenges


* Insight into potential implications of the GDPR for your organization;
* Services and technological solution accelerators; and
* Practical examples of project challenges and lessons learned
==Information Security==
Information security continues to shift left, whether that be with known secure starting templates or more frequent code scanning via up-to-date cloud services and continuous security testing, and SecOps will play a crucial role in helping to ensure improved security without compromising agility. Cognitive-enabled tools will again be key to faster identification and resolution.
The availability of new hosting technologies such as Kubernetes by the large cloud infrastructure-as-a-service (IaaS) providers will bring interesting new challenges. Adopters must look beyond the hype when selecting vendors and consider key security considerations, including:
Network protection. Are sufficient firewall capabilities provided by the service provider
Hosting infrastructure security. Is the responsibility shared, and how does it impact our service availability


== References ==
== References ==
   
[[Category:5 . Security Intelligence Of GDPR]]

Revision as of 21:26, 6 February 2018

The Global Data Protection Regulation (GDPR) or Regulation (EU) 2016/679[1] is a regulation aimed at protecting all EU citizens and residents from privacy and data breaches. It was adopted on 14 April 2016 by the European Parliament (EP) after four years of collaborative drafting and negotiations.[2] The regulation is also an update of Data Protection Directive. Enforcement for the GDPR goes into effect on 25 May 2018.[3]

The GDPR places specific legal obligations on 'controllers' and 'processors', those who acts as intermediaries between the user/consumer and themselves, the government or any other actor. The controller determines how and why data is processed and processors act on the controller's behalf. Processors maintain data records and are held responsible in case of a breach.

With the update on existing legislation, the GDPR is more precise and inclusive of what constitutes private information than its predecessor. Personal data, that is anything that can identify a user, including an IP address is included, as well as 'sensitive personal data' which may include genetic and biomedical data.

GDPR and WHOIS[edit | edit source]

The GDPR directly impacts the domain name space, most notability the WHOIS service. Prior to the GDPR enforcement date, ICANN's contracted parties (Registries and Registrars) expressed concern about their about to comply with their contractual requirement and be GDPR compliant. In light of this concern and the uncertainty around the implications of GDPR on WHOIS, ICANN announced that it would defer action against registries and registrars for noncompliance related to registration data.[4]


References[edit | edit source]

  1. ↑ Regulation (EU) 2016/679 of the European Parliament and of the Council 27 April 2016
  2. ↑ Lexology - EU General Data Protection Regulation Finally Adopted 15 April 2016
  3. ↑ Reform of EU data protection rules. Retrieved 27 Jun 2017.
  4. ↑ ICANN Contractual Compliance Statement Accessed 2 February 2018
Retrieved from "https://icannwiki.org/index.php?title=General_Data_Protection_Regulation&oldid=1032688"