Accuracy: Difference between revisions

(7 intermediate revisions by 2 users not shown)

Line 6:

* [[Cybersecurity]] workers and enthusiasts insist that data accuracy is important to mitigating [[DNS Abuse]] as law enforcement agencies and regulatory bodies need it for notifying victims, acting as a dissuading factor for bad actors, and ultimately catching perpetrators.<ref>Gabriel Andrews, of the FBI, representing the Public Safety Working Group, on the GAC Discussions: IGO Protection Matters and DNS Abuse Mitigation Panel, ICANN 72</ref>

===Will Ensuring Data Accuracy actually stop bad actors===

* Data registration regulation flowing down the [[ICANN]] hierarchy may not reach malicious activity because hackers do not provide accurate email addresses, money trails, or registration data.<ref>Theo Geurts, presenting on a DNS Abuse Dashboard at the GNSO: NCSG Membership Meeting, ICANN 72]</ref>

==References==

==Post-GDPR==

On 21 October 2020, the [[GNSO Council]] adopted a proposal that recommended that a Scoping Team address the effects of [[GDPR]] on Registration Data accuracy requirements and the [[Whois]] Accuracy Reporting System (ARS).

On 22 July 2021, the GNSO Council confirmed the formation of the Accuracy Scoping Team tasked to consider accuracy-related factors such as the current enforcement, reporting, measurement, and overall effectiveness of accuracy-related efforts. These considerations will inform the deliberations and development of recommendations to the GNSO Council to improve accuracy levels.<ref>[https://community.icann.org/display/gnsocouncilmeetings/Project+List?preview=/150178773/210469897/GNSO_Council_Project-List_20220825.pdf GNSO Council Project List, August 2022, Community, ICANN]</ref><br/>

In October 2021, the scoping team began its deliberations, focusing on defining, enforcing, reporting, and measuring accuracy. As of [[ICANN 75]], the team focused on proposals that do not require access to gTLD registration data, such as a registrar survey or registrar audit, but is concerned about low participation.<ref>[https://meetings.icann.org/en/remote75/icann75-policy-outlook-report-05sep22-en, EPDP-IDNs Background, GNSO Sessions, ICANN 75 Policy Outlook]</ref>

Specifically, the Scoping Team recommended to the GNSO Council:<ref>[https://75.schedule.icann.org/meetings/mLgjoa3GEzrYfnKba Accuracy Scoping Team Sessions, ICANN 75]</ref>

# requests that ICANN org carry out a Registrar Survey

# explore the option of conducting a Registrar Audit

Or

# pause the work involving proposals requiring access to registration data until it's a viable path

# request that ICANN org proceed with their outreach to EDPB with urgency as well as DPIA in connection with the scenarios

# encourage the finalizing the DPA between ICANN org and Contracted Parties

The [[ICANN Board]] has also directed [[ICANN Organization]] to develop scenarios for obtaining access to gTLD registration data to confirm accuracy that could be tested with the European Data Protection Board (EDPB). As of September 2022, the EDPB has not responded.

On November 17, 2022, the GNSO Council resolved to pause the work in relation to proposals that require access to registration data, 2) encourage ICANN org to proceed with their outreach to the EDPB and the Data Protection Impact Assessment, and 3) request that ICANN org and Contracted Parties finalize the negotiations on the Data Processing Agreement (DPA).<ref>[https://gnso.icann.org/en/council/resolutions/2020-current#202011 November 17, 2022 Resolutions, GNSO Council, ICANN]</ref>

== References ==

@@ Line 6: / Line 6: @@
 * [[Cybersecurity]] workers and enthusiasts insist that data accuracy is important to mitigating [[DNS Abuse]] as law enforcement agencies and regulatory bodies need it for notifying victims, acting as a dissuading factor for bad actors, and ultimately catching perpetrators.<ref>Gabriel Andrews, of the FBI, representing the Public Safety Working Group, on the GAC Discussions: IGO Protection Matters and DNS Abuse Mitigation Panel, ICANN 72</ref>
 ===Will Ensuring Data Accuracy actually stop bad actors===
 * Data registration regulation flowing down the [[ICANN]] hierarchy may not reach malicious activity because hackers do not provide accurate email addresses, money trails, or registration data.<ref>Theo Geurts, presenting on a DNS Abuse Dashboard at the GNSO: NCSG Membership Meeting, ICANN 72]</ref>
-==References==
+==Post-GDPR==
+On 21 October 2020, the [[GNSO Council]] adopted a proposal that recommended that a Scoping Team address the effects of [[GDPR]] on Registration Data accuracy requirements and the [[Whois]] Accuracy Reporting System (ARS).
+On 22 July 2021, the GNSO Council confirmed the formation of the Accuracy Scoping Team tasked to consider accuracy-related factors such as the current enforcement, reporting, measurement, and overall effectiveness of accuracy-related efforts. These considerations will inform the deliberations and development of recommendations to the GNSO Council to improve accuracy levels.<ref>[https://community.icann.org/display/gnsocouncilmeetings/Project+List?preview=/150178773/210469897/GNSO_Council_Project-List_20220825.pdf GNSO Council Project List, August 2022, Community, ICANN]</ref><br/>
+In October 2021, the scoping team began its deliberations, focusing on defining, enforcing, reporting, and measuring accuracy. As of [[ICANN 75]], the team focused on proposals that do not require access to gTLD registration data, such as a registrar survey or registrar audit, but is concerned about low participation.<ref>[https://meetings.icann.org/en/remote75/icann75-policy-outlook-report-05sep22-en, EPDP-IDNs Background, GNSO Sessions, ICANN 75 Policy Outlook]</ref>
+Specifically, the Scoping Team recommended to the GNSO Council:<ref>[https://75.schedule.icann.org/meetings/mLgjoa3GEzrYfnKba Accuracy Scoping Team Sessions, ICANN 75]</ref>
+# requests that ICANN org carry out a Registrar Survey
+# explore the option of conducting a Registrar Audit
+Or
+# pause the work involving proposals requiring access to registration data until it's a viable path
+# request that ICANN org proceed with their outreach to EDPB with urgency as well as DPIA in connection with the scenarios
+# encourage the finalizing the DPA between ICANN org and Contracted Parties
+The [[ICANN Board]] has also directed [[ICANN Organization]] to develop scenarios for obtaining access to gTLD registration data to confirm accuracy that could be tested with the European Data Protection Board (EDPB). As of September 2022, the EDPB has not responded.
+On November 17, 2022, the GNSO Council resolved to pause the work in relation to proposals that require access to registration data, 2) encourage ICANN org to proceed with their outreach to the EDPB and the Data Protection Impact Assessment, and 3) request that ICANN org and Contracted Parties finalize the negotiations on the Data Processing Agreement (DPA).<ref>[https://gnso.icann.org/en/council/resolutions/2020-current#202011 November 17, 2022 Resolutions, GNSO Council, ICANN]</ref>
+== References ==
+{{reflist}}