<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Courier New \;color\:black";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.paragraph, li.paragraph, div.paragraph
{mso-style-name:paragraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;}
span.EmailStyle32
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi Volker - <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I am generally ok with your edits, with the exception of the changes to the listed safeguards, because those track what was submitted for the other questions, so it makes sense to keep the assumptions consistent
across questions posed to B&B. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Margie<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">Gnso-epdp-legal <gnso-epdp-legal-bounces@icann.org> on behalf of Volker Greimann <vgreimann@key-systems.net><br>
<b>Date: </b>Tuesday, October 1, 2019 at 9:02 AM<br>
<b>To: </b>"gnso-epdp-legal@icann.org" <gnso-epdp-legal@icann.org><br>
<b>Subject: </b>Re: [Gnso-epdp-legal] Updated Question 11<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p>Dear team, <o:p></o:p></p>
<p>please find attached a first commentary on the proposed question 11 outlining some issues and proposing some edits.<o:p></o:p></p>
<p>Best,<o:p></o:p></p>
<p>volker<o:p></o:p></p>
<div>
<p class="MsoNormal">Am 01.10.2019 um 15:56 schrieb Margie Milam:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi-</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Here’s my proposal based on prior discussions with Brian, Thomas & Volker. Please note that this language is not reviewed yet by Thomas, Brian & Volker, but I am sharing for the purposes of discussion today.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">__________________________</span><o:p></o:p></p>
<p class="MsoNormal"><b><u><span style="color:black">Updated Question 11</span></u></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:1.0in"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><i><span style="color:black">Status: Thomas, Volker, Brian and Margie to work together on refining this question in advance of the next LC call on Tuesday, 1 October.</span></i><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:1.0in"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">(Previous text proposed by Margie)<i>: </i>Is it permissible under GDPR to provide fast, automated, and non-rate limited responses (as described in SSAC 101) to nonpublic WHOIS data for properly credentialed security
practitioners<sup>1 </sup><span style="background:yellow;mso-highlight:yellow">(<s>as defined in SSAC 101</s>)</span> who are responsible for defense against e-crimes (including network operators, providers of online services, commercial security services,
cyber-crime investigators) for use in investigations and mitigation activities to protect their network, information systems or services (as referenced in GDPR Recital 49) and have agreed on appropriate safeguards? Or would any automated disclosure carry a
potential for liability of the disclosing party, or the controllers or processors of such data? Can counsel provide examples of safeguards (such as pseudonymization/anonymization) that should be considered?
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black;background:yellow;mso-highlight:yellow">In addition, does GDPR prohibit the SSAD to be designed to enable reverse lookups based on contact fields associated with domain names that have been identified as being
used for DNS abuse, such as phishing, malware and or similar type of attacks? What are the risks associated with reverse lookups, and if it is possible to conduct reverse lookups, are there steps that can be taken to mitigate any perceived risks?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">For purposes of this question, please assume the following safeguards are in place: </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:71.25pt"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:1.5in;text-indent:-.25in">
<span style="font-size:10.0pt;font-family:"Courier New \;color\:black"">o</span><span style="font-size:7.0pt"> </span><span style="color:black">Disclosure is required under CP’s contract with ICANN (resulting from Phase 2 EPDP policy).</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:1.5in;text-indent:-.25in">
<span style="font-size:10.0pt;font-family:"Courier New \;color\:black"">o</span><span style="font-size:7.0pt"> </span><span style="color:black">CP’s contract with ICANN requires CP to notify the data subject of the purposes for which, and types of entities
by which, personal data may be processed. CP is required to notify data subject of this with the opportunity to opt out before the data subject enters into the registration agreement with the CP, and again annually via the ICANN-required registration data
accuracy reminder. CP has done so.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:1.5in;text-indent:-.25in">
<span style="font-size:10.0pt;font-family:"Courier New \;color\:black"">o</span><span style="font-size:7.0pt"> </span><span style="color:black">ICANN or its designee has validated/verified the requestor’s identity, and required in each instance that the
requestor: </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:163.0pt;text-indent:-37.0pt;vertical-align:baseline">
<span style="color:black">• represents that it has a lawful basis for requesting and processing the data, </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:163.0pt;text-indent:-37.0pt;vertical-align:baseline">
<span style="color:black">• provides its lawful basis, </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:163.0pt;text-indent:-37.0pt;vertical-align:baseline">
<span style="color:black">• represents that it is requesting only the data necessary for its purpose, </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:163.0pt;text-indent:-37.0pt;vertical-align:baseline">
<span style="color:black">• agrees to process the data in accordance with GDPR, and </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:163.0pt;text-indent:-37.0pt;vertical-align:baseline">
<span style="color:black">• agrees to EU standard contractual clauses for the data transfer. </span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black;background:yellow;mso-highlight:yellow">Footnote 1:
<s>SSAC defines</s> “security practitioners” <s>in SSAC 101 as those who have a responsibility to perform specific types of functions (as specified in Section 3) related to the identification and mitigation of malicious activity, and the correction of problems
that negatively affect services and users online. </s></span><span style="font-size:11.0pt;background:yellow;mso-highlight:yellow"> are entities that have either legal authority and/or legal responsibility to protect their technology/network/infrastructure,
such as national CERTs, and also DSPs. (See the UK ICO (</span><span style="background:yellow;mso-highlight:yellow"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__ico.org.uk_for-2Dorganisations_the-2Dguide-2Dto-2Dnis_digital-2Dservice-2Dproviders_&d=DwMGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=_4XWSt8rUHZPiRG6CoP4Fnk_CCk4p550lffeMi3E1z8&m=xeXHSQy6Jg3NeENvgZ2sqoBiOr3J07ArOU4MUONzwU4&s=avDrp6cxNXTZKuZCGeGUDM-Cgi0HhyR9IzaQzQAiu3Y&e=">https://ico.org.uk/for-organisations/the-guide-to-nis/digital-service-providers/</a>)
since these types of companies appear to have security obligations (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__ico.org.uk_for-2Dorganisations_the-2Dguide-2Dto-2Dnis_security-2Drequirements_&d=DwMGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=_4XWSt8rUHZPiRG6CoP4Fnk_CCk4p550lffeMi3E1z8&m=xeXHSQy6Jg3NeENvgZ2sqoBiOr3J07ArOU4MUONzwU4&s=5R4dCyK71voQGm83RO7mPQTr5MU4wMXYqIbyvBJCJUE&e=">https://ico.org.uk/for-organisations/the-guide-to-nis/security-requirements/</a>).</span>
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Gnso-epdp-legal mailing list<o:p></o:p></pre>
<pre><a href="mailto:Gnso-epdp-legal@icann.org">Gnso-epdp-legal@icann.org</a><o:p></o:p></pre>
<pre><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Depdp-2Dlegal&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=_4XWSt8rUHZPiRG6CoP4Fnk_CCk4p550lffeMi3E1z8&m=NkMDNojCKj2xx_bu5c73yYRvS4FXTmB_APUpaDcdqXE&s=FXupu7dFwhNX8DGYd8APdAMVI6ol2N2ujebo-S41x7w&e=">https://mm.icann.org/mailman/listinfo/gnso-epdp-legal</a><o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=_4XWSt8rUHZPiRG6CoP4Fnk_CCk4p550lffeMi3E1z8&m=NkMDNojCKj2xx_bu5c73yYRvS4FXTmB_APUpaDcdqXE&s=1mdiqQvGEoTBRTJ1PTdmMauaC83rv17COTdaqlyUxAA&e=">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=_4XWSt8rUHZPiRG6CoP4Fnk_CCk4p550lffeMi3E1z8&m=NkMDNojCKj2xx_bu5c73yYRvS4FXTmB_APUpaDcdqXE&s=bsBO5Rv8_cHc9mFQ-IIw1p9F4Hp6AhGlKJtIzqDp284&e=">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.<o:p></o:p></pre>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">-- <br>
Volker A. Greimann<br>
General Counsel and Policy Manager<br>
<strong><span style="font-family:"Calibri",sans-serif">KEY-SYSTEMS GMBH</span></strong><br>
<br>
T: +49 6894 9396901<br>
M: +49 6894 9396851<br>
F: +49 6894 9396851<br>
W: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.key-2Dsystems.net&d=DwMDaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=_4XWSt8rUHZPiRG6CoP4Fnk_CCk4p550lffeMi3E1z8&m=NkMDNojCKj2xx_bu5c73yYRvS4FXTmB_APUpaDcdqXE&s=0F-1Jjn2Jt2GfXQnqZ6pMiHkOwfyvG6cxvVYkmlVBbE&e=">
www.key-systems.net</a><br>
<br>
Key-Systems GmbH is a company registered at the local court of Saarbruecken, Germany with the registration no. HR B 18835<br>
CEO: Alexander Siffrin<br>
<br>
Part of the CentralNic Group PLC (LON: CNIC) a company registered in England and Wales with company number 8576358.<o:p></o:p></span></p>
</div>
</div>
</body>
</html>