11,770
edits
Changes
Jump to navigation
Jump to search
mLine 9:
Line 9: − ==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 − − − − − − [[Category:5 . Security Intelligence Of GDPR]]
General Data Protection Regulation (view source)
Revision as of 21:26, 6 February 2018
, 6 years agoReverted edits by Kiran Kumar (talk) to last revision by Jackie Treiber
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>
== References ==
== References ==