[Gnso-epdp-team] RrSG initial comment on SSAD Registrant user group
alan.greenberg at mcgill.ca
Fri Jun 7 16:02:43 UTC 2019
Registrants have the right to request their data from any controller or processor, so they are a "natural" potential user of the SSAD. Access from their own registrar (or reseller?) is presumably already covered through their contractual arrangements. So that primarily leaves the registry or their sub-contractors (to the extent that the registry possesses any such non-public data). If registries are happy to treat such requests as edge cases and handle them on an ad hoc basis, then I think we can safely leave them off as potential users of the SSAD. And save ourselves a lot of work in the process! :-)
At 07/06/2019 10:33 AM, Greg Aaron wrote:
Agree. Registrants already have the appropriate means to view their own sensitive data fields and update their domain data: the registrarâs system. And that provides controlled, permissioned access for the registrants to see their data and theirs only. And registrants will have public access to RDS to see non-sensitive data about their domains.
To offer registrants access to the SSAD System on top of that would be a nightmare from an access management view. (How would registrants get credentials into a SSAD, and how would that system know what records the registrant is allowed to see?) SSAD is for third parties who need to access non-public data.
From: Gnso-epdp-team <gnso-epdp-team-bounces at icann.org> On Behalf Of Sarah Wyld
Sent: Thursday, June 6, 2019 9:36 AM
To: gnso-epdp-team at icann.org
Subject: [Gnso-epdp-team] RrSG initial comment on SSAD Registrant user group
The RrSG has significant concerns with the inclusion of Registrants as a user group for the System for Standardized Disclosure of non-public gTLD registration data, and strongly recommends that this group be removed from the proposed list of users. We are curious as to the origin of these proposed user groups, and suggest that instead of working through this list we begin by reviewing the purposes for processing data (Recommendation 1) and assessing the potential user group applicable to each purpose.
Registrants already access their domains via their service provider (registrar or reseller)âs system, as required under the RAA. Having multiple interfaces to access the same information poses a significant risk of inappropriate data exposure; this unnecessary and unbalanced security risk is not compliant with data protection law. It also creates a confusing user experience for the registrant. For example, if a registrant uses the SSAD to review their domain data for the purpose of confirming that it is accurate, they would still need to work with their service provider to confirm that the data held in that system is also up to date.
The RrSG notes that a system used to access or disclose data is not also a system to modify that data. The EPDP team definitions of access and disclosure do not include any capability to modify the data, so this is a new addition to the requirements not grounded in any previously agreed-upon basis or definition. Modification of domains via the SSAD could easily result in synchronization issues and security risks, where the SSAD holds data that is different from what is in the registrar or resellerâs platform, or an unauthorized party could modify and even hijack a registered domain. This also represents a fundamental shift from the system in place for the past twenty years: EPP is one-directional, with data flowing from the reseller or registrar through to the registry, so any functionality for updating domain data would need to be created and implemented by thousands of service providers worldwide.
We look forward to discussing this important concern at todayâs EPDP team call. Beyond these concerns about the âRegistrantsâ group, we are also uncertain that âend usersâ is a valid group; this and the other groups should be discussed with the plenary team.
Domains Product Team
+1.416 535 0123 Ext. 1392
_______________________________________________Gnso-epdp-team mailing list
Gnso-epdp-team at icann.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnso-epdp-team